TeamAmaze / TeamAmaze/AmazeFileManager
NPE on `FileUtils#isPathAccessible`
Open
Nobody has claimed this yet.
Crash-NullPointerException
From-telegram
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)
Cannot open my amaze file manager
Exception
- App Name: Amaze File Manager
- Package: com.amaze.filemanager
- Version: 3.7.2
- User Action: UI Error
- Request: Application crash
- OS: Linux Android 11 - 30
- Device: OP4F97
- Model: CPH2269
- Product: CPH2269T2
Crash log
java.lang.RuntimeException: Unable to resume activity {com.amaze.filemanager/com.amaze.filemanager.ui.activities.MainActivity}: java.lang.NullPointerException
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4822)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4860)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2356)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:264)
at android.app.ActivityThread.main(ActivityThread.java:8315)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1049)
Caused by: java.lang.NullPointerException
at java.io.File.<init>(File.java:283)
at com.amaze.filemanager.filesystem.files.FileUtils.isPathAccessible(FileUtils.java:967)
at com.amaze.filemanager.database.models.explorer.Tab.getOriginalPath(Tab.java:53)
at com.amaze.filemanager.ui.fragments.TabFragment.addTab(TabFragment.java:390)
at com.amaze.filemanager.ui.fragments.TabFragment.addNewTab(TabFragment.java:332)
at com.amaze.filemanager.ui.fragments.TabFragment.refactorDrawerStorages(TabFragment.java:355)
at com.amaze.filemanager.ui.fragments.TabFragment.onCreateView(TabFragment.java:137)
at androidx.fragment.app.Fragment.performCreateView(Fragment.java:2963)
at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:518)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:282)
at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2189)
at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2100)
at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:2002)
at androidx.fragment.app.FragmentController.execPendingActions(FragmentController.java:451)
at androidx.fragment.app.FragmentActivity.onResume(FragmentActivity.java:436)
at com.amaze.filemanager.ui.activities.superclasses.ThemedActivity.onResume(ThemedActivity.java:307)
at com.amaze.filemanager.ui.activities.MainActivity.onResume(MainActivity.java:1304)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1456)
at android.app.Activity.performResume(Activity.java:8294)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4812)
... 11 more
Reporter: VishnuSanalT
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 in FileUtils.isPathAccessible at FileUtils.java:967, then trace the call through Tab.getOriginalPath at Tab.java:53 and TabFragment.addTab at TabFragment.java:390. Reproduce the resume flow on Android 11 and identify the null path shown by the stack trace. Done means the file manager opens without this NullPointerException and the affected tab flow still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100