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
On iOS I can call canRequestPermission and it will return true if the device has not yet been prompted for notification permission. If the device has been previously prompted, it will return false. On an Android 13 device it always returns true even if the user has previously been prompted, rendering it useless. This means we have logic around this function that works on iOS and fails on Android.
Steps to reproduce?
Call `canRequestPermission` on a newly installed app - it returns `true`
Call `requestPermission(true)` and you will get the native prompt to allow permission
Call `canRequestPermission` again. Instead of returning `false` it continues to return `true`
What did you expect to happen?
It should work as documented and as it does in iOS
OneSignal Cordova SDK version
5.0.4
Which platform(s) are affected?
iOS
Android
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Actually it seems to continue to return true UNLESS, when you respond to the prompt, you click Allow. Then the canRequestPermission will return false. So it is different behavior to iOS but possibly expected?
What happened?
On iOS I can call
canRequestPermission
and it will returntrue
if the device has not yet been prompted for notification permission. If the device has been previously prompted, it will returnfalse
. On an Android 13 device it always returnstrue
even if the user has previously been prompted, rendering it useless. This means we have logic around this function that works on iOS and fails on Android.Steps to reproduce?
What did you expect to happen?
It should work as documented and as it does in iOS
OneSignal Cordova SDK version
5.0.4
Which platform(s) are affected?
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: