Search results for

Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

186,306 results found

Post

Replies

Boosts

Views

Activity

Reply to process.waitUntilExit never exits in tahoe 26.3
Hmmm, that’s not good. While I don’t want to engage in ‘blame the victim’ here, there is something you can do to reduce the risk of problems like this occurring in the future, namely, testing with beta seeds as they’re released. The beta seed programme exists to help us find and fixing regressions like this. Anyway, let’s see if we can find you a workaround. If you add this to your app’s entitlement, does it prevent the failure: A key of com.apple.security.temporary-exception.mach-lookup.global-name With the value being an array With a single string element Whose value is com.apple.storagekitd If that works, we can then talk about the App Review implications |-: Note Temporary exception entitlements have an interesting history. I have a couple of links in App Sandbox Resources that explain more about them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Core OS Tags:
2d
CLMonitor API Missing Geofence Entry Events After Initial Registration
We are experiencing a failure in CLMonitor event delivery when the application is launched into the background via an APNS (Remote Push Notification). Even when a CLBackgroundActivitySession is instantiated immediately upon background launch, CLCircularGeographicCondition Enter events are suppressed. The system fails to deliver these events until the user manually brings the application to the Foreground. This indicates that CLBackgroundActivitySession does not correctly maintain background persistence when the session begins in a background state rather than transitioning from the foreground. Comparison of API Behavior (Background State) Launch via APNS: CLMonitor: Fails to trigger Enter events until the app is manually brought to the foreground. Legacy API: Successfully triggers and delivers Enter events immediately upon background launch. Exit Event Reliability: CLMonitor: Reliably triggers exit events even in the background. Legacy API: Reliably triggers exit events. Foreground Dependency: CLMonitor: Requ
2
0
167
2d
Run destination for my Xcode submission
My swift student challenge submission is an iPad app built in Xcode and I'm planning on selecting the Xcode 26 option for testing in the dropdown provided in the application. Just have to confirm that the run destination for the playground in Xcode will be an iPad simulator right? Recently I have seen many participants post their submission screenshot for iPhone renders so just wanted to confirm the run destination. Thank you👾
1
0
68
2d
Reply to Securing code signing ceritifcates in the secure enclave
First up, I want to be clear about terminology. You don’t sign code with a certificate, you sign it with a digital identity, that is, the combination of a certificate and its associated private key. There’s no need to protect the certificate; it’s the private key that matters. I talk more about this in TN3161 Inside Code Signing: Certificates. Second, the Secure Enclave (SE) doesn’t store private keys. Rather, you protect a private key with the SE. The SE generates the private key and returns it wrapped in a way so that only that SE can use it. You then send key operations, like ‘sign this blob with this wrapped key’, to the SE, it internally unwraps the key, does the operation, and returns you the result. So the unwrapped key material never leaves the SE, but it’s not stored in the SE. Note This is how the SE works but it’s not true for other hardware-based keys. Notably, with a smart card the private key is actually stored on the smart card itself. Folks using the smart card don’t work with a wrapped key, t
2d
Securing code signing ceritifcates in the secure enclave
I am on a mission to secure our key material for our iOS app's code signing certificate. My first endeavor with storing the code signing certificate on a YubiKey is a marginal success - it seems that with a pin policy that requires entering the PIN at least once we must enter the PIN umpteen times per build. Creating a certificate with a policy of never would be ill-advised. On the other hand, we could chose to store the code signing certificate in the Secure Enclave. However, it seems that I am only allowed to create eliptic curve private keys and not RSA keys in the secure enclave. When I attempt to upload a certificate signing request to AppStoreConnect, I am told that only an RSA2048 key will do. What I am after is a way to authenticate access to the certificate once per boot so that we can make multiple builds per day without manual intervention whilst also ensuring that the key material is not stored on disk. A yubikey would be preferable, but I am fine with the secure enclave
1
0
50
2d
Xcode Cloud: Unable to Notarize macOS App (Stuck in Infinite Waiting)
Hi everyone, I’m encountering an issue with Xcode Cloud when trying to notarize my macOS app. As shown in the screenshot, there are no errors in the logs, but the process gets stuck indefinitely. The message says: The post-action could not be completed because the build was canceled. No artifacts are generated at all. This problem started recently. Notarization works perfectly when I submit from my local Xcode, so it seems to be specific to Xcode Cloud. Has anyone else experienced this?
4
0
213
2d
Why do I feel like my growth as an iOS developer has slowed down
I have 9 plus years of iOS experience starting with Objective C and moving to Swift, but after 4 years in my current company with little salary growth, I am struggling to find new opportunities in a highly competitive market with fewer openings and broader skill expectations. I am unsure about the long term career path for mobile developers, concerned about compensation growth and lacking SwiftUI experience, and would appreciate guidance on what additional skills to learn to stand out and secure better opportunities.
1
0
32
2d
dropDestination does not work inside List
I've discovered an issue with using iOS 16's Transferable drag-and-drop APIs for SwiftUI. The dropDestination modifier does not work when applied to a subview of a List. This code below will not work, unless you replace the List with a VStack or any other container (which, of course, removes all list-specific rendering). The draggable modifier will still work and the item will drag, but the dropDestination view won't react to it and neither closure will be called. struct MyView: View { var body: some View { List { Section { Text(drag this title) .font(.largeTitle) .draggable(a title) } Section { Color.pink .frame(width: 400, height: 400) .dropDestination(for: String.self) { receivedTitles, location in true } isTargeted: { print($0) } } } } } Has anyone encountered this bug and perhaps found a workaround?
9
0
3.6k
2d
Reply to Is calling different SBApplication objects from different threads bad?
(2) Redesign your approach such that you stop actually doing any “long-term running. That's a no-go. Jobs just have to run until they are done. There are dozens if not hundreds of pieces of data that are built and used along the way. Some of them are hogs that will run for 3 hours. How isolated are each of these jobs? For example, is progress being routed back to another thread or is all of the work contained to that thread? All the work for each job is pretty much self-contained in its thread as far as the SBApplication goes. Each job gathers data from the network, generates one of more InDesign documents and saved the resulting files of various types. They all communicate back to other servers by various means (simple I'm still working heartbeats), communicate with main parent app and various objects in the app to show progress, all of which has been heavily stressed and show no signs of causing problems. Swift has wormed its way into this fairly old Cocoa app, mostly in the data access from networ
2d
Reply to CBCentralManager State Changes to PoweredOff After Using ASK for Accessory Setup
I am experiencing the same issue described here. If I bring up the AccessorySetupKit picker for ~10 seconds, the BluetoothCentral goes to disconnected. All peripherals also disconnect but I do not get notified (checking peripheral state will show disconnected) There is no recovery without restarting my app. This still reproduces on iOS 26.2 and iOS 26.3. I am ONLY using ASK paired accessories. No bluetooth scanning. With that said, I have a workaround. Disconnect all peripherals AND clear all references to BluetoothCentral before bringing up ASK picker Do not attempt to connect to newly added peripheral while ASK picker is on screen (that is don't use .accessoryAdded as a chance to connect because you don't want to create the central with ASK in use) After ASK is dismissed, recreate BluetoothCentral WITHOUT state restoration Go through all accessories (new and old) and get new references to peripherals + set new delegates etc. This seems to work reliably, but it seems really surprising that
Topic: App & System Services SubTopic: Core OS Tags:
2d
Reply to Is calling different SBApplication objects from different threads bad?
That's interesting about the difference between NSOperation and NSThread as far as Mach ports go. I watched the # ports in Activity Monitor as I ran a job, and it certainly doesn't climb as each job runs. It goes from initially in the 300s to the low 500s right when the job starts, and stays around there, even after the job ends, and then I run the same job 2 or 3 more times without quitting. Well, that's the joy of Mach port leaks... you never REALLY know what you'll get. So, as some broader background here, the actual issue here isn't really about the thread API itself- ultimately, both APIs are using pthreads and the special pthread GCD uses aren't really different than standard pthreads. The real issue here is that you don't actually own the thread and the assumptions AppleEvents/ScriptingBridge were built around. Both of those APIs predate GCD (by many, many years) and are built around the assumption that they'll be used on a long-running thread that's running its own runloop, as that w
2d
Reply to Extract raw Screen Time data? Security says it's 'expected'
Hi, thanks for posting this — I've been hitting the exact same wall. I'm building a screen time management app and spent considerable time trying to persist per-app usage data from the DeviceActivityReportExtension to the App Group container. I exhaustively tested every storage mechanism available: Core Data, JSON files, UserDefaults (App Group suite), Keychain, raw POSIX syscalls, SQLite, iCloud KV, and NSUbiquitousKeyValueStore. All fail with permission errors — the extension is completely write-locked at the kernel level (POSIX errno 1 / EPERM). I also confirmed the DeviceActivityMonitor extension has the same restriction. So I'm very interested in your finding that the host app can reconstruct raw activity data from the report. Could you share more about the technique you used? Specifically: How does your host app access the data from the report extension? Is it through the rendered view hierarchy, some callback mechanism, or something else entirely? Are you able to get per-app bundle identifiers
Topic: App & System Services SubTopic: General Tags:
2d