LuckSiege / LuckSiege/PictureSelector
Fatal Exception: java.lang.IllegalStateException
- Dominant language
- Java
- Stars
- 13.6k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Description
## Current use version?
#### 当前使用的版本是多少?
```
v3.11.1、v3.11.2
```
## Will this problem occur in demo?
#### Demo能否复现这问题?
```
firebase后台上报
```
## Describe the problem or provide an error log?
#### 描述问题或提供错误log?
```
Fatal Exception: java.lang.IllegalStateException: Fragment PictureSelectorFragment{52b50e3} (5544a541-b60f-4b2f-8262-e125e32642d0 id=0x7f0b02be tag=PictureSelectorFragment) did not return a View from onCreateView() or this was called before onCreateView().
at androidx.fragment.app.Fragment.requireView(Fragment.java:2)
at com.luck.picture.lib.PictureSelectorFragment.setAdapterData(PictureSelectorFragment.java:2)
at com.luck.picture.lib.PictureSelectorFragment.handleFirstPageMedia(PictureSelectorFragment.java:5)
at com.luck.picture.lib.PictureSelectorFragment.access$3400()
at com.luck.picture.lib.PictureSelectorFragment$12.onComplete(:2)
at com.luck.picture.lib.loader.LocalMediaPageLoader$1.onSuccess(LocalMediaPageLoader.java:4)
at com.luck.picture.lib.loader.LocalMediaPageLoader$1.onSuccess(LocalMediaPageLoader.java:1)
at com.luck.picture.lib.thread.PictureThreadUtils$Task$3.run(PictureThreadUtils.java:1)
at android.os.Handler.handleCallback(Handler.java:790)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:200)
at android.app.ActivityThread.main(ActivityThread.java:6971)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the stack-trace entry points in PictureSelectorFragment.setAdapterData and handleFirstPageMedia, then inspect the LocalMediaPageLoader callback and Fragment lifecycle handling. Reproduce the crash on v3.11.1 or v3.11.2 if possible; done means the reported asynchronous path no longer calls requireView before onCreateView or after the view is destroyed, with regression coverage.
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