-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Apns Delegate Never Fired" status when OneSignal in the abstract_target in a Podfile #180
Comments
+1 This happens for me without the abstract_target thing. Using the 2.3.5 version. |
Switched back to 2.1.6 and everything works again. |
@RazvanPaul Could you share your Thanks. |
@RazvanPaul Fixed a This was fixed in commit 9f51c12 and will be included in the next release. Additionally, the a 3rd possible way the |
@RazvanPaul The commit noted above was released in 2.3.6. Can you try our latest 2.4.2 SDK to see if you still have this issue? |
@RazvanPaul I have made a number of changes in our 2.5.0 SDK around handling the current subscribed state and added a number of unit tests to ensure we are not reporting an inaccurate subscription state. Let us know if you continue to see an issue after updating to the 2.5.1 SDK. Thanks. |
I am using Ionic with Capacitor on the latest versions, I had configured wrongly the steps, I did everything from beginning but slowly and reading everything as the documentation was saying. Now it is working. |
Edit
Issue was not related to
abstract_target
, it was related to a bug in the OneSignal-iOS-SDK 2.5.0 and was fixed in 2.5.1.#180 (comment)
Issue
Devices will have a "Apns Delegate Never Fired" status on the All Users page on the OneSignal dashboard when OneSignal is in the
abstract_target
in aPodfile
. They may only happen when it also contains library project that gets embed into the app.Changing the
Podspec
like this fixes the issue.The text was updated successfully, but these errors were encountered: