You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Done with the following command:
yarn upgrade -- $(tools/deps | grep sentry) && yarn yarn-deduplicate && yarn
(See discussion [0].)
When `pod install` ran from the postinstall script, I got this
error:
```
[!] CocoaPods could not find compatible versions for pod "Sentry":
In snapshot (Podfile.lock):
Sentry (= 4.4.3, ~> 4.4.0)
In Podfile:
RNSentry (from `../node_modules/@sentry/react-native`) was resolved to 1.6.3, which depends on
Sentry (~> 5.1.8)
Specs satisfying the `Sentry (= 4.4.3, ~> 4.4.0), Sentry (~> 5.1.8)` dependency were found, but they required a higher minimum deployment target.
```
Just running `pod update RNSentry` was enough to let `pod install`
run without errors the next time. I didn't pin down precisely what
the reported change in minimum deployment target was. In fact,
between 4.4.0 and 5.1.8 of Sentry, I don't see *any* change to
`s.ios.deployment_target` in the Podspec file [1] that gets
processed and hosted by CocoaPods as JSON, nor did I see changes to
`platforms.ios` in the JSON itself [2] [3].
But the current Podspec there has "8.0" for that value, which is
quite safe, as our deployment target (project > ZulipMobile > Info
in Xcode) is 10.3, and in any case, it works.
The idea to run `pod update RNSentry` came from a comment [4] on
CocoaPods/CocoaPods#4373.
[0] https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/changes.20in.20generatedEs3.2Ejs/near/935892
[1] getsentry/sentry-cocoa@4.4.0...5.1.8#diff-90b813c6043692fcb10d7f0efa7cbf19
[2] https://github.com/CocoaPods/Specs/blob/master/Specs/a/b/d/Sentry/4.4.0/Sentry.podspec.json
[3] https://github.com/CocoaPods/Specs/blob/master/Specs/a/b/d/Sentry/5.1.8/Sentry.podspec.json
[4] CocoaPods/CocoaPods#4373 (comment)
0 commit comments