LuckSiege / LuckSiege/PictureSelector
低概率崩溃问题
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.6k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Description
Android12 型号:XIAOMI Poco M3
报错内容:
java.io.File. (File.java:288)
com.luck.picture.lib.entity.LocalMedia.e (LocalMedia.java:21)
com.luck.picture.lib.basic.PictureCommonFragment.R0 (PictureCommonFragment.java:5)
com.luck.picture.lib.PictureSelectorSystemFragment.Q1 (PictureSelectorSystemFragment.java:1)
com.luck.picture.lib.PictureSelectorSystemFragment$a.a (PictureSelectorSystemFragment.java:15)
com.luck.picture.lib.PictureSelectorSystemFragment$a.onActivityResult (PictureSelectorSystemFragment.java:3)
androidx.activity.result.ActivityResultRegistry$1.onStateChanged (ActivityResultRegistry.java:102)
androidx.lifecycle.LifecycleRegistry$ObserverWithState.dispatchEvent (LifecycleRegistry.jvm.kt:25)
androidx.lifecycle.LifecycleRegistry.forwardPass (LifecycleRegistry.jvm.kt:83)
androidx.lifecycle.LifecycleRegistry.sync (LifecycleRegistry.jvm.kt:80)
androidx.lifecycle.LifecycleRegistry.moveToState (LifecycleRegistry.jvm.kt:33)
androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent (LifecycleRegistry.jvm.kt:15)
androidx.fragment.app.Fragment.performStart (Fragment.java:29)
androidx.fragment.app.FragmentStateManager.start (FragmentStateManager.java:26)
androidx.fragment.app.FragmentStateManager.moveToExpectedState (FragmentStateManager.java:68)
androidx.fragment.app.FragmentStore.moveToExpectedState (FragmentStore.java:31)
androidx.fragment.app.FragmentManager.moveToState (FragmentManager.java:28)
androidx.fragment.app.FragmentManager.dispatchStateChange (FragmentManager.java:10)
androidx.fragment.app.FragmentManager.dispatchStart (FragmentManager.java:12)
androidx.fragment.app.FragmentController.dispatchStart (FragmentController.java:7)
androidx.fragment.app.FragmentActivity.onStart (FragmentActivity.java:38)
androidx.appcompat.app.AppCompatActivity.onStart (AppCompatActivity.java:1)
android.app.Instrumentation.callActivityOnStart (Instrumentation.java:1468)
android.app.Activity.performStart (Activity.java:8230)
android.app.ActivityThread.handleStartActivity (ActivityThread.java:3799)
android.app.servertransaction.TransactionExecutor.performLifecycleSequence (TransactionExecutor.java:221)
android.app.servertransaction.TransactionExecutor.cycleToPath (TransactionExecutor.java:201)
android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:173)
android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:97)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:2291)
android.os.Handler.dispatchMessage (Handler.java:106)
android.os.Looper.loopOnce (Looper.java:211)
android.os.Looper.loop (Looper.java:300)
android.app.ActivityThread.main (ActivityThread.java:8322)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:556)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1038)
Contributor guide
No contributing guide indexed for this repository
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 with the stack-trace entry points LocalMedia.java:21 and PictureCommonFragment.java:5, using the Android 12 Xiaomi Poco M3 details as the reproduction context. Trace the File constructor call from the reported activity-result path and determine what input causes the crash. Done means identifying the cause and verifying a fix for this low-probability crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100