microsoft-authentication-library-for-android
microsoft-authentication-library-for-android copied to clipboard
Fatal Exception: java.lang.NullPointerException: uriString
Describe the bug we are having some crashes reported in crashlytics, it's happening in the version 4.7.0
Smartphone (please complete the following information):
- Device: Samsung A32
- Android Version: 13
- Browser [e.g. Chrome, Edge]
- MSAL Version: 4.7.0
Stacktrace
Fatal Exception: java.lang.NullPointerException: uriString
at android.net.Uri$StringUri.
Expected behavior show the login or no get any crash
Actual Behavior suddenly get a crash
++ I experienced the same situation. One user encountered 27 crashes. Does anyone have a solution or information?
I already update the version from 4.7.0 to 5.3.1 and I am still having the issue, looking in internet I watched this Issue that you solved in past, in my case I am passing a configFile, because I can have different logins, so I am using this method
`public static void createMultipleAccountPublicClientApplication(@NonNull final Context context, @NonNull final File configFile, @NonNull final IMultipleAccountApplicationCreatedListener listener) {
validateNonNullArgument(context, NONNULL_CONSTANTS.CONTEXT);
validateNonNullArgument(listener, NONNULL_CONSTANTS.LISTENER);
runOnBackground(new Runnable() {
@Override
public void run() {
createMultipleAccountPublicClientApplication(
initializeConfiguration(context, configFile),
listener
);
}
});
}`
@Javs-21 Can you please try to check the config file? Please make sure that is is correctly formatted and includes all necessary fields, particularly the redirectUri.
@negoe yes is correct, we are pasign the correct values, we can show the webview with the login but for some reason some users get that crash, the last one was yesterday
this image in my QA environment
this one is in my PROD environment
@negoe please don't ignore me
@Javs-21 Can you please share your config file so that we can try reproducing the issue on our side?
@Javs-21 Can you please share your config file so that we can try reproducing the issue on our side?
Can you explain why I still get this crash if I provide the config file information?