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
[question]: APNS Delegate Never Fired #1484
Comments
We have the same problem in production. It is really hard to track down the problem, as there is no consistency to what devices and iOS Versions are affected by this. It seems to be a problem with about 50% of installs. |
Did you find any solution to this? |
Seeing a high volume of subscribers with the same issue |
Hello everyone! Apologies that this issue has gone stale. "APNS Delegate Never Fired" is a timeout message for when iOS doesn't fire a success or failure message if a connection is not made to Apple's APNS servers. We have a comprehensive guide here that covers troubleshooting steps. Since it has been some time since this issue has seen any activity, I'm going to close it out. However, if anyone is still having trouble with this on our latest SDK version, please open a new issue and we will be happy to assist! Thanks! |
How can we help?
Hello,
I'm running into the "APNS Delegate Never Fired" issue and banging my head up against the wall trying to solve it. I'm running the app in the Simulator - the device is iPhone 14 Pro running iOS 16.2
On the OneSignal Settings page, I see this when I click Checked Subscribed Users:
As far as I know, I do not have any installed. I previously had
react-native-permissions
installed (I need to access the microphone in my app, and used it for that). I removed it to ensure its notifications permissions functionality was not causing a conflict. No difference.In my podfile, sibling to my app's target, I have:
In my index.js:
Verbose log output:
My certificates with Apple were regenerated today, and expire over a year from now. They are Production and Sandbox certificates.
Versions:
Thanks,
Will
Code of Conduct
The text was updated successfully, but these errors were encountered: