Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.0.6
-
Labels:None
-
Story Points:6
-
Rank:23
-
Sprint:OBM Sprint 2015#1
Description
Pre-conditions
Use an Android device
Reproduction steps
- usera creates a contact on its phone
- server is slow enough to have the phone issue the same request
- both request eventually get processed
Current behavior
- The contact is inserted twice : NOK
Expected behavior
- The contact is inserted once : OK
Additional informations
This changeset aims to protect the backend about contact duplication.
That protection is implemented using the hash of every contact created by a device.
When a contact hash is already known by Opush, it'll not send the creation command to its backend.
This fix has been done to handle the never fixed "ClientId" bug of Android, see https://code.google.com/p/android/issues/detail?id=61100
Issue Links
- is cloned by
-
OP-158 CLONE 3.1 - T#9813 Prevent resent requests from inserting duplicated contacts
-
ABORTED: Integrated in
opush-master-3.0 #24
OP-139Add an integration test (thilaire: 19eba662803bffffd9f811e0110163e7ca5a4351)OP-139Add Cassandra dao (thilaire: c3fcc4f3152df556127802055ce4d8530b245c42)OP-139Check contact creation is already done (thilaire: c5a5ff29a4753dead9e1f35ae9d206c3c1f72bf3)