Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Crash when opening changelog without a web browser #2913

Closed
THEtomaso opened this issue Oct 17, 2021 · 4 comments
Closed

Crash when opening changelog without a web browser #2913

THEtomaso opened this issue Oct 17, 2021 · 4 comments
Labels
Issue-Bug Related unexpected behavior or something worth investigating. Issue-Easy (good first issue) Beginners welcome! Issues with relative low difficulty. Issue-Task (low) This isn't a bug, but should be dealt with.

Comments

@THEtomaso
Copy link

Issue:

"Guru Meditation" App/UI crash.

How to reproduce:

Go to 'Settings' > 'About Amaze File Manager' > 'Changelog'.

Note:

Not internet connected phone.

--

System info:

  • Amaze File Manager version: v3.6.5
  • Android device: Samsung Galaxy XCover 4s
  • Android version: 11
@VishalNehra VishalNehra changed the title Guru Meditation crash Crash when opening changelog without a web browser Oct 17, 2021
@VishalNehra VishalNehra added Issue-Easy (good first issue) Beginners welcome! Issues with relative low difficulty. Issue-Task (low) This isn't a bug, but should be dealt with. labels Oct 17, 2021
@EmmanuelMess EmmanuelMess added the Issue-Bug Related unexpected behavior or something worth investigating. label Oct 17, 2021
@THEtomaso
Copy link
Author

VishalNehra changed the title Guru Meditation crash Crash when opening changelog without a web browser

I do have a web browser installed, but I've disabled Chrome, if that's relevant.

@VishalNehra
Copy link
Member

Yes that is relevant. You essentially don't have any app available that can handle the INTENT to open a webpage.

@THEtomaso
Copy link
Author

THEtomaso commented Oct 17, 2021 •
edited
Loading

Confirmed.
Once I configured my browser to handle external requests, the issue went away (although still relevant, of course).

@voidEnum
Copy link

Hi, I wanted to start working on this, but I believe it has already been fixed by the commit that fixed issue #3963. Just letting you know so you can mark is as closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug Related unexpected behavior or something worth investigating. Issue-Easy (good first issue) Beginners welcome! Issues with relative low difficulty. Issue-Task (low) This isn't a bug, but should be dealt with.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@VishalNehra @THEtomaso @EmmanuelMess @voidEnum @VishnuSanal