-
-
Notifications
You must be signed in to change notification settings - Fork 337
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
xcode: Upload Debug Symbols to Sentry has ambiguos dependencies #3537
Comments
@Yonom This is appears to be causing builds to fail during |
My EAS builds work just fine despite the warning |
Thanks for the quick response. I noticed this upgrading from 49 to 50 and following their migration guide. My issue appears to be sentry related and I was seeing the warning as well.
|
@Yonom Thank you for the message, we will update the build phase to remove the warning. Note: We want it to run on every build, so the current behavior is correct. Just the script is not correctly marked in Xcode. |
@iM-GeeKy Can you open a new issue for the Android build failure and if possible share a large portion of the build log output? |
Sure thing, I'll do that in a couple of hours when I'm back at my laptop. The issue appeared to be happening on iOS and Android. I'm make sure to attach as much of the build log as possible. |
This is not the reason the build is failing, if you scroll up in your logs you should see the actual failure reason. This is just outputted at the bottom of the Fastlane log output. It does not cause the build to fail. |
This needs to be updated in the |
We are running into this issue as well using Expo. We have a Error
Dependencies
Is there anyway to resolve this? |
@drewbietron Thank you for the message, this is only a warning, we will fix it soon. Let us know if your build is failing, as that would be caused by something else. |
@krystofwoldrich thanks for the quick reply. This is actually making our builds fail |
@drewbietron Thank you for the extra logs, can you add This seems to be an example of an issue we recently closed, can you post the new logs there and we can reopen it. Does it happen only in CI or also when you try the build locally? |
@krystofwoldrich It is only happening when building in Expo. When I run the app locally I can send errors to Sentry and see the source. The xcode logs are actually giving a 401
|
@drewbietron Thank you for the log, I checked and see all your tokens were used at least once. When you check When running the app locally have you tried to build the Release version, using Expo Go the debug files are not uploaded. You can try running only the upload command to verify the token. https://docs.sentry.io/product/cli/dif/#uploading-files |
@krystofwoldrich turns out I had a token set in project secrets and account wide secrets in or Expo account, and the project environment variable was outdated. Appreciate your response on this, everything works as expected after using the correct token. 🙇 |
@drewbietron Happy to hear that, everything works now! |
I was getting the error message for local builds. What was not obvious to me, is that you need to have the Sentry auth token set locally as well: In my case, I created a
Note in the instructions, you can also use the |
@chrisl777 If you only build a Release version of your application in CI, then you don't have to have the token set locally. If you want to build Release locally without uploading debug files to Sentry you can use https://docs.sentry.io/platforms/react-native/manual-setup/manual-setup/ |
Maybe this information will help someone as well: |
Unfortunately, [RUN_FASTLANE] ⚠️ Script has ambiguous dependencies causing it to run on every build.
To fix, go to: Xcode » Pods/abseil » Build Phases » 'Create Symlinks to Header Folders'
Either: Uncheck "Based on dependency analysis", or select output files to trigger the script
[RUN_FASTLANE] ⚠️ Script has ambiguous dependencies causing it to run on every build.
To fix, go to: Xcode » Ponder/Ponder » Build Phases » 'Upload Debug Symbols to Sentry'
Either: Uncheck "Based on dependency analysis", or select output files to trigger the script
[RUN_FASTLANE] ⚠️ Script has ambiguous dependencies causing it to run on every build.
To fix, go to: Xcode » Ponder/Ponder » Build Phases » '[CP-User] [RNFB] Core Configuration'
Either: Uncheck "Based on dependency analysis", or select output files to trigger the script |
Hi @olddustysocksunderthecouch,
|
Hey all! I got this to work. I found that even though I already have the I hope this helps. |
This has been happening to me today. I have my I have checked the Sentry status page and all is green. Not really sure what to do from here. |
I eventually found the issue with my build! Hidden in the Xcode Logs output was a problem with the iOS distribution certificates and provisioning profiles. I deleted all of them locally (key chain) and on Apple Developers. I then recreated them with I wish the error message had been more obvious and easier to discover! Not finding it made me think poorly of Sentry because its warnings were outputted last in the build output, and I had to hunt through Xcode logs of a local iOS build instead. Weirdly, one of the Cloud eas builds succeeded, and another didn't indicate any issues, even in the Xcode logs. This prompted me to try building it locally (see these docs). You'll also need to set Anyway, I hope this helps some one. |
Yeah I found my problem also it was a PrivacyInfo.xcprivacy duplication issue |
@zlanich Could you share how your set the |
@olddustysocksunderthecouch Thank you for the update, happy to hear that you find it and that it was not Sentry. I feel with you, the Xcode logs are difficult to navigate. |
@TreeMan360 Anything we can help with? Or was it unrelated to Sentry? |
I am seeing this warning as well. However, it's not preventing us from building the app. But our We recently upgraded to Expo 50 and also did the migration from sentry-expo to the sentry react native package. |
Hi @avogel3, Could you open a new issue with details about the bundle and the source map? Could you include what do you see in Sentry, it the bundle 0 bytes or missing? Could you include Xcode log from |
@krystofwoldrich Yeah, of course. Appreciate the fast response! 🤝 |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 5.16.0
react-native
version: 0.73.2Are you using Expo?
Are you using sentry.io or on-premise?
I have the following issue:
During build, I see a warning regarding an ambiguous dependency. I am using the
"@sentry/react-native/expo"
config plugin.Steps to reproduce:
npx expo run ios
and observe the logsActual result:
I see the following warning:
Expected result:
I expected no warnings.
The text was updated successfully, but these errors were encountered: