Open mnosov622 opened 1 week ago
This was an iOS issue that was fixed in iOS 18. For this reason we do not plan on attempting to mitigate this for iOS 17. Please reopen if it is still an issue on iOS 18.
This is still an issue on IOS 18.
Got it. Must be a slightly different issue. Can you provide full logs, including WebRTC verbose logs?
I already sent the logs to the AWS Support, let me know if you got it. If not, let me know where else I can send it privately, so I don't send it here.
Got it, I should have access to those eventually. They were iOS 18 logs correct? With the verbose browser logs? It should have a lot more then logs from just the SDK.
They were IOS 17 logs from the logrocket, I don't know if you heard of this app. Will it contain verbose browser logs?
If not, could you please send instructions on how to get them ?
My bad, I thought you were viewing the logs in Safari desktop app already. 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.
After you have those logs working, navigate to the safari console tab in the image i sent and enable verbose logging for those other 3 settings.
Thank you, but that seems like a lot to ask from a customer to be honest, would the logs that I sent to AWS support be enough? Let me know once you get them please
If you have a MacOS device it takes around 2 minutes to set up. The browser logs will not likely have enough information, since I will likely need to cut a ticket to apple. I can see if our QA team can reproduce but it may delay mitigation.
I will check if we can get that information, but hope that those logs might be useful!
Hi!
Do you have any update on this issue ?
We are still looking at this internally.
Hi!
@hensmi-amazon I'm a bit confused with instructions. It says how to connect IOS device to Mac, and your picture shows how to enable verbose logs, but where to actually export them ?
You can hold off on that for now, I think with the Javascript console logs we have a hypothesis on a possible race condition. Note that if this change went it it would be released mid December.
Regarding the instructions: Safari will add the browser internal logs to the console logs. There are instructions on export here: https://stackoverflow.com/questions/15507059/save-safari-javascript-console-to-file
Got it, thank you! So you don't need other logs for now, correct ?
No logs for now, thank you!
Got it! Is this the new feature of Ipads that have Ultra Wide camera and Front Facing camera causing the main issue ?
Not sure yet
What happened and what did you expect to happen?
Users on iPad (10th Gen) have Front Ultra Wide Camera as selected camera, then user is then attempting to change to the standard Front Camera. Upon selecting the Front Camera, the camera will work for a moment before cutting out with their video/camera feed then going black.
Here are the errors we get in the logs:
Video input device which was active is no longer available, stopping video.
cannot bind video preview since video input device has not been chosen
could not acquire video input from current device
Issue seems be specifically to Ipads, is this known issue ? Is there a way to overcome that ?
Thank you for response.
Have you reviewed our existing documentation?
Reproduction steps
N/A
Amazon Chime SDK for JavaScript version
3.23.0
What browsers are you seeing the problem on?
Safari (Ipad 10th)
Browser version
safari 17 (17.7.0)
Meeting and Attendee ID Information.
No response
Browser console logs
1) Video input device which was active is no longer available, stopping video.
2) cannot bind video preview since video input device has not been chosen
3) could not acquire video input from current device
4) Issue seems be specifically to Ipads, is this known issue ? Is there a way to overcome that ?