Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.0.0.GA, 4.1
-
Fix Version/s: EE-4.1.0.RC1, EE-4.1.0.GA, 4.2.BETA, 4.2
-
Component/s: Push Library
-
Labels:None
-
Environment:ICEpush, Cloud Push
Description
If multiple Push-IDs belonging to the same Browser-ID are in a single Group, issuing a Request for a Cloud Push results in multiple identical Cloud Push Notifications to be issued to the same device.
Issue Links
- blocks
-
PUSH-410
Allow for multiple pending Cloud Push Notifications for a single Browser-ID
-
- Resolved
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Before starting the ConfirmationTimeouts for a Set of NotificationEntries a new Set of NotificationEntries is created containing a single NotificationEntry per Browser-ID. As ConfirmationTimeouts are bound to a Browser-ID, it doesn't make sense to use the full Set of NotificationEntries possibly containing multiple Push-IDs associated to a single Browser-ID. Marking this one as FIXED.
Show
Jack Van Ooststroom
added a comment - - edited Before starting the ConfirmationTimeouts for a Set of NotificationEntries a new Set of NotificationEntries is created containing a single NotificationEntry per Browser-ID. As ConfirmationTimeouts are bound to a Browser-ID, it doesn't make sense to use the full Set of NotificationEntries possibly containing multiple Push-IDs associated to a single Browser-ID. Marking this one as FIXED.
Sending icepush-ee/core/src/main/java/org/icepush/OutOfBandNotification.java
Transmitting file data .
Committed revision 48699.