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
First of all I apologize if the title of my post is not clear... I'll try to explain better.
I'm developing an Android app and I have two devices... one with Android10 and the other with Android13.
The project is unique for both and I notice that when the app is closed and I touch the push message that arrived in the background on the status bar the plugin opens the app correctly, but while Android 10 shows the app icon Android 13 does not.
Some idea?
The text was updated successfully, but these errors were encountered:
FranGhe
changed the title
Android13 - Start App without logo on tap to background messaging when the app is close
Android13 - Start App without logo on tap to background messaging
May 10, 2024
I'm experiencing the same issue in my Cordova Android build, on a Samsung device, running Android 14. This doesn't seem to occur on a Cordova iOS build.
Cordova setup:
cordova -v (12.0.0)
cordova-android (13.0.0)
cordova-plugin-firebasex (16.5.0)
My specific scenario occurs when clicking through on a push notification, when the Android app is closed/task killed. In this instance, I only see the splash screen background on app launch, not the splash screen icon. With cordova-android 13 using the Android 12+ core splash screen functionality, not the cordova splashscreen plugin, I suspect it might be related to the new splashscreen implementation.
First of all I apologize if the title of my post is not clear... I'll try to explain better.
I'm developing an Android app and I have two devices... one with Android10 and the other with Android13.
The project is unique for both and I notice that when the app is closed and I touch the push message that arrived in the background on the status bar the plugin opens the app correctly, but while Android 10 shows the app icon Android 13 does not.
Some idea?
The text was updated successfully, but these errors were encountered: