You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not good at English, so I ask for your understanding of using a translator.
my library version is flutter_local_notifications: 4.0.1+2
I am using 6 notification channels and I am trying to create 2 notification channels.
However, when two are generated, the notification sound of the existing channel changes.
create chennel part in my code const newOrderNotiChannel = AndroidNotificationChannel( 'noti_push_NEW_ORDER', // id 'noti_push_NEW_ORDER', // title 'neworder', // de sound: RawResourceAndroidNotificationSound('new_order'), importance: Importance.max); await flutterLocalNotificationsPlugin .resolvePlatformSpecificImplementation<AndroidFlutterLocalNotificationsPlugin>() ?.createNotificationChannel(newOrderNotiChannel);
when send notification value of android_channel_id as noti_push_NEW_ORDER,
The sound that plays is the basic sound or other custom sound (ex DONE_ORDER) but title body is right.
Ios have no problem. i think.. because it is handed over to the sound of payload.
While searching for this issue, the stackoverflow answer is write keep.xml, so this code is also written down. <?xml version="1.0" encoding="utf-8"?> <resources xmlns:tools="http://schemas.android.com/tools" tools:keep="@drawable/*,@raw/new_order,@raw/hurry_order,@raw/checked_order,@raw/new_message,@raw/new_notice,@raw/test_alarm" />
If i send notification A, iwill hear notification B sound , and if isend notification B, i will hear sound C.
If the notification sound changes after release at google play, users will feel uncomfortable because there is no solution other than reinstalling the application and deleting data.
Is this a version issue? Or is there a solution?
The text was updated successfully, but these errors were encountered:
I'm reopening this as from the issue you've described, it looks like there's a valid problem to be addressed here where if the resource IDs change, a different sound could be played
I'm not good at English, so I ask for your understanding of using a translator.
my library version is
flutter_local_notifications: 4.0.1+2
I am using 6 notification channels and I am trying to create 2 notification channels.
However, when two are generated, the notification sound of the existing channel changes.
create chennel part in my code
const newOrderNotiChannel = AndroidNotificationChannel( 'noti_push_NEW_ORDER', // id 'noti_push_NEW_ORDER', // title 'neworder', // de sound: RawResourceAndroidNotificationSound('new_order'), importance: Importance.max); await flutterLocalNotificationsPlugin .resolvePlatformSpecificImplementation<AndroidFlutterLocalNotificationsPlugin>() ?.createNotificationChannel(newOrderNotiChannel);
send notification on server
const NOTI_FOR_NEW_ORDER = { notification: { title: "neworder", body: "neworder", android_channel_id: "noti_push_NEW_ORDER", sound: "NEW_ORDER.wav" }, data: { click_action: "FLUTTER_NOTIFICATION_CLICK", type: "NEW_ORDER" } };
when send notification value of android_channel_id as noti_push_NEW_ORDER,
The sound that plays is the basic sound or other custom sound (ex DONE_ORDER) but title body is right.
Ios have no problem. i think.. because it is handed over to the sound of payload.
While searching for this issue, the stackoverflow answer is write keep.xml, so this code is also written down.
<?xml version="1.0" encoding="utf-8"?> <resources xmlns:tools="http://schemas.android.com/tools" tools:keep="@drawable/*,@raw/new_order,@raw/hurry_order,@raw/checked_order,@raw/new_message,@raw/new_notice,@raw/test_alarm" />
If i send notification A, iwill hear notification B sound , and if isend notification B, i will hear sound C.
If the notification sound changes after release at google play, users will feel uncomfortable because there is no solution other than reinstalling the application and deleting data.
Is this a version issue? Or is there a solution?
The text was updated successfully, but these errors were encountered: