jpush / jpush/jpush-react-native

jpush-react-native对应的Jpush SDK版本和addConnectEventListener问题

Open
#841 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.4k
Forks
348
PR merge metrics
No merged PRs in 30d

Description

你的运行环境

  • 插件版本:
  • react-native 版本:
    "react-native": "~0.63.4"

实际效果

之前版本:

"jcore-react-native": "1.7.0",
"jpush-react-native": "2.7.5",

gradle配置,对应版本为3.5.4

implementation project(':jpush-react-native')  // 添加 jpush 依赖
implementation project(':jcore-react-native')  // 添加 jcore 依赖

//    implementation files('libs/jpush-android-plugin-huawei-v4.0.5.jar');//引入极光-华为jar包
implementation 'com.huawei.hms:push:3.0.3.301'
implementation 'cn.jiguang.sdk.plugin:huawei:3.5.4'// 极光厂商插件版本与接入 JPush 版本保持一致,下同
implementation 'cn.jiguang.sdk.plugin:xiaomi:3.5.4'
implementation 'cn.jiguang.sdk.plugin:oppo:3.5.4'

一切正常。但是出现oppo,华为回调无效!!
JPush.addConnectEventListener(this.connectListener);

解决,尝试升级到最新版本。但是不知道最新jpush-react-native对应的Jpush SDK是哪个版本

"jcore-react-native": "1.9.2",
"jpush-react-native": "2.8.3",

对接厂商时要统一版本号发生错误
image

期望效果

问题
1.怎么知道jpush-react-native对应的Jpush SDK版本
2.部分厂商JPush.addConnectEventListener无效该怎么处理

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the common_problems.md document and the Gradle dependency declarations shown in the issue. Check how jpush-react-native 2.8.3 maps to the JPush SDK and vendor plugin versions, then investigate JPush.addConnectEventListener for OPPO and Huawei callbacks. Done means the compatible versions and a reproducible callback resolution are identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, react-native
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.