-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
React (0.11.0) is being added as a dependency for ios, creating conflicts. #925
Comments
Hmm that is interesting, I can't seem to reproduce this issue. But I'm on React Native version |
I'm also experiencing this, upgrading from But then when I do
And at the end, One interesting thing is that I successfully upgraded back in I think January, but then downgraded again because of the issue with native crashes not getting any context added. So it seems like this is probably a recently added issue, somehow. EDIT: I take back the part about it probably being recent, given that the dependency on React in the Sentry podspec has never changed. This only changes to my
and
EDIT: My conclusion here, is that, being on React Native 0.59.9, I don't want to use React* through CocoaPods, which means not using Sentry through CocoaPods (since it depends on React Native). However, sentry-react-native no longer appears to work when linked manually, because this commit removed the Sentry submodule inside |
Any updates on this issue? This is a huge block on our way to integrate sentry to our product. |
I was having the same problem with React Native 0.59.9. My Podfile had only Sentry and it was installing exactly as @benanderman described:
I had to manually add some lines in this podfile (for react and some dependencies) and everything worked fine. My
Even though things are working fine now with this change I don't think Sentry should be installing React 0.11. |
@pedroferreira1 I've already done that and unfortunately this doesn't work quite right. It builds and runs successfully but on start I am getting a popup that says "Warning, could not connect to Sentry native SDK...". |
@eyaydin do you see this popup here? Did you try this solution here #670 (comment)? It looks like a linking problem with your lib. My Podfile has some differences from yours. I've removed the |
Yes I've tried everything including #670 (comment) but didn't work. My podfile includes
|
Have you tried running pod repo update
# then
pod install ? This just looks like you guys have outdated repos because I've been investigating this and I don't see anything that could cause this on our side. |
@jennmueng Tried removing and reinstalling for pods, node modules, lock files multiple times but the issue persists. Its a huge blocker for months now. Also tried with latest sentry version for react native i.e 1.4.5. Please try creating and integrating sentry on react native 59.9 and below |
I have and haven't run into this issue before. It's definitely not an issue with the Here: sentry-react-native/RNSentry.podspec Line 18 in 638c843
Examples of this in Other Packages: I understand the frustration though, you can try manually setting the |
does not work. But I can confirm that adding React and related packages to podfile (which I shared here) and then removing the |
Ok I actually finally replicated this issue. This is caused by cocoa pods being unable to find the correct source for the pod 'React', :path => '../node_modules/react-native/' Also note that this line needs to be before any library (like Sentry) that depends on |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 1.4.5
react-native
version: 0.59.10Are you using Expo?
Are you using sentry.io or on-premise?
If you are using sentry.io, please post a link to your issue so we can take a look:
none
Configuration:
(
@sentry/react-native
)I have following issue:
After running
react-native link @sentry/react-native
andcd ios && pod install
, Podfile.lock has this content:Which is problematic since React 0.11.0 is too old to be supported. This creates a build error which is explained in #895 .
Steps to reproduce:
Actual result:
And at the same time, metro gives this error:
UnhandledPromiseRejectionWarning: Error: jest-haste-map: Haste module naming collision: Duplicate module name: react-native Paths: /Users/.../.../.../.../ios/Pods/React/package.json collides with /Users/.../.../.../.../node_modules/react-native/package.json
Expected result:
The app should work on Simulator.
What I have tried:
I wrote comments in #895 but since its a closed issue I am going to copy-paste here as well.
I changed RNSentry.podspec in @sentry/react-native to look for specifically my installed version of React. i.e:
s.dependency 'React'
tos.dependency 'React', '0.59.10'
. When I do this the Podfile.lock sees React and React related dependencies as 0.59.10. This approach successfully builds but fails when I try to run because of duplicate resources. i.e:Class RCTWebSocketModule is implemented in both /Users/.../Library/Developer/CoreSimulator/Devices/90D0534D-6CED-42AC-9B6E-218E2B603ABC/data/Containers/Bundle/Application/290ADA55-F4BB-4D47-86DD-D4352C218625/APPNAME/Frameworks/React.framework/React (0x102c44a30) and /Users/.../Library/Developer/CoreSimulator/Devices/90D0534D-6CED-42AC-9B6E-218E2B603ABC/data/Containers/Bundle/Application/290ADA55-F4BB-4D47-86DD-D4352C218625/APPNAME/APP (0x1025daab8). One of the two will be used. Which one is undefined.
I also tried some of the old versions of @sentry/react-native.
The text was updated successfully, but these errors were encountered: