TeamAmaze / TeamAmaze/AmazeFileManager
Copying 146MB the service crashes and the notifications is uncancellable
Open
Nobody has claimed this yet.
Issue-Bug
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
First start the copy of a folder with a lot of small items, then close the app and keep using the phone (Moto E Gen 2 4G in my case), the service crashes and the notifications is uncancellable (and undismissable).
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
Reproduce the folder-copy scenario on an Android device, then close the app and continue using the phone to observe the service crash and notification state. No file or test is named; done means the service remains stable and the copy notification can be dismissed or cancelled after the app closes.
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
- 35/100