TeamAmaze / TeamAmaze/AmazeFileManager

`RuntimeException` on `MainActivityHelper#guideDialogForLEXA`

Open
#4,099 0 comments 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)

copy file transfer multiple made .apk internal to sd, no loss, wont
contact, old phone

Exception

  • App Name: Amaze File Manager
  • Package: com.amaze.filemanager
  • Version: 3.10
  • User Action: UI Error
  • Request: Application crash
  • OS: Linux Android 6.0 - 23
  • Device: m216n
  • Model: LG-K420
  • Product: m216n_global_com
Crash log

java.lang.RuntimeException: Can't create handler inside thread that has not
called Looper.prepare()
at android.os.Handler.<init>(Handler.java:200)
at android.os.Handler.<init>(Handler.java:114)
at android.app.Dialog.<init>(Dialog.java:120)
at android.app.Dialog.<init>(Dialog.java:169)
at com.afollestad.materialdialogs.DialogBase.<init>(DialogBase.java:18)
at
com.afollestad.materialdialogs.MaterialDialog.<init>(MaterialDialog.java:87)
at
com.afollestad.materialdialogs.MaterialDialog$Builder.build(MaterialDialog.java:2183)
at
com.amaze.filemanager.utils.MainActivityHelper.guideDialogForLEXA(MainActivityHelper.java:321)
at
com.amaze.filemanager.utils.MainActivityHelper.guideDialogForLEXA(MainActivityHelper.java:294)
at
com.amaze.filemanager.utils.MainActivityHelper.checkFolder(MainActivityHelper.java:465)
at
com.amaze.filemanager.asynchronous.asynctasks.movecopy.PreparePasteTask.finishCopying(PreparePasteTask.kt:336)
at
com.amaze.filemanager.asynchronous.asynctasks.movecopy.PreparePasteTask.access$finishCopying(PreparePasteTask.kt:64)
at
com.amaze.filemanager.asynchronous.asynctasks.movecopy.PreparePasteTask$resolveConflict$1.invokeSuspend(PreparePasteTask.kt:320)
at
kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at
kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
at
kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:749)
at
kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
at
kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException:
[StandaloneCoroutine{Cancelling}@9ae17f7, Dispatchers.Default]


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 MainActivityHelper.java at guideDialogForLEXA and the PreparePasteTask.kt call path shown in the stack trace. Reproduce the copy-to-SD APK transfer if possible and trace how the dialog is reached from the coroutine; done means the transfer no longer raises the reported RuntimeException.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.