LuckSiege / LuckSiege/PictureSelector
io.reactivex.android报错了
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?
#### 当前使用的版本是多少?
```17年的版本
```
## Will this problem occur in demo?
#### Demo能否复现这问题?
```必现
```
## Describe the problem or provide an error log?
#### 描述问题或提供错误log?
大佬你好,有个问题想咨询一下就是我接手的这个项目使用的17年的时候PictureSelector库,然后网络请求框架是retrofit2+(rxjava1+rxjava2像是同时存在),我想升级PictureSelector,然后正当我移除旧版的PictureSelector的时候发现网络框架那边出错了(例如这个import io.reactivex.android.schedulers.AndroidSchedulers导入的Android报错了),请问一下你的这个库对网络请求那边是做了什么兼容了rxjava1和rxjava2的。
下面是我项目接入的网络框架
/*rxJava*/
implementation 'io.reactivex:rxjava:1.1.6'
implementation 'io.reactivex:rxandroid:1.2.1'
/*retrofit网络请求*/
implementation 'com.squareup.retrofit2:retrofit:2.1.0'
implementation 'com.squareup.retrofit2:adapter-rxjava:2.1.0'
implementation 'com.squareup.retrofit2:adapter-rxjava2:2.5.0'
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 Gradle dependency list in the report and the failing io.reactivex.android.schedulers.AndroidSchedulers import. Compare the rxjava, rxandroid, Retrofit rxjava, and Retrofit rxjava2 entries before and after removing PictureSelector. Done means the project’s dependency setup and the cause of the import failure are clearly identified.
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
- 20/100