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
I have observed that even after explicitly setting the parameter to false in the method call OneSignal.Notifications.requestPermission(false);, iOS still presents a fallback alert. Additionally, the function returns an array that contains a boolean value on iOS, instead of returning a boolean value directly.
Everything is working correctly on Android as per the documentation.
1. Request permission in the following way: `const result = await OneSignal.Notifications.requestPermission(false);`2. Cancel the permission access
3. Observe a fallback alert that points to the Settings app
4. Observe the `result` type is Array on iOS
What did you expect to happen?
Not present the fallback alert if I call the function with false value. Also, the return value should be boolean on iOS as well
React Native OneSignal SDK version
5.1.0
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:
What happened?
I have observed that even after explicitly setting the parameter to
false
in the method callOneSignal.Notifications.requestPermission(false);
, iOS still presents a fallback alert. Additionally, the function returns an array that contains a boolean value on iOS, instead of returning a boolean value directly.Everything is working correctly on Android as per the documentation.
Versions:
react-native-onesignal: 5.1.0
OneSignalXCFramework: 5.1.3
Steps to reproduce?
What did you expect to happen?
Not present the fallback alert if I call the function with
false
value. Also, the return value should be boolean on iOS as wellReact Native OneSignal SDK version
5.1.0
Which platform(s) are affected?
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: