Remove the byte-order mark from pubspec.yaml - #15
Merged
Merged
Conversation
A UTF-8 BOM at the start of pubspec.yaml makes pub fail before it reads
the file ("Missing the required 'name' field"), so every app that
depends on this package from git could no longer resolve dependencies.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
pubspec.yamlon main starts with a UTF-8 BOM (ef bb bf), introduced with the file_picker 12 bump.pubrejects the file before parsing it ("Missing the required name field"), so any app depending on this package via gitref: maincan no longer runflutter pub get.Verified locally:
flutter pub getresolves,flutter analyzereports 0 errors / 0 warnings (91 pre-existing infos),flutter testpasses.