MSALException java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference in android native app

Grover, Sidhartha 1

I'm trying to use MSAL android library to implement Azure AD B2C authentication in our enterprise android native app. After generating the appropriate configuration and using it in the azure samples (Botth Java and Kotlin) I get the error

java.lang.NullPointerException: Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference

On checking the network logs it appears that the authentication response is missing the access_token. On searching the web I found this open issue on github that has a workaround/ instructions to get past this error but that didnt help.

I would really like to get this working.

James Hamil 21,546 Reputation points Microsoft Employee

2021-04-19T19:35:05.19+00:00

Hi @Grover, Sidhartha , what documents/samples are you following? Can you please check that the scope of the token is correct?

Thank you,
James
Grover, Sidhartha 1 Reputation point

2021-04-20T15:04:24.673+00:00

I've been working with the sample @ https://github.com/Azure-Samples/ms-identity-android-java.git

I used the configuration from my company's Azure portal and followed all directions given in the readme of the repo. I successfully get a login page with multiple auth providers, choose one and it seems to authenticate me but in returning from the auth page I get this exception.

Can you elaborate on what I need to check in the scope of the token? I was provided the scope by the identity and auth team in our company.

Thanks,
Sid

1 answer

James Hamil 21,546 Reputation points Microsoft Employee

2021-04-20T21:18:23.043+00:00

Hi @Grover, Sidhartha , I think the best bet is to open a support ticket so we can look at your code and environment. I can get you a free ticket if you email "azcommunity@microsoft.com" with subject "ATTN: James Hamil" and attach your subscription ID. Please let me know when you have done so.

Best,
James
Please sign in to rate this answer.
Grover, Sidhartha 1 Reputation point

2021-04-21T20:50:18.537+00:00

Hi @James Hamil thanks for the prompt reply. I have an update here. I finally got the authentication to work but not without quirks. We followed the directions in this github issue message and setup a new scope. That scope worked and got rid of the error for us. Now we can see the access token in the AuthenticationResult object but cannot see the id_token which we are interested in.

Additional info: From the MSAL-android-kotlin sample I figured that the id_token is accessible from authenticationResult.getAccount().claims["id_token"] but I am getting a null claims object.

I am still interested in pursuing this further for the id token, so please let me know if I should go ahead with sending an email to the azcommunity address with your attention.

James Hamil 21,546 Reputation points Microsoft Employee

2021-04-27T20:40:02.427+00:00

Hi @Grover, Sidhartha , thanks for the update! We've been looking into your issue and have a few documents which may help you in general. This is one Azure Sample, and this is another. For the null claims object issue, the feature might not be present in the Android version. However, this may work as a solution: https://github.com/AzureAD/microsoft-authentication-library-for-android/issues/850#issuecomment-566821052

Please let me know if this helps!

Best,
James

Grover, Sidhartha 1 Reputation point

2021-04-30T20:03:55.753+00:00

@James Hamil thanks a lot for that response. The github post you provided worked for us. In fact along with the id token we were able to get the claims as well with the same approach.
Sign in to comment