Under what conditions should we use CKContainer.fetchUserRecordID() and then fetch the CKRecord object, and under what conditions should we use CKFetchRecordsOperation.fetchCurrentUserRecordOperation().

I need to take some suggestions from other programmers about something. When we have to use an asynchronous closure, often because the Framework provides only an asynchronous method for something we can't do without, it seems to prevent us from using the guard statement, which we need to make the code easier to read. The guard statement keeps us from making nested if statements, which makes the code difficult to read if there are many lines of code within a set curly braces. I would see a closing curly brace, and not be able to see the what the if condition is for that if clause (what's between the set of curly braces). Putting comments at the closing curly brace works, but that means I would still have to find the if condition at the beginning of the if clause. I could collapse the clause where the curly braces closes a clause, but then I have to find that collapsed clause, because Xcode scrolls the content of the editor upward, so that the beginning of the clause is hidden upwards toward the top, and I don't know how far up it is. This problem that the guard statement solves is also a problem with completion handlers, which we have to have with any asynchronous code. One approach to this problem is to avoid nested curly braces. How do I do that when I have to have asynchronous clause of code? If there is someway I can return a variable of type Result from a function the classical way instead of in a completion handler, I could avoid nested closures or clauses. One way I've found is to use the DispatchSemaphore or any statement to instructs code execution to wait for an asynchronous closure end and then return. There's something I don't like about this that I'm not sure what it is. Anytime there is a code instruction to wait, it makes me uncertain to its effectiveness. One thing that would help is if Xcode would show in the editor the beginning of collapsed code, so that when I click on the left side of the code editor to collapse a closure/clause when I'm seeing the bottom of the closure, Xcode would scroll downward so that the code editor shows me the code at the beginning of the clause, so that I wouldn't have to scroll upward to find the code that introduces the clause of code. I could file a bug report with Apple. Anyone have any contributions to any solutions to this problem? By the way, what is the Apple or Swift word for I'm calling a clause? What, for example, is the code that is enclosed between curly braces? Am I using the words clause and closure each time I used them?

If I have a class property let appDelegate: AppDelegate? = UIApplication.shared.delegate as? AppDelegate Each time appDelegate is accessed, would it return the value at the time it is accessed, or would it return the value the first time it was accessed? I'm trying to understand whether the property above works the same way as let appDelegate: AppDelegate? = { return UIApplication.shared.delegate as? AppDelegate }() The second declaration of the appDelegate property runs the closure the first time the property is accessed and never again. Later references to appDelegate returns the value that was returned the first time the property was accessed.

I want to check if my code to cache contacts data while my iOS app is running is done well or not. Anyone have any samples I can look at. I did a search on the internet and cannot find much. Maybe code to cache any time of cache would help for me to look at. I am using Xcode 13.4.1, and my app is intended to install on iOS 12.0 up to the most current iOS version. I seem to remember a search class in one of Apple's frameworks for iOS. I don't remember if that was part of the Contacts Framework. I also will have a cache for the Contacts data that I store in CloudKit, so I take that into account to be looking for any way that might make the Contacts cache and the CloudKit cache work together.

Anyone have any words of wisdom about using NSCache and NSPurgeableData for caching in an iOS app, specifically to cache Contacts data from the device contact store? Under what conditions does this work well?

What does the following line do in the code snippet from CloudKitShare Apple sample Xcode project that I show after that?   assert(zoneID == self.zone.zoneID) // Update the server change token. // operation.recordZoneChangeTokensUpdatedBlock = { (zoneID, serverChangeToken, _) in   assert(zoneID == self.zone.zoneID)   self.setServerChangeToken(newToken: serverChangeToken) } The documentation for the assert statement says that when the project build is -0none and also in Playground, the code terminates completely, and not just exit from the current code, do I understand that correctly? The documentation seems to assume I understand C-style programming.

Is there any way I can allow my app to programmatically make a phone call?

Is there a way for me to put my iOS app in side of the shared with you?

Is there a way to use code pin iOS to pin a message to the top in the Messages app?

When I go to the Shortcuts app and add an action, there is a tab that lets me see Apps that has actions I can use. How do I make my iOS app be able to contribute actions for users to use in a shortcut, so that a user creating a shortcut can add an action that does something in my app? An example of this is the Walmart app. A user can create use an action that allows him to check in.

How do I get my iOS app to run code when something specific in a message in Messages happens, like a specific phone number sends a specific phrase?

I've been using the CloudKitShare sample code found here as a sample to help me write code for my app. I want to use performWriterBlock and performReaderBlockAndWait as found in BaseLocalCache using a completionHandler without violating the purposes of the design of the code, which focuses on being thread-safe. I include code from CloudKitShare below that are pertinent to my question. I include the comments that explain the code. I wrote comments to identify which code is mine. I would like to be able to use an escaping completionHandler if possible. Does using an escaping completionHandler still comply with principles of thread-safe code, or does it in any way violate the purpose of the design of this sample code to be thread-safe? If I use an escaping completionHandler, I would need to consider when the completionHandler actually runs relative to other code outside of the scope of the actual perform function that uses the BaseLocalCache perform block. I would for one thing need to be aware of what other code runs in my project between the time the method executes and the time operationQueue in BaseLocalCache actually executes the block of code and thus the completionHandler. class BaseLocalCache { // A CloudKit task can be a single operation (CKDatabaseOperation) // or multiple operations that you chain together. // Provide an operation queue to get more flexibility on CloudKit operation management. // lazy var operationQueue: OperationQueue = OperationQueue() // This sample ... // // This sample uses this dispatch queue to implement the following logics: // - It serializes Writer blocks. // - The reader block can be concurrent, but it needs to wait for the enqueued writer blocks to complete. // // To achieve that, this sample uses the following pattern: // - Use a concurrent queue, cacheQueue. // - Use cacheQueue.async(flags: .barrier) {} to execute writer blocks. // - Use cacheQueue.sync(){} to execute reader blocks. The queue is concurrent, // so reader blocks can be concurrent, unless any writer blocks are in the way. // Note that Writer blocks block the reader, so they need to be as small as possible. // private lazy var cacheQueue: DispatchQueue = { return DispatchQueue(label: "LocalCache", attributes: .concurrent) }() func performWriterBlock(_ writerBlock: @escaping () -> Void) { cacheQueue.async(flags: .barrier) { writerBlock() } } func performReaderBlockAndWait<T>(_ readerBlock: () -> T) -> T { return cacheQueue.sync { return readerBlock() } } } final class TopicLocalCache: BaseLocalCache { private var serverChangeToken: CKServerChangeToken? func setServerChangeToken(newToken: CKServerChangeToken?) { performWriterBlock { self.serverChangeToken = newToken } } func getServerChangeToken() -> CKServerChangeToken? { return performReaderBlockAndWait { return self.serverChangeToken } } // Trial: How to use escaping completionHandler? with a performWriterBlock func setServerChangeToken(newToken: CKServerChangeToken?, completionHandler: @escaping (Result<Void, Error>)->Void) { performWriterBlock { self.serverChangeToken = newToken completionHandler(.success(Void())) } } // Trial: How to use escaping completionHandler? with a performReaderBlockAndWait func getServerChangeToken(completionHandler: (Result<CKServerChangeToken, Error>)->Void) { performReaderBlockAndWait { if let serverChangeToken = self.serverChangeToken { completionHandler(.success(serverChangeToken)) } else { completionHandler(.failure(NSError(domain: "nil CKServerChangeToken", code: 0))) } } } }

I'm curious why I don't see posts about Xcode crashing. Since I updated both macOS Monterey 12.6 and Xcode 14, Xcode repeatedly crashes, becoming more frequently, even within 20 seconds between the last two crashes. Am I the only one getting these crashes?

Is there always only one local CNContainer on any iOS device whether the user is logged in to iCloud or not, and whether the device is an iPhone or an iPad?

The documentation for DispatchQueue.AutoreleaseFrequency.workItem says , "The queue configures an autorelease pool before the execution of a block, and releases the objects in that pool after the block finishes executing." Does this mean that the dispatch queue releases each work item or each code in ()->Void after each one finishes executing? When it says, "releases the objects in that pool er the block finishes executing", it makes it sound like there is only one block executing and then the entire pool is released. I'm making sure I verify that I understand this correctly.