deps: Fix issues in Podfile.lock #148
Merged
Conversation
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
In f28dd0b, we upgraded the Dart package sqlite3_flutter_libs past simolus3/sqlite3.dart@c16721003, which bumped the version of the `sqlite3` pod published on CocoaPods (not to be confused with the Dart package with that same name on pub.dev). So in `flutter run` targeting an iOS device, the `pod install` step would fail with output including the following: ``` [!] CocoaPods could not find compatible versions for pod "sqlite3": In snapshot (Podfile.lock): sqlite3 (= 3.41.0, ~> 3.41.0) In Podfile: sqlite3_flutter_libs (from `.symlinks/plugins/sqlite3_flutter_libs/ios`) was resolved to 0.0.1, which depends on sqlite3 (~> 3.41.2) You have either: * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`. * changed the constraints of dependency `sqlite3` inside your development pod `sqlite3_flutter_libs`. You should run `pod update sqlite3` to apply changes you've made. ``` Flutter then gave its own output, along the lines of just that first bullet point: ``` Error: CocoaPods's specs repository is too out-of-date to satisfy dependencies. To update the CocoaPods specs, run: pod repo update Exception: Error running pod install ``` But actually, after studying both bullet points and trying their suggested fixes, it turns out the second one is right. So, follow it here by running `pod update sqlite3`. (Because I wrote this commit in my environment, the command also made a few unrelated changes that match changes that `pod install` has been wanting to make for me recently. I'll commit those changes separately, with an explanation, next.)
These changes happen in my environment when I run `pod install`, which I've just done for this commit. Greg's and my Podfile.lock were disagreeing about these checksums. It turns out they agree once one runs `flutter run` (for an iOS device), rather than just `pod install`. Discussion and diagnosis: zulip#92 (comment) [greg: added mention of `flutter run`]
|
Thanks! Looks good; merging. |
gnprice
force-pushed
the
pr-podfile-lock-fixes
branch
from
1ef429a to
61a23c3
Compare
This was referenced Jun 2, 2023
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.
Supersedes PRs #92 and #143.