Restricting Contact Permission Causes AmazeF.M To Crash Repeatedly.

organik (60)in #utopian-io • 7 years ago

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 on
There 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 option APP. You can also find it by long pressing the app icon and dragging it into the App Info option 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 Contact
Now 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)

Recording Of The Bug

proof of work done

https://github.com/organik1

#bug-hunting #bug #dev

7 years ago in #utopian-io by organik (60)

$0.08

9 votes

Sort:

Trending

[-]

fego (72) 7 years ago (edited)

Hi @organik, thanks for observing and making a report of this error. The aim of integrating Google+ with Amaze File Manager was to allow a user pick and set a profile picture. Fortunately, this has been discussed as completely redundant and points were given as to why it can be and should be - replaced with a feature that allows for picking a picture directly from the file manager itself for use.

As a result, a motion was moved to take down this feature. This can be found in this closed issue. And here also is the pull request where it was removed from the master branch - (pull link). There have been 801 commits to the master branch since the app's latest release of version 3.2.1 , hopefully these changes would be made available when a new release rolls out.

And the app crashing as a result of a google + integration would be ruled out, for the feature would not be present. It is advised that you provide a logcat for cases like this in future contributions.

I apologise for any inconvenience encountered in the process. I look forward to evaluating your future contributions.

Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]