Replies: 3 comments
-
This is a refinement of the closed-but-not-resolved ticket #2999 |
Beta Was this translation helpful? Give feedback.
-
ANSWER: The curl command was sending in a workflow ID that had been set up via the Workflow Editor. I foolishly thought that specifying via web interface that I wanted to use the codemagic.yaml file would invalidate the previously-existing workflow IDs - so if I tried to initiate a build with a deactivated workflow ID, that the build process would fail immediately. UNFORTUNATELY, the build process is quite happy to use the GUI-apparently-disabled workflow ID to do a build - and hence a obsolete flutter version was used. MORAL: Do not trust CodeMagic's GUI when it says use codemagic.yaml when you are using the CURL API interface. |
Beta Was this translation helpful? Give feedback.
-
This error explains #2999 as well as this ticket! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
If you are looking for help, please confirm the following...
Which mobile framework are you using?
Flutter (Dart)
Steps to reproduce
Expected results
If step 10 succeeds, I would expect step 8 to also succeed.
Actual results
In our project (with the second build kicked off next after the failing build specified with the build ID below), the first, curl-API-initiated build failed with an incorrect Flutter version.
NOT ONLY THAT, BUT THE CODEMAGIC.YAML FILE THAT IS INSIDE OUR SOURCE CODE WITH SHA bcafe32 WAS NOT PROPERLY LOADED INTO OUR BUILD LABELED AS "Production Workflow #85" - as there is no "Production Workflow" labeled workflow in our codemagic.yaml file in SHA bcafe32!
Starting the SAME repository, same branch, same workflow via the CodeMagic web GUI produced the "iOS Production Workflow #7" -- a build that succeeded.
I changed the workflow label in our source code with SHA bcafe32 - but somehow the CodeMagic build pulled stale source code, but reported that the proper code branch and commit had been pulled in our build labeled "Production Workflow #85"
I have included the Build ID of the failing "flutter-app: Production Workflow #85" in this ticket.
WHAT THE HECK IS GOING ON?
Build id (optional)
67ce10618ea7520a328335c3
Beta Was this translation helpful? Give feedback.
All reactions