LuckSiege / LuckSiege/PictureSelector
pixel全系手机,选择通过云同步下来的照片,必然崩溃
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能否复现这问题?
```
能,pixel全系手机,选择通过云同步下来的照片,必然崩溃
```
## Describe the problem or provide an error log?
#### 描述问题或提供错误log?
```kotlin
java.lang.NullPointerException
at java.io.File.(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:3058)
at androidx.fragment.app.FragmentStateManager.start(FragmentStateManager.java:587)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:279)
at androidx.fragment.app.FragmentStore.moveToExpectedState(FragmentStore.java:113)
at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1374)
at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:2841)
at androidx.fragment.app.FragmentManager.dispatchStart(FragmentManager.java:2791)
at androidx.fragment.app.FragmentController.dispatchStart(FragmentController.java:273)
at androidx.fragment.app.FragmentActivity.onStart(FragmentActivity.java:486)
at androidx.appcompat.app.AppCompatActivity.onStart(AppCompatActivity.java:246)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1510)
at android.app.Activity.performStart(Activity.java:8315)
at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3701)
at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2308)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7898)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)
```
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 the stack trace shows the NullPointerException, then trace the call from PictureCommonFragment.buildLocalMedia and PictureSelectorSystemFragment.onActivityResult. Reproduce selection of a cloud-synced photo on a Pixel device and verify that the flow no longer crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100