-
Notifications
You must be signed in to change notification settings - Fork 53
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]: No push token generated via eas build #229
Comments
@szbphoto are you seeing a subscription in the OneSignal dashboard? If so what "Subscription Status" does it show? Are you only seeing this issue with iOS? Are Android pushes working for you? |
@jkasten2 i don't see anything on the onesignal dashboard since if i want to add a new project then i have to create a push token first but since it doesnt generated i cannot create totally the project on the onesignal. I have this issue with iOS since only iOS requires push token |
@szbphoto it sounds like you are talking about a push certificate / push key instead of a device push token. So for these there was originally only a .p12 push keys / certificates which you needed one for every app. There is now a new .p8 push keys / certificates which I think EAS Build defaults to now. The .p8 works for all of your iOS apps under your developer account so .p8 are recommend of using the older .p12. |
Closing due to inactivity |
What happened?
I tried to build a new app with expo and onesignal, i already made 10+ apps with expo + onesignal and each time at the first build expo asks me if i want to generate push token for this project, so i did the exactly same then i did in the past. But for now theres no push token generated for my project and I canno't see any update in the documentation on the onesginal site and neither on the expo site.
Steps to reproduce?
What did you expect to happen?
In the last step i should see a question just like earlier where it asks me to if i want to generate push token for this project
OneSignal Expo SDK version
2.0.2
Platform
iOS
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: