Douglas M. Barcellos

SO: Android 7.0 - Physical Device I have the same problem. When opening the app for the first time through the notification, **getInitialNotification()** runs perfectly. After leaving the app idle...

In recent days I've been trying to solve this problem by researching, modifying, and debugging the native code. Even though my background has been based on Java, I find it...

I have not given up yet. Yesterday, while I was in the barber shop waiting for my turn, I still insisted on how to solve the problem, cleanly. I did...

> 1. Is there a way for iOS to do the same? Since I do not program for iOS I really do not know how to answer that. In fact,...

@evollu I think there may be a misunderstanding about point 2. The problem is precisely because on Android, when the app is killed by the system (not by the user)...

@evollu 1. Yes, through the listener `FCM.on(FCMEvent.Notification, fn)`. 2. In this case, through the `getInitialNotification()`.

> case 2: You don't get any notification callback? No, I'm getting the callback data

> then why not just act on the callback data? Because, following those steps I've explained, the data is not arriving correctly. It's coming up with the old notification data....

> `getInitialNotification()` should not be updated because the app is just suspended, not killed. The app status is persisted. Are you still on the same page when you resume the...

I tested the emulator by following the suggested steps, but although the device was idle, the app was not killed by the system. So in this case yes, when I...