Notifications: read one by one & read selected only

Solar2D General Questions/Discussion
#1

I have 2 part question regarding notifications (testing so far only on Android)

#1 when app is in the background

When notifications appears, there are listed in menu under status bar. I use lunchArgs approach to handle selecting notiication from this menu. However if I select one, all other disappear. Is there a way to read only selected one?

#2 when you are using application

If I use “notification” listener it reacts twice for each notification. First it fires when notification appears in status bar (and notification is still in the status bar dropdown menu). Second one is when I select one manualy. From what  I saw the event content is the same (not 100% sure but I think it was). Is there the way to separate this two actions?

#2

I posted about the second issue as I see exactly the same thing. I received no answer but it appears for now there is no way to differentiate. I would like the events to arrive with a ‘source’ parameter or something, so at least you’d know if it came from the notification bar, or was the internal event. With launch args I don’t see what you see - only the notification that you select gets removed from the bar. Are you clearing all notifications and setting them up again when you enter your app? That could explain them all vanishing. Regarding the notifications in the app, I am likely to try out a solution (ie something better than just ignoring all notifications received when e app is open). I am going to assign each notification that I create a unique id. If a notifitcation arrives while the app is open, I will ignore the first time an event arrives with that ID as it is guaranteed to be the internal event. You can’t do it the other way around (ie process the internal notification and then remove the notification from the system bar because you can’t save the notification ID to remove it later (corona staff explained that once you send out a notification abd close the app, the OS does not give you control to remove individual notifications, only all of them).

#3

Ah right, I had to schedule notifications once again on start to get new ids, so this is it, my bad to miss it :stuck_out_tongue:

Yes, I discussed this on forum with staff and they thankfuly expanded notification documentation gotchas with android notification handling :slight_smile:

#4

I posted about the second issue as I see exactly the same thing. I received no answer but it appears for now there is no way to differentiate. I would like the events to arrive with a ‘source’ parameter or something, so at least you’d know if it came from the notification bar, or was the internal event. With launch args I don’t see what you see - only the notification that you select gets removed from the bar. Are you clearing all notifications and setting them up again when you enter your app? That could explain them all vanishing. Regarding the notifications in the app, I am likely to try out a solution (ie something better than just ignoring all notifications received when e app is open). I am going to assign each notification that I create a unique id. If a notifitcation arrives while the app is open, I will ignore the first time an event arrives with that ID as it is guaranteed to be the internal event. You can’t do it the other way around (ie process the internal notification and then remove the notification from the system bar because you can’t save the notification ID to remove it later (corona staff explained that once you send out a notification abd close the app, the OS does not give you control to remove individual notifications, only all of them).

#5

Ah right, I had to schedule notifications once again on start to get new ids, so this is it, my bad to miss it :stuck_out_tongue:

Yes, I discussed this on forum with staff and they thankfuly expanded notification documentation gotchas with android notification handling :slight_smile: