Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to ably-cocoa v.1.2.8 #293

Merged
merged 1 commit into from
Jan 14, 2022
Merged

Conversation

QuintinWillison
Copy link
Contributor

This involved (some steps may have not been required):

  1. Modifying version in ios/ably_flutter.podspec
  2. flutter clean from root
  3. flutter pub get from root
  4. flutter pub get from example/
  5. flutter pub get from test_integration/
  6. pod repo update
  7. pod update Ably && pod install from example/ios, updating Podfile.lock in that folder
  8. pod update Ably && pod install from test_integration/ios, updating Podfile.lock in that folder

Fixes #287

This involved (some steps may have not been required):
1. Modifying version in `ios/ably_flutter.podspec`
2. `flutter clean` from root
3. `flutter pub get` from root
4. `flutter pub get` from `example/`
5. `flutter pub get` from `test_integration/`
6. `pod repo update`
7. `pod update Ably && pod install` from `example/ios`, updating `Podfile.lock` in that folder
8. `pod update Ably && pod install` from `test_integration/ios`, updating `Podfile.lock` in that folder
@QuintinWillison QuintinWillison merged commit 87b9c3d into main Jan 14, 2022
@QuintinWillison QuintinWillison deleted the feature/ably-cocoa-1.2.8 branch January 14, 2022 10:57
QuintinWillison added a commit that referenced this pull request Jan 20, 2022
I tried to follow the steps that had worked for me a few days ago, as detailed in the opening comment here:
#293

However, I got some odd CocoaPods errors. I ended up following these instructions (it's `trunk`) which got me there for the example directory but was still failing for test_integration:
https://stackoverflow.com/a/34526412/392847

So, I ended up picking the changes that the pod tool had applied to the lock file in the example directory and manually transferring those over to the test_integration lock file.
Not ideal - so there's more to be understood here as this is not sustainable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Push device registration does not clear/reset device details on iOS
3 participants