-
-
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
RNSentry.m:64:38: too many arguments to block call, expected 1, have 3 #895
Comments
have you solved it?Thanks |
@JetCyC not yet. |
@takagisou This issue seems very odd, react-native changed the signature of this function 4 years ago. Are you using any other library that patches this? |
@JetCyC I want to remind you about our CoC https://github.com/getsentry/.github/blob/master/CODE_OF_CONDUCT.md |
@HazAT
I'm not sure because I recently joined the ReactNative project. I'm using "react-native-sentry": "0.42.0" and it happened during the transition to "@sentry/react-native" with the following reference. https://docs.sentry.io/platforms/react-native/ I will do a little more research. |
@takagisou I really don't understand, we are using this reject method it has 3 arguments and this is the reference to version |
I'm not very familiar with ReactNative... React Native version as follow. $ react-native -v
react-native-cli: 2.0.1
react-native: 0.59.10 Podfile.lock PODS:
- GoogleSignIn (4.3.0):
- "GoogleToolboxForMac/NSDictionary+URLArguments (~> 2.1)"
- "GoogleToolboxForMac/NSString+URLArguments (~> 2.1)"
- GTMOAuth2 (~> 1.0)
- GTMSessionFetcher/Core (~> 1.1)
- GoogleToolboxForMac/DebugUtils (2.2.1):
- GoogleToolboxForMac/Defines (= 2.2.1)
- GoogleToolboxForMac/Defines (2.2.1)
- "GoogleToolboxForMac/NSDictionary+URLArguments (2.2.1)":
- GoogleToolboxForMac/DebugUtils (= 2.2.1)
- GoogleToolboxForMac/Defines (= 2.2.1)
- "GoogleToolboxForMac/NSString+URLArguments (= 2.2.1)"
- "GoogleToolboxForMac/NSString+URLArguments (2.2.1)"
- GTMOAuth2 (1.1.6):
- GTMSessionFetcher (~> 1.1)
- GTMSessionFetcher (1.2.2):
- GTMSessionFetcher/Full (= 1.2.2)
- GTMSessionFetcher/Core (1.2.2)
- GTMSessionFetcher/Full (1.2.2):
- GTMSessionFetcher/Core (= 1.2.2)
- React (0.11.0):
- React/Core (= 0.11.0)
- React/Core (0.11.0)
- RNSentry (1.4.2):
- React
- Sentry (~> 5.1.1)
- Sentry (5.1.1):
- Sentry/Core (= 5.1.1)
- Sentry/Core (5.1.1)
DEPENDENCIES:
- GoogleSignIn (~> 4.3.0)
- "RNSentry (from `../node_modules/@sentry/react-native`)"
SPEC REPOS:
https://github.com/CocoaPods/Specs.git:
- GoogleSignIn
- GoogleToolboxForMac
- GTMOAuth2
- GTMSessionFetcher
trunk:
- React
- Sentry
EXTERNAL SOURCES:
RNSentry:
:path: "../node_modules/@sentry/react-native"
SPEC CHECKSUMS:
GoogleSignIn: 11183592dc63e105475c7305a325045ff95e02b7
GoogleToolboxForMac: b3553629623a3b1bff17f555e736cd5a6d95ad55
GTMOAuth2: e8b6512c896235149df975c41d9a36c868ab7fba
GTMSessionFetcher: 61bb0f61a4cb560030f1222021178008a5727a23
React: ab1a2e21deb34965c38328d5ec40cc7d12c6050a
RNSentry: c4bdecef182912b8d8bb5b626f45da314f047dbd
Sentry: a8e37dc33aedb8a53540e36607fc2eaef7c31b4f
PODFILE CHECKSUM: 5e2bafbc45a648acb0e86e46e657665eede9abe4
COCOAPODS: 1.9.0
/**
* Block that bridge modules use to reject the JS promise waiting for a result.
* The error may be nil but it is preferable to pass an NSError object for more
* precise error messages.
*/
typedef void (^RCTPromiseRejectBlock)(NSError *error); Thank you. |
OK so that is the problem, your So I am closing this, solution is upgrading to a new react-native version. |
Hello, @HazAT you are right the version that is being referenced ( And at the same time, metro gives this error:
Not sure why React 0.11.0 is being added to the project with the Sentry. Any help would be appreciated. |
Can we reopen this issue 😕 |
I updated RNSentry.podspec to look for specifically my installed version of React. i.e:
|
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 1.4.2
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:
[Link to issue]
Configuration:
(
@sentry/react-native
)I have following issue:
Build failed.
Steps to reproduce:
react-native run-ios
Actual result:
Expected result:
Run on simulator
The text was updated successfully, but these errors were encountered: