b2g loop client is using DEV: https://github.com/mozilla-b2g/firefoxos-loop-client/blob/f85f047bf321f914a1adba0f264fe2bb1788de0f/js/config.js#L6 Desktop is using PROD http://mxr.mozilla.org/mozilla-central/source/browser/app/profile/firefox.js#1536 everyone should be on prod so that we can have calls between the two clients.
As soon as MVP is deployed to production both will be using prod. For now prod is MLP and B2G is MVP.
without agreeing on the endpoint - desktop Fx can not talk to b2g client. MVP seems too long to wait for this to happen.
+ a few people. This is blocking QA testing.
Priority: -- → P1
In fact we and our QA team (Loop Mobile client) are looking forward to testing using Production server but due to bugs like this, bug 1045706, we can not do it. As soon as it's fixed (I think it's already but not verified yet) we will point Loop Client to Production server.
Depends on: 1045706
This appears to be a mobile client issue not a server issue? :mostlygeek can I get a confirmation? If so, we need someone on the mobile client team to make the change in the code.
:oteo can you please follow-up with the mobile client team?
Yes, this is a mobile client issue, that was waiting on bug 1045706 to land, as without that one, FxOS will not work at all (we tried to point to production and login into Loop was not working). Still don't understand why 1045706 was not blocking this bug, but anyhow, we have just made a test and after today server changes we can login now into Loop with FxOS using Production so we will ensure tomorrow, if all is ok, that the "official" client points to production.
Anyhow, in order to be able to fully test the Desktop/Standalone/FxOS scenarios, we need also bug 1034041 to land as FxOS is already supporting the call-connection progress protocol but not desktop/standalone.
OK. Got it. :oteo - sorry that was my understanding. I have not officially signed off on bug 1045706. I am trying hard to complete the work by 5pm.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.