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
#910 - not it, tried #880 leads to #503 where is the answer. Apparently, the docs got updated and no longer say to manually add pod 'OneSignal', '>= 2.6.2', '< 3.0' to Podfile
Description:
After following every required step in the installations docs
yarn add react-native-onesignal
cd ios && pod install && cd ..
and then adding required capabilities in Xcode, I was able to initialize the service, but pushToken from onIds was always null and Dashboard always showed APNS delegate never fired error. After traversing issues I found out that former docs included these lines.
That was not really straightforward and should be added back to the documentation.
Environment
Steps to Reproduce Issue:
(your steps here)
Anything else:
(crash stacktraces, as well as any other information here)
The text was updated successfully, but these errors were encountered:
@rgomezp yeah, it indeed is, but the section starts with this This step is optional but highly recommended. The OneSignalNotificationServiceExtension allows your application (in iOS) to receive rich notifications with images and/or buttons, along with Badges and advanced analytics like Outcomes.
This is the kind of the section you skip when you are going for the quick setup with minimal functionality and I think it shouldn't be marked optional if not following these steps screws the whole notification thing :)
#910 - not it, tried
#880 leads to #503 where is the answer. Apparently, the docs got updated and no longer say to manually add
pod 'OneSignal', '>= 2.6.2', '< 3.0'
to PodfileDescription:
After following every required step in the installations docs
and then adding required capabilities in Xcode, I was able to initialize the service, but pushToken from
onIds
was always null and Dashboard always showedAPNS delegate never fired
error. After traversing issues I found out that former docs included these lines.That was not really straightforward and should be added back to the documentation.
Environment
Steps to Reproduce Issue:
Anything else:
(crash stacktraces, as well as any other information here)
The text was updated successfully, but these errors were encountered: