INJIVER- In Browser Stack, after clicking the 'Scan QR Code' button,the user is not directed to the camera access 'Allow' popup screen

Rootcause

Working as expected

Description

Step to reproduce:

  1. Open the browser stack

  2. Choose the Mozilla Firefox browser version 90 to 99

  3. Enter this https://injiverify.qa-inji.mosip.net/ URL

  4. Click on the scan QR code button

  5. Check the Allow access popup

Observed: In Browser Stack, the user is not directed to the 'Allow' popup screen after clicking the' Scan QR Code' button. Instead, the user is directed to the 'Deny' popup screen. Please refer to the video

 

Expected: In Browser Stack, after clicking the 'Scan QR Code' button, the user should be directed to the 'Allow' popup screen.

Environment

qa-inji.mosip.net

Resolved by

Attachments

1
  • 31 May 2024, 07:09 AM

Activity

Show:

Santhosh September 12, 2024 at 9:40 AM

Verified this issue in the latest build, the issue is not observed any more, hence closing the bug

Srikanth Kola August 30, 2024 at 8:34 AM

As there is an browserstack camera access limitations, by default the browserstack is denying the os level popup, Hence the UI level popup is appearing showing the camera permission is denied instead of os level popup showing allow and denied. But in local browser the os level pop is appearing and behaving as expected.

https://www.browserstack.com/support/faq/mobile/test-session-mobile/can-i-access-the-device-camera-for-testing#:~:text=The%20camera%20is%20accessible%20in,MacOS%20+%20Chrome%20on%20Live

Srikanth Kola August 26, 2024 at 11:48 AM

https://www.browserstack.com/support/faq/mobile/test-session-mobile/can-i-access-the-device-camera-for-testing#:~:text=The%20camera%20is%20accessible%20in,MacOS%20+%20Chrome%20on%20Live
browserstack camera access limitations. The browser can’t handle permission because there is no camera access. But works fine in the firefox browser directly.

Fixed

Details

Assignee

Reporter

Severity

Critical

Sprint

Fix versions

Priority

Created May 31, 2024 at 7:09 AM
Updated September 12, 2024 at 9:40 AM
Resolved August 30, 2024 at 8:35 AM