Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha3
-
Fix Version/s: 3.0
-
Component/s: None
-
Labels:None
-
Environment:server
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
Avoid sending cloud push notifications when notifications are triggered during the server-response - client-request gap. During this gap the pushIds are temporarily parked (when blocking connection runs) which is falsely interpreted as stopped blocking connection.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Mircea Toma [ mircea.toma ] |
| Salesforce Case | [] | |
| Fix Version/s | 2.0.0 [ 10233 ] | |
| Fix Version/s | 2.0-Beta [ 10232 ] |
| Salesforce Case | [] | |
| Fix Version/s | 3.0 [ 10259 ] | |
| Fix Version/s | 2.0.0 [ 10233 ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Salesforce Case | [] | |
| Affects | [Documentation (User Guide, Ref. Guide, etc.)] |
| Comment | [ Stopped scanning for expiry when adding (or re-adding) pushIDs to the group. The scanning is to be triggered only after the notification confirmation is received giving thus a chance to the server to touch the active pushIds and groups. ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |