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

NullPointerException in onResume for certain devices #415

Closed
cvance opened this issue May 10, 2017 · 4 comments · Fixed by #420
Closed

NullPointerException in onResume for certain devices #415

cvance opened this issue May 10, 2017 · 4 comments · Fixed by #420
Milestone

Comments

@cvance
Copy link

cvance commented May 10, 2017

Device: Galaxy Note 4 (VZW)
OS: Android 6.0 (API Level 23)
Lock.Android Version: 2.5.0

Crash Log:

Unable to resume activity {com.auth0.android.lock.LockActivity}: 
java.lang.NullPointerException: Attempt to invoke virtual method 'void com.auth0.android.lock.views.formLayout.setEnabled(boolean)' on a null object reference 
com.auth0.android.lock.views.ClassicLockView.showProgress (ClassicLockView.java:293)
com.auth0.android.lock.LockActivity.onNewIntent (LockActivity.java:285)
android.app.Instrumentation.callActivityOnNewIntent (Instrumentation.java:1240)

I haven't been able to reproduce on any of my devices but this user has encountered it several times since we've added this library.

@lbalmaceda
Copy link
Contributor

It seems it's happening after a callback from the browser on the web authentication/passwordless flow, and the cause it's that the device is running out of memory and killing the activity before the actual result arrives. I couldn't reproduce it on this side. This is not a priority for us but I'll leave it open so if anyone has the same issue or knows how to reproduce it we can reevaluate it.

Cheers.

@viethoang88
Copy link

viethoang88 commented May 16, 2017

+1

screen shot 2017-05-16 at 3 28 10 pm

screen shot 2017-05-16 at 3 31 49 pm

@lbalmaceda lbalmaceda added this to the v2-Next milestone Jun 29, 2017
@lbalmaceda lbalmaceda modified the milestones: v2-Next, 2.6.0 Jul 12, 2017
@ebudagov
Copy link

I had a similiar issue. In my case, I was able to reproduce it as following:

  1. Run application
  2. Open android settings
  3. Go to application/storage settings and erase all aplication data
  4. Run application again

@lbalmaceda
Copy link
Contributor

@ebudagov on (1) are you attempting to log in? (e.g. is browser being launched?), also what version of Lock are you using?

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

Successfully merging a pull request may close this issue.

4 participants