We have a WebRTC based solution and have been excited about WebRTC support on ios 11 Safari. However, every WebRTC solution we have tested using iPhone 6 on ios 11.0.3 experiences the same problem:
After a while the remote video freezes and the whole phone crashes requiring force reset. There seems to be no talk about such issues anywhere on Internet. Has somebody been experiencing the same and have you found any solutions?
We have replicated the issue with ios 11.0.2, ios 11.0.3, iPhone 6 iPhone 6+ and the following solutions:
Our own WebRTC solution based on SimpleWebRTC
Talky.io
TokBox Safari Demo
This has been reported to webkit, see either https://bugs.webkit.org/show_bug.cgi?id=175014 or https://bugs.webkit.org/show_bug.cgi?id=176439
Related
Developed webRTC platform for 1:1, 1: many users. OK on Android, Windows (Chrome, Firefox) and MacOS (Chrome, Firefox, Safari). Fails on iOS. 1:1 ok (iOS > 11.x). More than 3 iOS users can fail. Cannot determine a pattern to find the cause. Tested on OpenTox Demo and the same issue. Using the latest SDK. TokBox support advise test has been replicated and no issues experienced. They have not suggested a starting point to determine the error. Keep referring back to SDK and their test was successful.
The primary issue being some audio streams fail. Using the latest SDK (17 at the time of writing).
As an example, we tested today (290420) and after successfully joining with 1 x Windows, 1 x macOS, I joined with iPad 11 Pro latest OS and the audio speaker failed on the iPad. I joined on iPhone 8 (iOS 13.x) and was fine.
Suggestions?
P.S. All web based using Javascript sdk
I have an app in Android and iOS that uses Sinch videocalls but since the iOS 13 launching the video the iOS 13 sends is bad, it looks like static. I've discovered that if during the videocall I use the iPhone in landscape orientation the video transmitted is normal. This problem happens even with the sinch demo. Any ideas to solve this?
I've tried: use multiple connections, updating the framework to the last version, in multiple devices, modifiy the frame from the callAsyncLocalVideoFrameHandler.
I expect to be able to send good video from devices with iOS 13 of higher and iPadOS.
we are aware of the issue, it's caused by a compatibility issue between iOS 13's H264 Codec and the WebRTC version we use on our SDK.
We are working to fix that. There will be a new major iOS SDK release to support iOS 13, at the moment we do not recommend customers to release new versions of their apps with iOS 13/Xcode 11 support.
Your current apps will still work on devices running iOS <12 and the new iOS 13, as long as they are not built with XCode 11.
iOS 13 brings also new directives to use VoIP Push on Apple devices, this will also cause changes on how customers integrate any VoIP SDK, if you use VoIP Push notifications.
See note and links on our website.
https://www.sinch.com/docs/resources/downloads/index_vvv.html#info-ios-13-voip-push-changes
Jorge Siqueira - Sinch Voice & Video.
I also see problems with iOS 13 and Sinch Video call. I have tried to go back and build with Xcode 10.3 but that does not help either. iOS 12 still works like you say
Audio in HMTL5 video works fine in Safari on iOS 10.3.1 on iPhone, though it doesn't in standalone web apps (same html code & video file). Video play is fine. Just no sound.
There are a few other related discussions in the past, eg, Why HTML5 video doesn't play in IOS 8 WebApp(webview)?. I tested on iOS 10 using the html provided by that post.
Not sure whether it is a new bug introduced in iOS 10, or a bug that has never been fixed by Apple since earlier versions. Does anyone experience this issue? Are there any workarounds? Thanks in advance.
I had the same question. I googled all over the place. Then I realized what was causing the problem: I had the physical "soft mute" switch (next to the volume buttons) on my iPad turned on. Infuriatingly, this muted the volume on web apps, but not Safari web pages.
I am a teacher who has developed an app that streams video tutorials to mobile devices. The app has been around for a while and was originally built in CS6 using AIR SDK 20. More recently I have moved to CC and published the app using CC and AIR SDK 23 and 24 (including beta 24.0.180).
The app now crashes on IOS first access after installing the app. When you open the app up again, it opens but will crash when pulling up the control centre, pulling down the notification bar, clicking on the home button or minimising the app with a pinch.
I have stripped out the code and have isolated the problem to video streaming within the project. The issue is replicated using the xml and swf file found here: Dropbox -
https://www.dropbox.com/sh/h4rht8ksps2k1gg/AADdlFLst5CALJgl6oUsziIUa?dl=0
(everything has been stripped from the project so I appreciate that no video will play - didn't need it to play to replicate the issue). The app has been installed on iPad Air with IOS10 and iPad Mini 1 IOS9, but my students have also experienced the issue on iPhones running IOS7 +.
Any help with this would be much appreciated as my students would like to use the app without the issues.
Kind regards
Matt
Preface: there are questions (some good, some bad) already in existance on StackOverflow about webRTC support on various browsers and platforms, including iOS. However I couldn't find anything definitive that was more recent than ~2012, and this is a rapidly-changing field.
I'm working on a browser-based webapp that uses webRTC for minimal-latency peer-to-peer data transfer (not for audio/video, unlike most applications it would seem - all I need is DataChannel).
I hit a snag when I started testing the data-transfer part of the project and discovered that iOS devices still don't natively support this in their built-in browsers (despite some recent rumors).
Bowser is a free open-source browser App for iOS that purports to support webRTC on iOS. The problem is that when I try to open the app, it simply crashes and closes. I've tested this on an iPhone 5 and 5s. Googling has failed to turn up alternatives - even Chrome for iOS doesn't currently support webRTC it seems.
My questions:
1) Are there alternative browsers (even iOS-version restricted) that are currently supporting webRTC, or is there anything promising coming down the pipeline?
2) Does Bowser actually work (webRTC) on iOS devices where it doesn't crash immediately upon launch?
3) What strategies have other people used to work around this limitation?
As of iOS 11, WebRTC is now supported in Safari: https://developer.apple.com/library/archive/releasenotes/General/WhatsNewInSafari/Articles/Safari_11_0.html#//apple_ref/doc/uid/TP40014305-CH13-SW1
Check out crosswalk project ( https://crosswalk-project.org )
This Provides runtime of Chromium engine for native support in older devices.
1) Are there alternative browsers (even iOS-version restricted) that are currently supporting webRTC, or is there anything promising coming down the pipeline?
Answer:
There is a Browser called Bowser that supports webRTC.
2) Does Bowser actually work (webRTC) on iOS devices where it doesn't crash immediately upon launch?
Answer:
It's not crashing as of now.But I couldn't successfully test with anything so far.I have raised an issue about it
3) What strategies have other people used to work around this limitation?
Answer:
Apple is yet to support WebRTC in Webkit so as of now the only way would be develop a native or Hybrid app that would support the unsupported WebRTC APIs.
You can develop a hybrid app powered by OpenWebRTC or cordova-plugin-iosrtc