The way we handle SimplePushURLs changed with this version, make sure that you've made a POST /registration with this token since you've changed the server.
I'm confused. Shouldn't such a post happen at every browser startup? If not, how do I force it?
(In reply to Rémy Hubscher (:natim) from comment #1) > The way we handle SimplePushURLs changed with this version, make sure that > you've made a POST /registration with this token since you've changed the > server. We are doing the same POST /registration that we always have, with just using simplePushURL as the parameter. According to the docs, this is still supported: https://wiki.mozilla.org/Loop/Architecture/Rooms#Loop_Server_API_Changes I haven't looked at what changes have been made to the server, so this may be irrelevant. I have verified the clients work with 0.12.4, but not with latest master.
Okay, we're looking at it.
Severity: normal → major
We should check Stage as well...
Status: NEW → ASSIGNED
I am pretty sure 0.12.6 has got this bug as well.
Never mind, the loadtest tests it: https://github.com/mozilla-services/loop-server/blob/0.12.x/loadtests/loadtest.py#L293
I don't think this problem still exists, but if it's the case, I'm not 100% sure to undestand what it is. Can you confirm that when you're doing a call from Bob to Alice using the link-clicker UI, Bob's client isn't waken up via simple push?
This are the related commits that make me think it has been fixed: - https://github.com/mozilla-services/loop-server/commit/3a367ea39dc92bf7bd933a4fd610ce76afabc3c9 - https://github.com/mozilla-services/loop-server/commit/474111afc879e59ae4056b4af30c6560d6bc8481
And of course, it's wrong. Let me do it again: Can you confirm that when you're doing a call from Bob to Alice using the link-clicker UI, Alice's client isn't waken up via simple push?
I've just been trying this on dev and its working fine. I've done a combination of direct calls and link clicker calls both ways.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.