TeamAmaze / TeamAmaze/AmazeFileManager
ProcessViewerFragment not attached to a context
Open
Nobody has claimed this yet.
From-Email
Issue-Bug
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Issue explanation (write below this line)
Exception
- App Name: Amaze File Manager
- Package: com.amaze.filemanager
- Version: 3.6.7
- User Action: UI Error
- Request: Application crash
- OS: Linux Android 6.0.1 - 23
- Device: D6633
- Model: D6633
- Product: D6633
Crash log
java.lang.IllegalStateException: Fragment ProcessViewerFragment{713a5a3}
(8ed150ce-d8ea-4aa0-b2a3-d21464c94558)} not attached to a context.
at androidx.fragment.app.Fragment.requireContext(Fragment.java:898)
at androidx.fragment.app.Fragment.getResources(Fragment.java:962)
at
com.amaze.filemanager.ui.fragments.ProcessViewerFragment.processResults(ProcessViewerFragment.java:218)
at
com.amaze.filemanager.ui.fragments.ProcessViewerFragment$CustomServiceConnection$1.lambda$onUpdate$0(ProcessViewerFragment.java:463)
at
com.amaze.filemanager.ui.fragments.ProcessViewerFragment$CustomServiceConnection$1.lambda$onUpdate$0$ProcessViewerFragment$CustomServiceConnection$1(ProcessViewerFragment.java)
at
com.amaze.filemanager.ui.fragments.-$$Lambda$ProcessViewerFragment$CustomServiceConnection$1$Pgwl2x2oQWYgFcMg6AlZCZ-QTV4.run(lambda)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:234)
at android.app.ActivityThread.main(ActivityThread.java:5526)
at java.lang.reflect.Method.invoke(Native Method)
at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
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
Start by inspecting ProcessViewerFragment.processResults at line 218 and the CustomServiceConnection callback at line 463, using the provided stack trace as the entry point. Trace how the callback can run after the fragment is detached. Done means the reported UI action no longer crashes with a fragment-not-attached exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100