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
Related
Since iOS 9.3 we can use the API SKCloudServiceController.requestAuthorization to ask permission to access the user's music library. The documentation says that the only change to this API on Xcode 11 was the support for tvOS, which should not change anything on iOS (which is the platform I'm using).
But, since Xcode 11 beta 4 I've noticed that the SKCloudServiceController.requestAuthorization callback does not get called.
My question is: is there a new API to ask for music library access or is this a iOS 13 bug?
I've found two unresolved discussions on Apple Developer Forums with related issues:
SKCloudServiceController.requestAuthorization not working on iOS 13
MPMedialLibrary.requestAuthorization not working on iOS13 devices
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
Along the news that came with the release of iOS 10 and WatchOS 3 there was CallKit.
I tried the demo app provided by Apple (and shown in the WWDC) called SpeakerBox in my devices (iPhone 6s, iOS 10 beta 5; AppleWatch with WatchOS 3 beta 5) and I have a serious doubt:
Are the features provided by CallKit available only on iOS or, since it uses the OS call system, we will have Apple Watch call handling for free as well?
I tested with the demo app but in that case I have the call ringing only on the phone, that sounds to me very weird since CallKit should be a framework to simplify the integration with the OS call system.
Does anybody know how and if is possible to have the standard call handling in WatchOS (>3 of course) as well?
If for managerial reasons I'm am developing an app that has not been designed with iOS7 in mind(the notion of supporting iOS7 wasn't apparent until I upgraded to XCode5 and tested the app in the simulator running iOS7), can I restrict my app to devices not running iOS7?
I know it's possible to change the app to support iOS 7 but we're already in the testing phase and it's not my decision how the app is made.
You can compile your application using Xcode 4, which will mark the binary to run in a compatibility mode on an iOS 7 device.
I'm assuming you want the app to still work on an iOS 7 device, just not with an iOS 7 user interface.
No, you can not restrict your app to devices not running iOS7.
You could check if the device is running with iOS 7 and through some kinde of exception or show an error message. Of course you won't get it through apples revision.
But it might work if you only deliver it to local devices.
Hi I am totally new to apple ios. I read and searched lots of artical about the push notification but i didn't find any thing much regarding the new updation from io4 to ios 6 for APNS. Can any one provide me proper information how APNS works on ios4 to ios 6? Is there any implementation changes?
Also i know that apple changes the way the PN appears in iOS 4 and iOS 5 like when PN appears ios 5 can show it without unlocking the device.
no, there is no change in implementation.
there is no difference in the code.
You can either use the same code for notifications whatever the ios version you are using.