Hi @vladimir-upirov, I just notice the notification is not being able to trigger the App (Android) anymore. I’m receiving the notifications with App open, closed and in Background. But when I tap on the notification bar it just closes the top bar without triggering the App even when the App is in the background it does not bring it to the foreground.
If I tap in the notification with the App in the foreground now it crashes the App.
Could you please confirm this behavior? If this might be related to RN or Android? Regards
Hi @vladimir-upirov I couldn’t sorted-out what’s making the Android app closes after try to open from a notification yet. I check your android files and couldn’t find any specific or different configuration for backendless-react-native.
I was able to run the project on simulator only, couldn’t test the notifications, got an error on the device that I can’t resolve. Does not run on my devices (S9+, J6), did not test on iPhone.
The new project does not contain any dependencies (just backendless-react-native), we don’t need the followed dependencies anymore?
I was able to run the project on simulator only, couldn’t test the notifications, got an error on the device that I can’t resolve. Does not run on my devices (S9+, J6), did not test on iPhone.
do you run simulator and real device at the same time? did you try to restart metro-builder and click to “reload JS” button on the device?
could you please provide steps to how you run your app, I use this way:
Hi @vladimir-upirov I just use the Android Studio to Sync project with Gradle files and open AVD Manager to start one emulator. From this point forward I can just run react-native run-android from VS Code, it will emulate the .apk in all devices available (emulators and devices).
Since I’m working with notifications I’m using real devices directly not emulators. Real devices are also faster some times.
Use again AS to profile, debug the APK to check after assemble the Release.
