Hi!
Since using MABS 9 our Android 13 endusers can't receive notifications anymore. This is because Google decided to make pushnotifications an opt-in model in Android 13. Unfortunatly our users are not able to opt-in because it seems there is some configuration missing in the manifest.xml. As far as we understand we are not able to update the manifest.xml to add the missing configuration.
Anyone else having the same issues? (and better fixed them already?) Did we miss something?
Thanks,Willem
Hi Willem,
To test the push notifications Mobile App, I used the "FireBase Mobile Sample" application on the forge to test it. I'm using MABS 9.
After lunching the app on Android 13, i can't see it on notifications application settings and the notifications doesn't work. the application works fine on android 12 device.
Did you find a solution?
Thanks,
Mehdi
Hi Mehdi,
I have the same issue with Android 13, did you find any solution?
thanks,
Pier Paolo
Hi Pier,
we resolved the issue by using the OneSignal Pluging that is supported by outsystems.
Regards,
Hello all
In my current project, our Cordova team ended up developing a plugin that checks if the user already granted permissions for push notifications and, if not, triggers the Android built-in popup that requests those permissions
This popup is only triggered for Android 13 devices. In Android 12 it does not show because the user can toggle the notifications on in the device's settings
Hi Ângelo,
thanks for your answer.
Is this Cordova plugin available to everyone?
We've installed this plugin.
This will add some missing configs.
With this plugin in the app settings, we correctly see the Notify option but it is blocked by default. In addition, the functionality of the plugin to request permission always returns true even if the permission in the setting is blocked and the Android built-in popup doesn't open it to trigger it.