-
Notifications
You must be signed in to change notification settings - Fork 206
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
Android Crash - "Callback arg cannot be called more than once"; #601
Comments
Same with The stack trace looks like this
|
@markstreich we disabled the double callback as a local patch for remediation |
@mobinni could you share the patch? |
Something like this? (I don't know how to recreate it, and don't know java, so kind of flying blind) --- a/node_modules/react-native-appsflyer/android/src/main/java/com/appsflyer/reactnative/RNAppsFlyerModule.java
+++ b/node_modules/react-native-appsflyer/android/src/main/java/com/appsflyer/reactnative/RNAppsFlyerModule.java
@@ -326,7 +326,7 @@ public class RNAppsFlyerModule extends ReactContextBaseJavaModule {
});
}
} catch (Exception e) {
- errorCallback.invoke(e.getMessage());
+ // errorCallback.invoke(e.getMessage());
return;
}
}
|
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Report
Plugin Version
6.15.1
On what Platform are you having the issue?
Android only
What did you do?
We use
logEvent
What did you expect to happen?
logEvent
callbacks not to crash on AndroidWhat happened instead?
On new arch in production for Android we receive crash logs where
onError
callback is called, but invoked twice which causes a crash to trigger;Please provide any other relevant information.
Im not sure how the double invocation happens, based on google play console it happens mostly on backgrounding. I could repro the issue by manually double invoking a callback. Based on the codepaths I see that we trigger the error callback in the try / catch as well as onError, there might be some type of condition being hit here where the error happens in
logEvent
natively gets thrown up and handled again?The text was updated successfully, but these errors were encountered: