Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

[CRASH] AccountManagerUtil.java line 59 #340

Open
bruno-cunha opened this issue Sep 17, 2019 · 7 comments
Open

[CRASH] AccountManagerUtil.java line 59 #340

bruno-cunha opened this issue Sep 17, 2019 · 7 comments

Comments

@bruno-cunha
Copy link

Hi, im having the following issue in the AccountManagerUtil when I run
MAS.start(context, config);.

Im using com.ca:mas-foundation:1.8.01-Beta1.

Caused by java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
       at com.ca.mas.core.storage.sharedstorage.AccountManagerUtil.<init> + 59(AccountManagerUtil.java:59)
       at com.ca.mas.core.storage.sharedstorage.MASSharedStorage.getStorageProvider + 167(MASSharedStorage.java:167)
       at com.ca.mas.core.storage.sharedstorage.MASSharedStorage.<init> + 69(MASSharedStorage.java:69)
       at com.ca.mas.core.storage.MASSecureSharedStorage.<init> + 28(MASSecureSharedStorage.java:28)
       at com.ca.mas.core.datasource.MASSecureStorageDataSource.<init> + 51(MASSecureStorageDataSource.java:51)
       at java.lang.reflect.Constructor.newInstance0(Constructor.java)
       at java.lang.reflect.Constructor.newInstance + 343(Constructor.java:343)
       at com.ca.mas.core.datasource.DataSourceFactory.getStorage + 23(DataSourceFactory.java:23)
       at com.ca.mas.core.store.StorageProvider.createTokenManager + 87(StorageProvider.java:87)
       at com.ca.mas.core.store.StorageProvider.<init> + 41(StorageProvider.java:41)
       at com.ca.mas.core.store.StorageProvider.getInstance + 51(StorageProvider.java:51)
       at com.ca.mas.core.conf.ConfigurationManager$ClientChangeListener.onUpdated + 406(ConfigurationManager.java:406)
       at com.ca.mas.core.conf.ConfigurationManager.activate + 170(ConfigurationManager.java:170)
       at com.ca.mas.core.MobileSsoFactory.getInstance + 169(MobileSsoFactory.java:169)
       at com.ca.mas.foundation.MAS.start + 169(MAS.java:169)
@Ruqiya-Kaladgi
Copy link
Contributor

Hi Bruno,
Please make sure you have the account authenticator xml added in you application and authenticator service in AndroidManifest.xml. Please refer the document links to which are given in README.md.

@bruno-cunha
Copy link
Author

Hi @Ruqiya-Kaladgi!
The MASAuthenticatorService is allready added to the AndroidManifest, i think it might have a different cause, thanks anyway.
This is the top offensor crash in or app, we have 10k+ crashs in the last 7 days and 98% of them are from Samsung devices with Android 9.
Any help is much appreciated.

@Ruqiya-Kaladgi
Copy link
Contributor

Hi @bruno-cunha
Please give details on the use case.
ADB logs would really help.
Is your app being installed first time on the devices?
The failure could occur if you already have an app with account manager setup and you try to install same app with different signature.

@bruno-cunha
Copy link
Author

@Ruqiya-Kaladgi, unfortunately I haven’t been able to to reproduce the error, all I have is the report on fabric.

@Ruqiya-Kaladgi
Copy link
Contributor

@bruno-cunha
Is your app being used afresh by the users or is it an ugrade to previous version?
Is it possible to give details like on which Device and Android version the issue is happening?

@bruno-cunha
Copy link
Author

@Ruqiya-Kaladgi
The app is an update from previous versions.

Those are the devices with most occurrences in the last 90 days, all of the them with Android 9:

Device %
Galaxy J6 11%
Galaxy S8 11%
Galaxy J6+ 8%
Galaxy J7 Pro 8%
Galaxy J8 7%
Galaxy S8+ 7%
Galaxy J4+ 4%
Galaxy J7 Prime 2 3%
Galaxy Note8 3%
Galaxy S9+ 2%

@Ruqiya-Kaladgi
Copy link
Contributor

Is your app available to everyone, so we could get it installed and see?

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

No branches or pull requests

2 participants