Conversation
|
We want this feature to also work on Maestro Cloud - so we must enforce the app binary to be inside Maestro workspace folder. |
If I understand correctly, we already make it enforced. @bartekpacia
|
|
The pipeline got an error, there seems to be no authentication key, but idk why |
|
Don't worry about the pipeline, it's expected. It only fails for external contributors, and it's okay, because we don't want to expose our backend secret key to external people. |
|
I see, shall we merge it as it is? |
|
Let's also add docs for this new command in |
|
re: this It's only checking if the app file exists, right? But it has to be inside Maestro workspace folder (together with all your flows, etc), so that when it's uploaded to Maestro Cloud (MC), it can work there as well. If the app file is outside the Maestro workspace folder, it won't get uploaded and the flow will fail on MC. |
|
All done 🥳 @bartekpacia |
bartekpacia
left a comment
There was a problem hiding this comment.
Overall this LGTM, but I'm holding off because there are some concerns internally.
|
Het @boranfrkn, we like this feature and will merge the PR soon, but first we need to make some changes to our backend platform. Tentative plan is to release this in Maestro v1.39. Thanks for understanding and sorry about the delay! |
4d1155c to
f0965b2
Compare
…ndroidApp # Conflicts: # maestro-orchestra/src/main/java/maestro/orchestra/yaml/YamlFluentCommand.kt # maestro-test/src/test/kotlin/maestro/test/IntegrationTest.kt
|
I see, thanks a lot Bartek. its passed 👍 |
|
Hey @Fishbowler any update here? |
|
You only merged the change a few minutes ago, give us a chance! 😂 |

Proposed changes
Added “installApp” command.
Testing
Issues fixed
Resolve #1665