-
-
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
Version 2.0.0 not building with use_frameworks #1171
Labels
Comments
6 tasks
5 tasks
The fix has been introduced in this PR to |
Looking forward to the update! |
philipphofmann
added a commit
to getsentry/sentry-cocoa
that referenced
this issue
Nov 9, 2020
Hybrid SDKs as react-native need a way to synchronously store an envelope to disk. Previously, this was possible by exposing SentryFileManager on the SentryClient, but this breaks users of react-native that use use_frameworks!, see getsentry/sentry-react-native#1171. A way to fix this would be to expose SentryFileManager and SentryCurrentDateProvider as proposed in #835. This has the downside of making classes public, that shouldn't be public. A better workaround is to expose storeEnvelope on the SentryClient.
philipphofmann
added a commit
to getsentry/sentry-cocoa
that referenced
this issue
Nov 9, 2020
Hybrid SDKs as react-native need a way to synchronously store an envelope to disk. Previously, this was possible by exposing SentryFileManager on the SentryClient, but this breaks users of react-native that use use_frameworks!, see getsentry/sentry-react-native#1171. A way to fix this would be to expose SentryFileManager and SentryCurrentDateProvider as proposed in #835. This has the downside of making classes public, that shouldn't be public. A better workaround is to expose storeEnvelope on the SentryClient.
5 tasks
philipphofmann
added a commit
to getsentry/sentry-cocoa
that referenced
this issue
Nov 10, 2020
Hybrid SDKs as react-native need a way to synchronously store an envelope to disk. Previously, this was possible by exposing SentryFileManager on the SentryClient, but this breaks users of react-native that use use_frameworks!, see getsentry/sentry-react-native#1171. A way to fix this would be to expose SentryFileManager and SentryCurrentDateProvider as proposed in #835. This has the downside of making classes public, that shouldn't be public. A better workaround is to expose storeEnvelope on the SentryClient.
8 tasks
This issue has been fixed in version 2.0.1. Please upgrade and don't forget to run |
Thanks @jennmueng ! Works well now 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 2.0.0
react-native
version: 0.63.3Are 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:
Not relevant
Configuration:
Not relevant
I have following issue:
When using
use_frameworks!
in the Podfile, I can't build RNSentry and get the following error:Steps to reproduce:
react-native init TestSentry
use_frameworks!
in Podfile (which producesThe 'Pods-TestSentry' target has transitive dependencies that include statically linked binaries
error when runningpod install
)pod install
work:Actual result:
Getting this error:
'Sentry/SentryFileManager.h' file not found
when building the appPerhaps should the file be added into this folder on
sentry-cocoa
? https://github.com/getsentry/sentry-cocoa/tree/master/Sources/Sentry/PublicPrevious version of the SDK is building fine however
Expected result:
The app should bulld
The text was updated successfully, but these errors were encountered: