230589 2021-09-21 17:39:04 -0700 REGRESSION: Camera feed does not render on 8th Wall WebAR experiences 2021-09-22 12:54:58 -0700 1 1 1 Unclassified WebKit WebGL Other iPhone / iPad Other RESOLVED DUPLICATE 230617 https://bugs.webkit.org/show_bug.cgi?id=230617 P2 Critical --- 1 joel webkit-unassigned connell dino kbr kkinnunen rigel tony oldest_to_newest 1795888 0 joel 2021-09-21 17:39:04 -0700 On iOS 15.1 beta 1 WebAR experiences that use the camera feed show a black screen instead of video. On iOS 15.0 the camera feed is properly rendered. This impacts major brands including: Marvel, LA Dodgers, Universal Pictures, MGM, Xbox, & More This link shows a video contrasting the behavior on iOS 15.0 and iOS 15.1 beta 1: https://youtu.be/qYr0_nPcRhY Use the following experiences on a device running iOS15.1 beta 1 to reproduce: Example 1: https://aircards.8thwall.app/dodgers/ Example 2: https://lookmister.8thwall.app/thetenrings/ Example 3: https://idareyou.candymanmovie.com/ Please let me know if I can provide more info, thank you. 1796006 1 connell 2021-09-22 04:05:26 -0700 I can confirm that we see this here too. Also running in production across many sites and businesses large and small! We're seeing a blue screen in place of the camera feed. We're using getUserMedia(...), a <video> element, and gl.texImage2D to get the camera feed as a WebGL texture. As per Joel's comment, everything is working great in iOS 15.0, but the iOS 15.1 Beta 1 shows the issue. Example: https://web.zappar.com Once Launch is tapped and permissions are granted, the camera feed should be visible. Happy to also provide any more info or testing - it's a super critical one for us this! 1796029 2 connell 2021-09-22 06:00:41 -0700 After some further digging, I've filed a separate bug for this inside the WebGL component: https://bugs.webkit.org/show_bug.cgi?id=230617 I've popped a minimal test case in there and it has a more specific title so hopefully will be surfaced to the right team members :-) 1796150 3 dino 2021-09-22 11:37:39 -0700 Tracking in the more specific bug. *** This bug has been marked as a duplicate of bug 230617 ***