Skip to content
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

java.lang.NullPointerException: Attempt to invoke virtual method 'com.paypal.android.sdk.onetouch.core.Result com.paypal.android.sdk.onetouch.core.Request.a(com.paypal.android.sdk.onetouch.core.a.a, android.net.Uri)' on a null object reference #101

Closed
nzakharchenko opened this issue May 23, 2016 · 9 comments

Comments

@nzakharchenko
Copy link

Hello!

on my release build after fresh install application I'm always getting java.lang.NullPointerException: Attempt to invoke virtual method 'com.paypal.android.sdk.onetouch.core.Result com.paypal.android.sdk.onetouch.core.Request.a(com.paypal.android.sdk.onetouch.core.a.a, android.net.Uri)' on a null object reference for first payment. More details here http://crashes.to/s/3d3f39c4400

It happens every first payment on freshly installed application on phone (Moto G 3rd edition) without installed PayPal application (login to PayPal are done in browser).

    compileSdkVersion 23
    buildToolsVersion "23.0.3"
    minSdkVersion 15
    targetSdkVersion 23

    compile "com.braintreepayments.api:braintree:2.3.0"

Thanks!

@lkorth
Copy link
Member

lkorth commented May 24, 2016

@nzakharchenko are you running proguard on your release builds? The stack trace isn't very useful as it seems to be obfuscated. Could you try it without proguard to see if it still crashes? If so it should provide as more useful stack trace.

@nzakharchenko
Copy link
Author

@lkorth here is stack trace without obfuscation http://crashes.to/s/cde28ba71d6. Let me know if you need something else.

@lkorth
Copy link
Member

lkorth commented May 26, 2016

@nzakharchenko: we just released 2.3.1-SNAPSHOT with a change that should fix this. Could you give it a try and let us know?

If you don't have the snapshot repository setup, you can add the following:

maven {
    url 'https://oss.sonatype.org/content/repositories/snapshots/'
}

@nzakharchenko
Copy link
Author

@lkorth looks like it works now. I've seen that you also already released 2.3.1, so I will make more testing on Monday with that

@lkorth
Copy link
Member

lkorth commented May 27, 2016

Note that 2.3.1 does not include the fix and will likely still result in a crash for you.

@nzakharchenko
Copy link
Author

Ok! then I will continue testing with SNAPSHOT and wait for next release

@nzakharchenko
Copy link
Author

nzakharchenko commented May 30, 2016

@lkorth Have you deleted SNAPSHOT ? I could not find it anymore under
maven { url 'https://oss.sonatype.org/content/repositories/snapshots/' }

@nzakharchenko
Copy link
Author

@lkorth is there any estimations about new release?

@lkorth
Copy link
Member

lkorth commented May 31, 2016

snapshots are automatically purged by Sonatype after a day or two. We will be making a release early this week with this fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants