-
Notifications
You must be signed in to change notification settings - Fork 453
Crash caused by java.lang.NullPointerException: dataIntent must not be null (potentially related: New chrome Version) #237
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
Comments
Looks like this is also related to my comment in #130 and is getting more and more frequent? Maybe a newer Chrome is somehow the problem here? @kadikraman have you had this issue occur as well? |
Hi @sraka1 - I haven't had the chance to investigate this yet, but it's on my backlog. |
@kadikraman could you please rename this issue into "Crash caused by java.lang.NullPointerException: dataIntent must not be null". I don't think the version of Chrome (or any other browser) is to blame here... |
Thanks for the tip, @sraka1 - the new Chrome version may be a coincidence in this case. |
Closing this out - should be fixed by #352. |
Issue
Hello, my application crashed with latest chrome browser( 72.0.3626.76)
In app i detected if the chrome is installed if yes the redirect url is change for page after the correct login the ids server will redirect user to page where is a button with required params for redirect back to APP. The login worked very well since last chrome update. The another browser working good.
Log:
E/AndroidRuntime: FATAL EXCEPTION: main
Process: secret, PID: 1804
java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=0, result=0, data=null} to activity {secret/secret.MainActivity}: java.lang.NullPointerException: dataIntent must not be null
at android.app.ActivityThread.deliverResults(ActivityThread.java:4268)
Environment
ExpoKit
?ExpoKit
The text was updated successfully, but these errors were encountered: