Follow the instructions on the big blue banner!

So if I'm ready this correctly the TooltipView view's observableObject Model is placing a call to a generic Store find method using a dynamic key path lookup. What's going on in Store.find<A>(:) ?

And you were building these for years and Apple is no help. Might be best to reach out to Apple developer support if disabling and re-enabling auto code signing doesn't work. Just upgrade your OS and Xcode and move on given a bunch of issues were fixed in Xcode 13.3.

data3 is a collection type of Datums. result?.data3[index].actions[(tableView.indexPathForSelectedRow?.row)!]

No bundle ids are unique identifiers per app.

This is a developer forum please ask your question or visit the nearest apple store: https://discussions.apple.com/welcome

Quadtrees?

You can't it requires macOS - use VmWare or Parallels to probably run a copy of macOS or invest in a Mac.

I'm assuming you're following this: https://developer.apple.com/documentation/swiftui/building_a_document-based_app_with_swiftui and https://developer.apple.com/documentation/uniformtypeidentifiers/defining_file_and_data_types_for_your_app

Apple CarPlay doesn't allow video playback due to safety concerns.

Please contact the App Store Connect directly as this is not a developer related issue.

In the catch statement you can use a switch/case statement to look for a specific error type. I have created an errors generator example that you can place into playgrounds to see the switch/case pattern in use. /**  Errors Example code by Sean Batson (MobileTen)  */ import Foundation enum GenericErrors: Error {     case offline, certificates } extension GenericErrors: LocalizedError {     var errorDescription: String? {         switch self {         case .offline:             return "Server responded out of disk space"         case .certificates:             return "Certificates expired 24 hours ago"         }     } } enum ForumQuestionErrors: Error {     case answered, none } extension ForumQuestionErrors: LocalizedError {     var errorDescription: String? {         switch self {         case .answered:             return "Question previously answered limit reached"         case .none:             return "Ok"         }     } } class Forums {     let error = [offlineGenericError, certsGenericError, answeredForumError, noneForumError]     func generateError() {         let method = error[Int.random(in: 0..<error.count)]         do {             try method(self)()         } catch {             switch error {             case is GenericErrors:                 print(error, error.localizedDescription)             case is ForumQuestionErrors: print(error, error.localizedDescription)             default:                 print(error, error.localizedDescription)             }         }     }     func offlineGenericError() throws {         throw GenericErrors.offline     }     func certsGenericError() throws {         throw GenericErrors.certificates     }     func answeredForumError() throws {         throw ForumQuestionErrors.answered     }     func noneForumError() throws {         throw ForumQuestionErrors.none     } } let forum = Forums() forum.generateError()

Not sure why an error string in a c++ compiler used by platforms other than Apple will have specific Apple help strings but yes, anything that runs on macOS in binary form must be notarized through code signing. Before looking all of these things that you wish existed, learn to use the Xcode tools first.

The implementation is wrong. See links below especially the medium link https://developer.apple.com/documentation/uikit/mac_catalyst/uikit_catalog_creating_and_customizing_views_and_controls https://medium.com/swift2go/swift-custom-uiview-with-xib-file-211bb8bbd6eb

Yes if you're storing the identity on 3rd party servers, no if the usage is localized to just the app. Disclosing it cannot kill.