Will Schurman

> even though expo-updates supports different workflows, we could limit the team running `eas update` from the same workflow. that is exactly what `runtimeVersion={hasPrebuild}:{fingerprint}` for The issue there is that...

Seeing an issue with this where running an xcode release build multiple times in a row doesn't produce a consistent fingerprint. Will need to investigate.

@reichhartd - just curious, what library does this conflict with? FWIW, the dependency was removed during the swift conversion.

> When will the new version be published? Most likely not until the next SDK release since it will be a major release (lots of breaking changes for people using...

Reopening until released.

I believe this was released in [email protected].

My recommendation is to pass it to `getExpoPushTokenAsync` manually for now. This code is historically very fragile (as you found). You are correct that this isn't enumerating all the cases...

Taking another look at this, I'm hesitant to change the code to look in `extra` within `expoConfig`. For managed workflow, local development, and served updates, the project ID is put...

@RRaideRR - in this issue summary Environment report it says `Expo Workflow: bare`. EAS Build can build any project, including bare projects. What bare means is that the `android`/`ios` directories...

> I'm developing a local app NOT deployed using EAS. I'm also using SDK49. I received this error attempting to implement push notifications. I've never been aware of or configured...