Fix running ios tests in example project with dev flavor #2516
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
|
To view this pull requests documentation preview, visit the following URL: docs.page/leancodepl/patrol~2516 Documentation is deployed and generated using docs.page. |
github-actions
bot
added
the
package: patrol
piotruela
force-pushed
the
fix/example-dev-flavor-ios
branch
from
d03a731 to
7db1174
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.
This PR fix running iOS tests in example app using
devflavor.Before the fix, process was failing with
xcodebuild: error: Failed to build workspace Runner with scheme dev.: There are no test bundles available to test.error which was caused by multiple.xctestfiles generated fordevscheme upon building the tests.To fix that,
shouldAutocreateTestPlan = "YES"line was removed fromdev.xcschemefile.PR also contains other changes which were required in order to make project compatible with Flutter 3.27.0, but those changes were also introduced in #2510.