My setup:
- Managed workflow
- eas-cli/0.54.1
- I’ve tested this scenario with a test app and I can’t find documentation supporting it
Hi,
I’ve been doing a test spike to assemble development and production setups for my new startup and came across a situation I’d need some clarification on.
I believe the easiest way to explain it is if I describe the steps and then finish with some questions.
Assumptions:
- I am running
eas build
andeas udpate
for a profile calledstaging
which has the propertychannel
with valuestaging
as well - I am NOT updating the runtime version between builds
Build 1:
- I run
eas build --profile staging
- On the EAS dashboard I’ll see a deployment with channel
staging
pointing at branchstaging
- Branch
staging
has no updates yet - Once I install this build on my phone all works as expected, the manifest that’s running on my device is the one embedded as there’s no update
- I open the app and see a blank screen
Update 1:
- I add a
Text
component to the intro screen sayinghello world
- I run
eas update --branch staging --message "foo"
- On the EAS dashboard I’ll now see that the branch
staging
has an update - Once I close and open the app installed on my phone I see the same blank screen but with the words
hello world
Build 2:
- I remove the
Text
component from the intro screen - I run
eas build --profile staging
- On the EAS dashboard I see that the staging deployment as a newer build but I still see that it points to the Update 1 with message
foo
- When I install this build 2 it won’t download the update
- I open the app and see a blank screen
I’m not saying this is not desirable behaviour. I’d say that if the manifest that’s embedded in the build is more recent than the last update that’s the one that should be picked up.
However on the dashboard and by looking at the relationship between the channel and the branch it’s confusing because I don’t know if my latest build will use the embedded manifest or if it will pick-up the latest update.
You can see this on the screenshot below:
- Even though it looks like my latest build is using the update
Updating the app test 4
in reality it doesn’t seem to be as it’s showing me the embedded manifest
Would anyone with some experience be able to share their thoughts? Anyone came accross this?
Thanks in advance,
Miguel