jpush / jpush/jpush-react-native
IOS模拟器弹不出来推送的授权弹窗，也获取不到registerID
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
你的运行环境
- 插件版本:
"jcore-react-native": "^2.1.0",
"jpush-react-native": "^2.9.8",
"qs": "^6.11.1",
"react": "18.2.0",
"react-native": "0.71.6",
通过pod install安装，没有其他手工步骤。
期望效果
正常弹授权，以及收到推送
实际效果
编译有个警告：Class 'AppDelegate' does not conform to protocol 'JPUSHRegisterDelegate'
重现步骤
- ...
- ...
- ...
- ...
Debug logs
包括 Android 或 iOS 的日志：
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 AppDelegate entry point and the JPUSHRegisterDelegate warning using the listed React Native and JPush versions. Check example/documents/common_problems.md and reproduce on the iOS simulator. Done means the authorization prompt appears and a registerID is obtained; add logs and reproduction steps to confirm the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100