Closed Bug 1120710 Opened 10 years ago Closed 10 years ago

Fallback procedure is not invoked due to security prompt not clicked in FxOS 2.1

Categories

(Firefox OS Graveyard :: Gaia::Loop, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 unaffected, b2g-v2.1 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.0 --- unaffected
b2g-v2.1 --- affected

People

(Reporter: oteo, Unassigned)

Details

Preconditions: - Firefox Hello logged in with a valid account but without having accepted the video/audio permissions yet (alternatively you can configure these permissions to ask in settings/app permissions) - Contact in the device address book with a phone number not registered in Loop (e.g. 555555555) STR: - Launch address book - Open the contact with the number non registered in Loop - Click on the video Hello call button - The calling screen is shown ACTUAL RESULT - The security prompt is shown for a while - No fallback procedure is offered to the user EXPECTED RESULT: - The security prompt is offered and does not disappear so user can accept the permissions - Fallback procedure to share the URL is offered Please note that this does not happen if the app already has the video/audio permissions granted (e.g. Changing them in settings/app-permissions) so it seems like a window manager issue.
Antonio, can you have a look at it? Thanks a lot!
Flags: needinfo?(amac.bug)
This seems to be bug 1082517 which for some reason wasn't uplifted to 1.1. The PR that should be uplifted is: https://github.com/mozilla-b2g/firefoxos-loop-client/pull/304
Flags: needinfo?(amac.bug)
I forgot to mention that this issue only happens with 1.1 Loop Mobile version. It does not reproduce with master version (future 1.1.1) because the fallback mechanism is different as it offers a Room to be shared in case the called user is not registered in Loop so the call screen and permission prompt will not be launched. I am going to close the bug as Won't fix as version 1.1.1 is going to land in 2.0, and future versions if they are included in 2.1 FxOS Release will not have this issue anymore.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.