[AC-6286] Silent push-notification regression
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Resolved |
| Resolution | Needs more info |
| Resolution Date | 2019-09-17T19:09:13.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Titanium SDK & CLI |
| Labels | ios |
| Reporter | Nick Kemp |
| Assignee | Shak Hossain |
| Created | 2019-06-11T23:56:10.000+0000 |
| Updated | 2019-09-17T19:09:14.000+0000 |
Description
Regression since TIMOB-26399 iOS: Several issues with push-notifications since 7.3.x Fix
- silent notifications fire on the dedicated silent event AND the normal (pre-existing)
Seems to have regressed in 8_0_1_GA
On iOS: we’re seeing the callback for
registerForPushNotifications being called twice when the push notification has content-available set to 1.
If we also register an event listener for silentpush this fires as well.
The result is when in the foreground we end up getting three different events to process the same notification. When the app is backgrounded we get 1 event on silentpush and one on the registerForPushNotifications callback.
I have tested the same code on 7.5.2 and the behaviour is correct (1 event) with this SDK.
Am I right in assuming that it's probably because we are using the callback property of registerForPushNotifications and so effectively "double registering" for events. I see in Han's example repo this is no longer used. If this is the case, the docs need an update to reflect the events have been split out!
[~nickkemp] Would it be possible to get a simple test case which reproduces the issue? Thanks.
Hello [~nickkemp], Can you please followup in here? Please provide a simple test case which reproduces the issue. Thanks.
Hello [~nickkemp], Can you please follow up in here? We haven't received the sample code yet. Can you please get on it and share with us so we can verify and take necessary steps farther? Thanks.