LuckSiege / LuckSiege/PictureSelector
java.lang.NullPointerException
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.6k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Description
Current use version?
当前使用的版本是多少?
v3.11.1
Will this problem occur in demo?
Demo能否复现这问题?
Describe the problem or provide an error log?
描述问题或提供错误log?
手机型号:[realme RMX1921 (realme XT)]
手机系统版本:[Android 11 (SDK 30)]
Exception java.lang.NullPointerException:
at java.io.File.<init> (File.java:283)
at com.luck.picture.lib.entity.LocalMedia.generateLocalMedia (LocalMedia.java:336)
at com.luck.picture.lib.basic.PictureCommonFragment.buildLocalMedia (PictureCommonFragment.java:1254)
at com.luck.picture.lib.PictureSelectorSystemFragment.access$900 (PictureSelectorSystemFragment.java:40)
at com.luck.picture.lib.PictureSelectorSystemFragment$10.onActivityResult (PictureSelectorSystemFragment.java:335)
at com.luck.picture.lib.PictureSelectorSystemFragment$10.onActivityResult (PictureSelectorSystemFragment.java:329)
at androidx.activity.result.ActivityResultRegistry$1.onStateChanged (ActivityResultRegistry.java:148)
at androidx.lifecycle.LifecycleRegistry$ObserverWithState.dispatchEvent (LifecycleRegistry.java:354)
at androidx.lifecycle.LifecycleRegistry.forwardPass (LifecycleRegistry.java:265)
at androidx.lifecycle.LifecycleRegistry.sync (LifecycleRegistry.java:307)
at androidx.lifecycle.LifecycleRegistry.moveToState (LifecycleRegistry.java:148)
at androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent (LifecycleRegistry.java:134)
at androidx.fragment.app.Fragment.performStart (Fragment.java:3026)
at androidx.fragment.app.FragmentStateManager.start (FragmentStateManager.java:589)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState (FragmentStateManager.java:300)
at androidx.fragment.app.FragmentStore.moveToExpectedState (FragmentStore.java:112)
at androidx.fragment.app.FragmentManager.moveToState (FragmentManager.java:1647)
at androidx.fragment.app.FragmentManager.dispatchStateChange (FragmentManager.java:3128)
at androidx.fragment.app.FragmentManager.dispatchStart (FragmentManager.java:3079)
at androidx.fragment.app.FragmentController.dispatchStart (FragmentController.java:262)
at androidx.fragment.app.FragmentActivity.onStart (FragmentActivity.java:510)
at androidx.appcompat.app.AppCompatActivity.onStart (AppCompatActivity.java:246)
at android.app.Instrumentation.callActivityOnStart (Instrumentation.java:1436)
at android.app.Activity.performStart (Activity.java:8177)
at android.app.ActivityThread.handleStartActivity (ActivityThread.java:3755)
at android.app.servertransaction.TransactionExecutor.performLifecycleSequence (TransactionExecutor.java:232)
at android.app.servertransaction.TransactionExecutor.cycleToPath (TransactionExecutor.java:212)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:184)
at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:102)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2326)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:263)
at android.app.ActivityThread.main (ActivityThread.java:8296)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:612)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1006)
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 at LocalMedia.java:336, where generateLocalMedia is called from PictureCommonFragment.java:1254 after the system picker result. Reproduce the reported flow on Android 11 with the listed device details, then trace which value reaches java.io.File and identify the conditions for the NullPointerException. Done means the flow no longer crashes and the affected behavior is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100