Fix Maestro iOS tests #24
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aaalaniz
force-pushed
the
task/fix-maestro-ios
branch
from
dbfac2b
to
660958f
Compare
aaalaniz
changed the title
aaalaniz
force-pushed
the
task/fix-maestro-ios
branch
from
67adbf3
to
10bbaae
Compare
These changes represent a collection of debugging focused steps to fix the runtime crash that occurred in the Maestro iOS tests after updating the project to Kotlin 2.0 Ultimately, the issue ended up being a chicken-or-egg issue related to compose resources not being installed into the final iOS app.
aaalaniz
changed the title
aaalaniz
force-pushed
the
task/fix-maestro-ios
branch
from
b837882
to
277ab00
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes represent a collection of debugging focused steps to fix the runtime crash that occurred in the Maestro iOS tests after updating the project to Kotlin 2.0
Ultimately, the issue ended up being a chicken-or-egg issue related to compose resources not being installed into the final iOS app.