Hi! Sorry you’re having trouble with this. We’re looking into it, thankfully this doesn’t seem to be a widespread issue.
Edit: Looks like this is related to sending push notifications when running your project in a snack. If you are developing locally with expo-cli, you won’t hit this issue
Hi, I’m having the same exact issue as well. I was doing some testing yesterday and it was working fine. I tried doing it today and it kept failing and giving me the same error mentioned. I’m also using python exponent_server_sdk to send notifications to android devices. I also tried using the expo push notification tool and the same error was returned to me there as well.
Any help on this matter will be greatly appreciated
@charliecruzan I’m not sure what a snack is, i’m pretty new to using expo.
I used ‘expo init ’ to make the new project.
Then i use ‘expo start --tunnel’ to run the app on my phone via the expo application. The token is generated fine, and the notifications used to come through with no problems until i tried testing it today. I hope this answered your question
Yeah, looks like this will affect expo-cli projects as well, if you have never run expo publish for that project before. We think we’ve found the root cause and will be pushing out a fix soon, but as a temporary workaround, if you run expo publish, and then continue developing as you normally have (with expo start), push notifications should work again
Not sure if it is related but I cannot use the Expo Push notification tool either (Push Notification Tool — Expo).
Keep getting the error message below…
Just to confirm what @pjately078 said, the fix landed in production, so if you are still getting Internal Server Error responses in your push tickets or receipts, please let me know and we can figure it out