-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
ciContinuous integration issues, workflows, or build pipeline problems.Continuous integration issues, workflows, or build pipeline problems.
Description
This is the same issue as flutter/flutter#174205. Duplicated to keep track of it on this repo and make it clear that running flutter pub get inside the kraft_launcher app package first is required before running flutter pub get at the workspace level.
Current workaround in CI:
kraft-launcher/.github/actions/setup-flutter/action.yml
Lines 13 to 26 in cd0f4d4
| # Workaround for localization generation issue (https://github.com/flutter/flutter/issues/174205): | |
| # Running "flutter pub get" at the root workspace normally triggers: | |
| # | |
| # Generating synthetic localizations package failed with 1 error: | |
| # PathNotFoundException: Cannot open file, path = 'l10n/untranslated.json' | |
| # (OS Error: No such file or directory, errno = 2) | |
| # | |
| # This happens when the "untranslated-messages-file" is set in | |
| # "kraft_launcher/l10n.yaml" and the root-level "flutter pub get" runs | |
| # before the app-level package. | |
| # | |
| # To avoid this, we first run "flutter pub get" in the app package directory, | |
| # then run it at the root workspace level. | |
| run: (cd kraft_launcher && flutter pub get) && flutter pub get |
Metadata
Metadata
Assignees
Labels
ciContinuous integration issues, workflows, or build pipeline problems.Continuous integration issues, workflows, or build pipeline problems.