jpush / jpush/jpush-react-native
Not Receive any Notification When App was killed in China
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
The title say it all. In Japan, when app was killed, our device can receive the notifications flawlessly, but when tested by our China tester, it does not work. It only works when app on the background state.
Already tested on 3 devices (Blackberry, Huawei Honor, and One Plus) still no luck. So definitely, not a device specific problem.
Any idea what is the root cause? Here is my AndroidManifest.xml, maybe there is something i miss.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.fastjapan.tabiko"
xmlns:tools="http://schemas.android.com/tools">
<permission android:name="${applicationId}.permission.JPUSH_MESSAGE" android:protectionLevel="signature" />
<application
android:name=".MainApplication"
android:label="@string/app_name"
android:icon="@mipmap/ic_launcher"
android:allowBackup="false"
android:theme="@style/AppTheme">
<activity
android:name=".wxapi.WXPayEntryActivity"
android:label="@string/app_name"
android:exported="true"
/>
<meta-data
android:name="JPUSH_APPKEY"
android:value="${JPUSH_APPKEY}" />
<meta-data
android:name="JPUSH_CHANNEL"
android:value="${APP_CHANNEL}" />
<activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
<service
android:name="cn.jpush.android.service.DaemonService"
android:enabled="true"
android:exported="true">
<intent-filter >
<action android:name="cn.jpush.android.intent.DaemonService" />
<category android:name="${applicationId}"/>
</intent-filter>
</service>
<service android:name="io.invertase.firebase.messaging.RNFirebaseInstanceIdService">
<intent-filter>
<action android:name="com.google.firebase.INSTANCE_ID_EVENT"/>
</intent-filter>
</service>
</application>
</manifest>
Update
It may refer to these problems
- https://github.com/jpush/jpush-react-native/issues/581
- https://github.com/jpush/jpush-react-native/issues/489
But i still don't understand why this problem only happened in China
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 AndroidManifest.xml shown in the issue and compare its JPush service configuration with issues 581 and 489. Reproduce the notification behavior on the listed devices or a comparable China environment, then trace the Android killed-app notification path. Done means identifying the China-specific cause and documenting or validating a concrete fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, 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