iOS Safari Mobile WebApp permissions not asked (Camera & Microphone)

[JacobWWHosking]

What happened and what did you expect to happen?

Expected Outcome:

1. Safari loads web app.
2. Safari requests access to Camera & Microphone
3. Safari loads user options
4. User selects
5. User connects

Experienced Outcome:

1. Safari loads web app
2. Safari loads user options
3. User selects
4. User tries to connect but is unable as permissions were never requested and accepted

Have you reviewed our existing documentation?

• GitHub issues
• FAQs page
• README page
• Feature-specific guides

Reproduction steps

1. Enter domain on Mobile Safari (version 18.1.0)
2. Page loads
3. User selects connection options
4. User trys to connect
5. User is unable as camera and mic permissions never requested or granted

Amazon Chime SDK for JavaScript version

amazon-chime-sdk-component-library-react@3.9.0 | amazon-chime-sdk-js@3.25.0

What browsers are you seeing the problem on?

Safari

Browser version

18.1.0

Meeting and Attendee ID Information.

N/A

Browser console logs

N/A

[ltrung]

Sorry what is the web app are you referring to here?

[JacobWWHosking]

Hi Trung, Web app refers to the product's online web implementation on a live demo server. Please see response from devs below:

…

__________________________________________________________________________ Reasons why we were unable to collect all browser logs 1. AWS API Gateway Payload Limits If you're invoking the Lambda function through API Gateway, note the following: REST API: Maximum payload size is 10 MB. 2. Cloudwatch Size limit - 1 MB limit for the entire batch of log events - 256 KB limit for each individual log event

__________________________________________________________________________ *Jacob Hosking*Head of Product & Development PADLOKTGLOBAL (AUS) +61 439 532 646 56 Bowman St | Pyrmont NSW 2009 | Australia Email: ***@***.***

On Sat, Dec 7, 2024 at 5:13 AM Trung Le ***@***.***> wrote: Sorry what is the web app are you referring to here? — Reply to this email directly, view it on GitHub <#3013 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOTXEERGV5XVMSLBADQLKE32EHSNRAVCNFSM6AAAAABTBJNC2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRTHA4TCMBVGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[hensmi-amazon]

If you can connect your phone to a MacOS device and get logs by following the steps in this blog: https://www.lifewire.com/activate-the-debug-console-in-safari-445798 . I usually have luck if all devices involved are updated to latest version. But we cannot investigate further without some client side logs, since we cannot reproduce ourselves.

[JacobWWHosking]

Hi Henry, This issue only existed with 18.1.0 18.0.1 faced a different issue and 18.1.1 did not have any issues at all This is more a flagging to let it be known that there were issues experienced with a certain version number of iOS/Safari. However, I will have the team follow the steps and use for tests moving forward. Regards, *Jacob Hosking*Head of Product & Development PADLOKTGLOBAL (AUS) +61 439 532 646 56 Bowman St | Pyrmont NSW 2009 | Australia Email: ***@***.***

…

On Wed, Dec 11, 2024 at 11:39 AM Henry Smith ***@***.***> wrote: If you can connect your phone to a MacOS device and get logs by following the steps in this blog: https://www.lifewire.com/activate-the-debug-console-in-safari-445798 . I usually have luck if all devices involved are updated to latest version. But we cannot investigate further without some client side logs, since we cannot reproduce ourselves. — Reply to this email directly, view it on GitHub <#3013 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOTXEERJYTEBOAS7O3HHL6D2E6CVNAVCNFSM6AAAAABTBJNC2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZTGM2TMMBZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[hensmi-amazon]

Got it, I appreciate the call out and this will be useful if we get similar reports in the future! Unfortunately it will be unlikely to be investigated further on our end because it has already been fixed by Apple, and likely is a OS level regression that we would not be able to circumvent. I will close this GH issue for now but will still be able to answer any further questions. Thanks!