Why are my EAS Updates not working??

[njaah]

I seem to have huge challenges in using EAS Updates and I no longer understand why.

My SDK version is 47, EAS CLI is 3.4.0. This is managed workflow.
I have setup production branch that alos listens to channel production. We have a custom runtimeVersion set, currently to “48-4.1”.
My latest base app from stores is versioned 4.2.1 and listens to branch production, with runtimeVersion “48-4.1” (image attached). Now this happened:

1. I made a EAS update, with command eas update --branch production --channel production
2. Update goes through, my app prompts for update, everything works. (Version codes where updated in the release, runtimeVersion untouched)
3. I make another release, nothing happens anymore
4. I uninstall and redownload 4.2.1 from app store.
5. Even the update that was prompted for installation once, is no longer appearing.
   What is going on??

[njaah]

Iamge about 4.2.1, confirming that runtimeVersion is right.

[cdueck]

We don’t have a custom runtime version, but what you describe is the exact same thing that happened to me (EAS Updates not appearing due to 'Failed to download manifest from URL' error)

At first the update worked, then I did eas update again, and now the app won’t get any of the updates at all, and has fallen back to the app store version (I guess because of the error I mention in my thread) but I have no idea what’s causing it. This is a major problem.

[brents]

hi there!

have you tried following these guides?

• Debug EAS Update - Expo Documentation
• Advanced EAS Update Debugging - Expo Documentation

[cdueck]

See what worked for me below, maybe it will help you identify your problem as well:

EAS Updates not appearing due to 'Failed to download manifest from URL' error

We found our issue by checking the build logs for our most recently submitted build. For some unknown reason, the read app config step on the Android build showed that updates.url was missing. This was not the case on the iOS build (even though both builds were started at the same time, with the same config). We rebuilt and resubmitted the Android version to the store, and now the updates are working again.