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
This whole issue relates to iOS. There are two situations that produce identical data but should be handled separately. When the user has the app open and a new notification comes through, it is not shown (as expected). However, when a user has the app open and opens the notification drawer in the foreground and clicks a notification, nothing happens (not expected). This is because the notifications in these two cases are identical. Both notifications, when returned from the plugin have the "tap" boolean as false. This makes it impossible to handle these situations differently. I would think that a user clicking a notification from the notification drawer (even with the app open) would have a tap value of true (which it does when the app isn't open).
The text was updated successfully, but these errors were encountered:
This whole issue relates to iOS. There are two situations that produce identical data but should be handled separately. When the user has the app open and a new notification comes through, it is not shown (as expected). However, when a user has the app open and opens the notification drawer in the foreground and clicks a notification, nothing happens (not expected). This is because the notifications in these two cases are identical. Both notifications, when returned from the plugin have the "tap" boolean as false. This makes it impossible to handle these situations differently. I would think that a user clicking a notification from the notification drawer (even with the app open) would have a tap value of true (which it does when the app isn't open).
The text was updated successfully, but these errors were encountered: