ios13

Xcode 12 beta and iOS 14: Weird console logs “objc[5551]: Class … is implemented in both”

时间秒杀一切 提交于 2021-01-20 17:54:07
问题 I have just downloaded Xcode 12 beta 2 and now I'm getting a bunch of weird logs in the console while I'm running my app (these warnings don't appear when using Xcode 11.5). They look like the following one: objc[5551]: Class CSAudioFileManager is implemented in both /Applications/Xcode-beta.app/Contents/Developer/Platforms/ iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/ Contents/Resources/RuntimeRoot/System/Library/ PrivateFrameworks/SpeakerRecognition

CallKit reportNewIncomingCall completion called but still getting “Killing app because it never posted an incoming call …” crash

℡╲_俬逩灬. 提交于 2021-01-07 02:42:58
问题 This is my first time using PushKit and CallKit combination to build a VoIP feature. I noticed that starting from iOS 13 it is mandatory to report a PushKit VoIP push, otherwise the app will crash. Due to this regulation I proceeded to implement the reportNewIncomingCall method inside didReceiveIncomingPushWith and made sure that its completion is successfully called, which it did, because the breakpoint I placed within the completion block was activated. However, not long after that, the app

iOS13: Alternative to VOIP push notifications (enterprise) to silently communicate with an app in background now that iOS13 killed it

和自甴很熟 提交于 2020-12-29 04:54:22
问题 So for about 4 years in our enterprise environment we were happily using VOIP push notifications to remotely access user's tablets for maintenance and remote data repair purposes. Unlike regular APNS, VOIP push notifications would access the app even if weren't running. I should have figured apple would kill it sometime. Is anyone aware of a private API to bypass the pushkit requirement to call reportNewIncomingCallWithUUID which brings about a full screen call UI, or another mechanism that I

iOS13: Alternative to VOIP push notifications (enterprise) to silently communicate with an app in background now that iOS13 killed it

坚强是说给别人听的谎言 提交于 2020-12-29 04:53:02
问题 So for about 4 years in our enterprise environment we were happily using VOIP push notifications to remotely access user's tablets for maintenance and remote data repair purposes. Unlike regular APNS, VOIP push notifications would access the app even if weren't running. I should have figured apple would kill it sometime. Is anyone aware of a private API to bypass the pushkit requirement to call reportNewIncomingCallWithUUID which brings about a full screen call UI, or another mechanism that I

iOS13: Alternative to VOIP push notifications (enterprise) to silently communicate with an app in background now that iOS13 killed it

女生的网名这么多〃 提交于 2020-12-29 04:52:00
问题 So for about 4 years in our enterprise environment we were happily using VOIP push notifications to remotely access user's tablets for maintenance and remote data repair purposes. Unlike regular APNS, VOIP push notifications would access the app even if weren't running. I should have figured apple would kill it sometime. Is anyone aware of a private API to bypass the pushkit requirement to call reportNewIncomingCallWithUUID which brings about a full screen call UI, or another mechanism that I

Collection View Compositional Layout with estimated height not working

牧云@^-^@ 提交于 2020-12-28 07:41:49
问题 I want my app to be optimized for every accessibility options including the text size. I made a collectionView layout based on sections with a compositional layout. So I need my cell's height to grow with it's content. I thought using .estimated(constant) would do the job but it doesn't seem to work. The inner constraints seems good to me. Here is the layout I'm working with : let size = NSCollectionLayoutSize(widthDimension: .fractionalWidth(0.42), heightDimension: .estimated(90)) let item =

Collection View Compositional Layout with estimated height not working

旧时模样 提交于 2020-12-28 07:38:18
问题 I want my app to be optimized for every accessibility options including the text size. I made a collectionView layout based on sections with a compositional layout. So I need my cell's height to grow with it's content. I thought using .estimated(constant) would do the job but it doesn't seem to work. The inner constraints seems good to me. Here is the layout I'm working with : let size = NSCollectionLayoutSize(widthDimension: .fractionalWidth(0.42), heightDimension: .estimated(90)) let item =

NSPersistentCloudKitContainer: How to check if data is synced to CloudKit

末鹿安然 提交于 2020-12-27 08:39:05
问题 I have implemented NSPersistentCloudKitContainer to get my data synced to CloudKit , I would like to know that the sync is finished and there is no other change pending to be synced. When I tried reinstalling the app, I start getting my data back from CloudKit and it started printing certain logs in the console. It takes around 30 seconds to get all my data back from the CloudKit. Some of the logs mention about NSCloudKitMirroringDelegate . It looks like NSCloudKitMirroringDelegate knows

NavigationLink hides the Destination View, or causes infinite view updates

爷,独闯天下 提交于 2020-12-15 07:08:52
问题 Let us consider the situation when you have ContentView and DestinationView . Both of them depend on some shared data, that typically lies inside the @ObservedObject var viewModel , that you pass from parent to child either via @EnvironmentObject or directly inside init() . The DestinationView in this case wants to enrich the viewModel by fetching some additional content inside .onAppear . In this case, when using NavigationLink you might encounter the situation when the DestinationView gets

NavigationLink hides the Destination View, or causes infinite view updates

折月煮酒 提交于 2020-12-15 07:07:40
问题 Let us consider the situation when you have ContentView and DestinationView . Both of them depend on some shared data, that typically lies inside the @ObservedObject var viewModel , that you pass from parent to child either via @EnvironmentObject or directly inside init() . The DestinationView in this case wants to enrich the viewModel by fetching some additional content inside .onAppear . In this case, when using NavigationLink you might encounter the situation when the DestinationView gets