TeamAmaze / TeamAmaze/AmazeFileManager

Crash on null DisableableViewPager

Open
#2,638 1 comment 0 reactions 0 assignees View on GitHub

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 Dateimanager
  • Package: com.amaze.filemanager
  • Version: 3.6.0
  • User Action: UI Error
  • Request: Application crash
  • OS: Linux Android 10 - 29
  • Device: FP3
  • Model: FP3
  • Product: FP3
Crash log

java.lang.NullPointerException: Attempt to read from field 'com.amaze.filemanager.ui.views.DisablableViewPager com.amaze.filemanager.ui.fragments.TabFragment.mViewPager' on a null object reference
	at com.amaze.filemanager.ui.activities.MainActivity.setPagingEnabled(MainActivity.java:1417)
	at com.amaze.filemanager.ui.fragments.MainFragment$2.onDestroyActionMode(MainFragment.java:695)
	at androidx.appcompat.app.AppCompatDelegateImpl$ActionModeCallbackWrapperV9.onDestroyActionMode(AppCompatDelegateImpl.java:2694)
	at androidx.appcompat.view.StandaloneActionMode.finish(StandaloneActionMode.java:112)
	at androidx.appcompat.widget.ActionBarContextView$1.onClick(ActionBarContextView.java:174)
	at android.view.View.performClick(View.java:7259)
	at android.view.View.performClickInternal(View.java:7236)
	at android.view.View.access$3600(View.java:801)
	at android.view.View$PerformClick.run(View.java:27892)
	at android.os.Handler.handleCallback(Handler.java:883)
	at android.os.Handler.dispatchMessage(Handler.java:100)
	at android.os.Looper.loop(Looper.java:214)
	at android.app.ActivityThread.main(ActivityThread.java:7356)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)


Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with MainActivity.java:1417, where setPagingEnabled accesses TabFragment.mViewPager, and trace the call from MainFragment.java:695 during action-mode destruction. Reproduce the reported UI action if possible and verify that finishing the action mode no longer crashes when the pager is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.