Project Information
- Repository: https://github.com/TeamAmaze/AmazeFileManager
- Title: Crash on restricting contact access when the app is signed to Google+
Expected behavior
I expected a notification declaring the contact permission as a neccesity for the app to run or a prompt to grant the permission when it is needed by the app.
Actual behavior
Amaze file Manager crashes few seconds after launch, when it is signed to Google+ and contact access is then restricted.
I suppose the few seconds after launch is the period when Google+ tries to access the contact, then it causes the app to crash on failure to access it instead of making a request.
How to reproduce
Device must have an active data connection during the process.
Launch Amaze filemanager and locate the three vertical dashes located at the upper left corner of the interface.
Clicking on the dashes will trigger the side bar.
Locate settings from the side bar and click on it to access the settings page.
Locate the
sign in ti google+toggle and turn the option onThere will be a prompt providing the existing gmail account on your device. choose the account and continue withghe set up.
Now exist the app and track the application info on the device settings page.
(You can find this through the setting page under the optionAPP. You can also find it by long pressing the app icon and dragging it into theApp Infooption that will appear. But not all launcher support this feature)Whenthe Application info for Amaze file manager is located, click on the permission option to access the toogles and turn of the toggle for
ContactNow head back to your application drawer and launch Amaze filemanager.. Wait for few seconds while google+ tries to access your contact.
The app should crash at this point.
Browser/App version: V3.2.1
Operating system: Android v6.9 marshmallow
Device: Itel p12 (spread chipset)