[dash] Fix Android release tutorial to not break builds sans android/key.properties #1536
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.
The instructions at https://flutter.io/android-release/ currently have a significant deficiency: after an app's
android/app/build.gradle
has been modified following these instructions, it is no longer possible to build and run the app without having theandroid/key.properties
file present.On any development team where only one person acts as release manager, this breaks everybody else's checkouts and
flutter run
workflow. Moreover, while the fix may be relatively obvious (as per my patch), it wasn't obvious to at least one junior developer who got stuck on the problem for more than a day. It would be good to fix the documentation to eliminate this problem.Many (eventually all?) Flutter users run into this problem. The workaround is always the same: instructing others to edit their local
android/app/build.gradle
to comment out the keystore and release configuration. For example, from a quick google:I reproduce the error from
flutter run
below for the benefit of users googling how to fix this problem: