-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Push Status ID and Hash fix #2067
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Current coverage is 91.93%@@ master #2067 diff @@
==========================================
Files 93 93
Lines 6537 6538 +1
Methods 1169 1169
Messages 0 0
Branches 1370 1371 +1
==========================================
+ Hits 6010 6011 +1
Misses 527 527
Partials 0 0
|
thanks for the PR! |
Because push_hash generated from app does not match pushHash generated by pushStatusHandler. I see no other logic assuming they both generate a correlation string between _PushStatus and AppOpened event. |
@nlutsenko the code look good to me. can you confirm the push_hash is computed that way? given the spec here, the full payload should be hashed: https://gist.github.com/flovilmart/bf64276507d685ae41f6#file-_pushstatus-L44 |
Will double check and get back to you guys tomorrow. Also, I would love to kill push hash completely and replace with push id, so we can get deterministic analytics. |
I'd move for that too, killing the hash, that will require update in the client SDK's which is not that bad. |
@nlutsenko iOS just hashes that payload.alert and posts to /AppOpened, Android receives the hash from payload.push_hash and posts to /AppOpened, so it's legit. You can calculate that md5 and everything works well. You can correlate in db. So I do not see any problems. |
pushStatusHandler should encode only data.alert to create MD5 Hash
PushController should also send pushStatus.objectId to adapter: adapter can map sends with ids