-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Utilize xcworkspace in addition to Podfile for Cocoapods detection #20486
Comments
This comment has been minimized.
This comment has been minimized.
Removing old version label as this is unlikely to have been fixed in 0.56. |
I am closing this issue because it does not appear to have been verified on the latest release, and there has been no followup in a while. If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue with up-to-date information by clicking here. |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Environment
Description
Let me preface this with: I have no idea what I'm doing. Hadn't touched RN before earlier this week.
I had a Podfile present in my path (I was intending to use it in the future), and RN's linker seems to utilize that to detect if we're using Cocoapods or not.
This caused errors such as the following from
react-native-sentry
:I ultimately discovered that it had modified the Podfile and was expecting the dependencies to be linked from Cocoapods. After doing unlink on the modules, renaming the Podfile, and re-linking them, my project was able to successfully compile.
The text was updated successfully, but these errors were encountered: