-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
visionOS app fails to build with latest Sentry version, previously succeeded #3809
Comments
@sebj, I can reproduce the problem. Using |
I'm seeing the exact same error for my VisionOS builds 👀 |
I noticed that if you change @armcknight can you give us a hand with this? You've work with C++ longer than us. |
I'm currently investigating this. I was unable to reproduce the workaround mentioned by @philipphofmann , in my test app, of linking For the sake of comparison I created a test iOS app project with the same setup as the visionOS one, using SwiftUI, pulling in the Sentry SDK via SPM, validating that they have the same setting for Attached are the two projects I created to test. Digging in further, there are a few differences in the
Essentially, this is only in the iOS
and this is only in the visionOS one:
Maybe we need to add something to the |
I'm seeing the same thing. One thing I noticed is that the |
Having the same issue when building visionOS app |
Hello @vvbutko, have you tried using Sentry-Dynamic framework? |
@brustolin , yes, using |
We do plan to fix it. Btw, both frameworks are the same, one have static linking and the other one dynamic linking, so you're not loosing anything by using |
Platform
visionOS
Environment
Develop
Installed
Swift Package Manager
Version
8.22.4
Did it work on previous versions?
8.21.0
Steps to Reproduce
SentrySDK.start { .. }
(purely for testing purposes, I thew this intoonAppear
inContentView
in this fresh demo project)Expected Result
App builds and runs successfully on visionOS simulator
Actual Result
App fails to build and run on visionOS simulator.
Build errors:
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: