TeamAmaze / TeamAmaze/AmazeFileManager
`UninitializedPropertyAccessException` on `CompressedExplorerFragment#prepareCompressedFile`: `fileName` has not been initialized
Open
Nobody has claimed this yet.
From-Email
- 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 文件管理器
- Package: com.amaze.filemanager
- Version: 3.6.7
- User Action: UI Error
- Request: Application crash
- OS: Linux
samsung/x1qzcx/x1q:12/SP1A.210812.016/G9810ZCU3EULJ:user/release-keys 12 -
31 - Device: x1q
- Model: SM-G9810
- Product: x1qzcx
Crash log
kotlin.UninitializedPropertyAccessException: lateinit property fileName has
not been initialized
at
com.amaze.filemanager.ui.fragments.CompressedExplorerFragment.prepareCompressedFile(CompressedExplorerFragment.kt:295)
at
com.amaze.filemanager.ui.fragments.CompressedExplorerFragment.onViewCreated(CompressedExplorerFragment.kt:184)
at androidx.fragment.app.Fragment.performViewCreated(Fragment.java:2974)
at
androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:543)
at
androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:282)
at
androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2177)
at
androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2088)
at
androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1990)
at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:524)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8641)
at java.lang.reflect.Method.invoke(Native Method)
at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1133)
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 reading CompressedExplorerFragment.kt around prepareCompressedFile at line 295 and its call from onViewCreated at line 184. Trace when fileName is assigned and how the fragment can reach this path without initialization; done means the reported crash no longer occurs when the compressed-file view is created.
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
- 45/100