missing package product

Hmmm, this is the second question I’ve seen about SAML-based SSO in the past week. Are you working on the same product as francisaugustomedeiros over in SAML with SSO extension triggering twice? Or is this just a coincidence? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There are two supported ways to package an ES client: A system extension embedded in an app installed in Applications A launchd daemon In the system extension case, you install your sysex using System Extensions framework. That framework was designed to be use by a GUI app in response to user actions. Trying to hide that process from the user doesn’t end well. If you’re not happy with that constraint it’s fine to package your ES client as a launchd daemon, and then install it via an installer package, using SMAppService, or any other privilege escalation path that takes your fance. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

We're having the same issue, but live on the production App Store. 100% of user downloads are failing to install. I can confirm that increasing the watchOS minimum deployment to 8.7 worked for us. Very frusrating, several $k lost. All tests worked beforehand and passed App Store review.

In MainApp I've tried creating the modelData variable with: // These two require ModelData to conform to ObservableObject, and vars must be marked with @Published: @StateObject private var modelData: ModelData = dataService.modelData @ObservedObject private var modelData: ModelData = dataService.modelData // This one uses @Observable instead, and vars aren't explicitly marked as @Published: @State private var modelData: ModelData = dataService.modelData // This is a simple let var: let modelData: ModelData = dataService.modelData In all four cases the entire list refreshes every time I swipe a row and press a button. In the case of the delete button, the confirmation dialog appears then disappears because the row changes. ObservableObject is the 'old' way of doing this, right? ModelData instead has the @Observable annotation. As stated earlier, the DataService is a singleton: DataService.swift: final class DataService { static let shared = DataService() private init() {} let coreData: CoreData = CoreData() le

Thanks for the post, I would recommend to search the 3rd party libraries you include in the project to see what framework included those methods and replace them for better solutions. You can find references to those API in your app by using the command-line to check the app and the libraries it links against. You can do so by running the grep command in Terminal. First build and archive your app. Then Open /Applications/Utilities/Terminal Type the following on the command-line to change to the directory where the application binary is: cd ~/Library/Developer/Xcode/Archives// For example, cd ~/Library/Developer/Xcode/Archives/2020-03-09/SampleApp 3-9-20, 11.47 AM.xcarchive To search for _cJSON_Delete, _cJSON_GetArrayItem, _cJSON_GetArraySize, _cJSON_Parse, type the following on the command-line: grep -R _cJSON_Delete * grep -R _cJSON_GetArrayItem * grep -R _cJSON_GetArraySize * grep -R _cJSON_Parse * If there are references to cJSON_Delete, _cJSON_GetArrayItem, _cJSON_GetArraySize, _cJSON_Parse, you will get