-
Notifications
You must be signed in to change notification settings - Fork 52
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
[Bug]: Not receiving Push Notifications on iOS #199
Comments
I have the same problem |
Did anyone ever figure this out? |
Same here |
Same here! In app notification works fine. But the push notification isn't working |
Same exact issue. Verbose logs don’t show anything. Devices seem to be registering fine as well. I’m not used to using p8 key for setup but it should work for both sandbox and production. I’m not clear when OneSignal uses one over the other though (what is it looking at to differentiate?) |
For reference. Testing with the simple code below correctly sends and receives a notification so it seems the app setup is correct. I encourage everybody to try the same
|
Hello everyone! Apologies that this issue has gone stale. Please upgrade to the latest version of our SDK and open a new issue if you are still having trouble. Thanks! |
What happened?
I followed this guide for setting up my project with OneSignal for notifications but I'm not receiving any notifications at all for my build I pushed to iOS. I feel like I set up everything correctly and have the correct .p8 certificate that's integrated with Expo and my developer account on Apple but I'm always seeing the same Failed error below. Anyone else run into any issues like this? I've tried working with the Support team at OneSignal but so far no luck and it's usually hours before they respond to my questions. Thanks again!
Steps to reproduce?
What did you expect to happen?
I expected to receive a push notification on my device with the content I sent out from the OneSignal dashboard
OneSignal Expo SDK version
2.0.0
Platform
iOS
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: