TeamAmaze / TeamAmaze/AmazeFileManager
[Regression] Picking a file with Amaze > v3.0.1 from another app returns no file (under AOSP 4.1.2)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
When using Android's "share" functionality, Amaze versions higher than 3.0.1 crash. Tested with Amaze v3.0.1 (O.K.), v3.1.1 (crashes) and 3.1.2rc3 (crashes) under AOSP 4.1.2 on an Jolla 1 phone.
- When using Amaze as a file picker from another application, it is invoked, correctly states "Pick a file", and crashes when tapping on a file ("Unfortunately, Amaze has stopped. [OK]" in this and all subsequent cases). The selected file is not received by the invoking application, to which Android returns to after Amaze's crash.
- When tapping on a file Amaze crashes immediately, but an Android "share" dialogue ("Complete action with") is successfully opened, which works fine (after picking an application).
- When selecting a file in Amaze (via long press) and then using Amaze's "Share" function, a (seemingly Amaze internal) application chooser is opened. After selecting an application there, Amaze crashes, but the intent gets through (as in the case before).
- When selecting a file in Amaze (via long press) and then using Amaze's "Open with" function, Amaze crashes immediately.
Please let me know, if it would be helpful for you to try to capture a log of these crashes or find tombstone files corresponding to these crashes, and transmit them to you.
Side note: Also tested these cases with a recent version of Ghost Commander (v1.53.10b4) and the last (good old) OI Filemanager (v2.0.5), and they both are working fine in all cases. Surprisingly though, Simple Explorer crashes in a very similar way, as Amaze > v3.0.1 does. All these file manages are Free Software and installed from F-Droid.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are identified in the report. First reproduce the file-picker, Share, and Open with crashes on AOSP 4.1.2 and capture logs or tombstones; done means these flows no longer crash and the invoking application receives the selected file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100