Search results for

“xcode github”

96,036 results found

Post

Replies

Boosts

Views

Activity

actionGroupCell Y coordinates are corrupted. The overlay for 'Save to Files' doesn't expose no valid id's for testability.
I am using Maestro framework for testing iOS. For our tests we need to save pdf's to files. When opening the 'QLOverlayDefaultActionButtonAccessibilityIdentifier' the buttons on the overlay are way off, the coordinates got corrupted. When opening the files app, the next screen has no coordinates for testing. I checked with xcode inspector and the same issue persists.
1
0
453
3w
Kernel panic when using fclonefileat from ES
Hi, I am developing instant snapshot backup solution for macOS using Endpoint Security. We have stumbled upon a Kernel Panic when using fclonefileat API. We are catching a kernel panic on customer machines when attempting to clone the file during ES sync callback: panic(cpu 0 caller 0xfffffe002c495508): apfs_io_lock_exclusive : Recursive exclusive lock attempt @fs_utils.c:435 I have symbolized the backtrace to know it is related to clone operation with the following backtrace: apfs_io_lock_exclusive apfs_clone_internal apfs_vnop_clonefile I made a minimal repro that boils down to the following operations: apfs_crash_stress - launch thread to do rsrc writes static void *rsrc_write_worker(void *arg) { int id = (int)(long)arg; char buf[8192]; long n = 0; fill_pattern(buf, sizeof(buf), 'W' + id); while (n < ITERATION_LIMIT) { int file_idx = n % NUM_SOURCE_FILES; int fd = open(g_src_rsrc[file_idx], O_WRONLY | O_CREAT, 0644); if (fd >= 0) { off_t off = ((n * 4096) % RSRC_DATA_SIZE); pwrite(fd, buf, sizeof(buf
5
0
212
3w
Live Activity creates successfully but never displays on lock screen or Dynamic Island ( iOS 26.4.1, Xcode 26.4)
Environment: Xcode 26.4 (17E192) iOS 26.4.1 iPhone 15 Pro Project uses PBXFileSystemSynchronizedRootGroup (Xcode 26 format) Setup: Widget Extension target named ModusWidgetExtension Bundle ID: com.calvin.Modus.ModusWidget NSSupportsLiveActivities = YES in both main app and widget extension Info.plist Live Activities enabled in Settings → Modus Live Activities enabled in Settings → Face ID & Passcode → Allow Access When Locked Background App Refresh enabled Push Notifications capability on both targets ActivityAttributes struct added to both targets via file target membership Behaviour: ActivityAuthorizationInfo().areActivitiesEnabled returns true Activity.request() succeeds and returns a valid activity ID No error is thrown Nothing appears on lock screen or Dynamic Island in foreground or background Widget preview in Xcode renders correctly for all presentations (compact, minimal, expanded, lock screen) Console output from liveactivitiesd filtered logs: Foreground process is per
1
0
146
3w
Reply to Live Activity creates successfully but never displays on lock screen or Dynamic Island ( iOS 26.4.1, Xcode 26.4)
Thanks for the post, this is extremely interesting to me. Can you post as much code as possible to see how you use the LiveActivitiy and is configured in the main entry? So the system successfully registers the activity from the main app, but when it asks to render it, the Widget Extension fails to provide a matching ActivityConfiguration? And your Xcode previews work, the UI code is valid, but it is not being successfully exposed to the system at runtime? Even if your Live Activity code is perfectly written and included in the target, the system will not know it exists unless it is explicitly instantiated in your extension's main entry point. Can you provide the code for that for me to review? If you have standard home screen widgets alongside your Live Activity, you must include both in the bundle. If the LiveActivity is missing from this bundle, the OS will create the activity in the background, but the extension will silently fail to render it, resulting in the error you are seeing I believe. Loo
3w
SwiftData property marked ephemeral getting persisted in CloudKit
Am I misunderstanding the expected behavior here, or is there a bug in the behavior of @Attribute(.ephemeral) tagged SwiftData model properties? The documentation for .ephemeral says Track changes to this property but do not persist. I started using .ephemeral because @Transient was inhibiting SwiftUI from reacting to changes to the property through @Observable. I am updating the value of my @Attribute(.ephemeral) property about once a second and I am seeing corresponding console log output showing the property as part of the generated CKRecord object. I then confirmed in the CloudKit dev portal that the .ephemeral property was added to the Record schema and contains real values. The behavior seems as though the .ephemeral property is being completely ignored. This is observed in a new Xcode project using SwiftData with CloudKit, Xcode 16.2, macOS 15.3.1 and during Build & Run testing on physical devices.
3
0
966
3w
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
[quote='884233022, DTS Engineer, /thread/821961?answerId=884233022#884233022'] I’m talking with the right folks about this [/quote] I now have specific advice for folks in this situation: Please re-apply for the Contactless Pass Provisioning capability. The approval folks will then assign you the Contactless Pass Provisioning (deprecated) capability, which you can use right now. Once this Xcode issue is resolved (FB22439399), they will assign you the newer Contactless Pass Provisioning (SharableCredential) to use going forward. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
3w
macOS DNS Proxy system extension makes device stop processing MDM commands until reboot
Hi, I see an interaction issue between a DNS Proxy system extension and MDM on macOS: after some time the device stops processing MDM commands until reboot, while DNS filtering continues to work. Environment: macOS: 15.x / 26.x (reproduced on multiple minor versions) App: /Applications/MyMacProxy.app System extension: NEDNSProxyProvider as system extension Bundle id: com.company.agent.MyMacProxy.dnsProxy Deployment: MDM (SimpleMDM) DNS proxy config via com.apple.dnsProxy.managed Devices: supervised Macs Steps to reproduce: Enrol Mac into MDM. Install MyMacProxy app + DNS proxy system extension via pkg and apply com.apple.dnsProxy.managed profile. DNS proxy starts, DNS is filtered correctly, user network works normally. After some hours, try to manage the device from MDM: push a new configuration profile, remove an existing profile, or install / remove an app. 5.MDM server shows commands as pending / not completed. On the Mac, DNS is still filtered via our DNS proxy, and general network acces
1
0
150
3w
LLDB RPC server crashes when running top-level async code in Playground files
When running top-level async code in Swift Playgrounds, the LLDB RPC server crashes. For example, when running the following code from Concurrency section of The Swift Programming Language book: func fetchUserID(from server: String) async -> Int { if server == primary { return 97 } return 501 } let userIDs = await withTaskGroup(of: Int.self) { group in for server in [primary, secondary, development] { group.addTask { return await fetchUserID(from: server) } } var results: [Int] = [] for await result in group { results.append(result) } return results } print(userIDs) Xcode reports that the LLDB RPC server has crashed. The Swift Playground app reports “There was a problem running this playground.” However, in the case of the Swift Playground app, results are populated as expected. For example, the console shows “[97, 501, 501]”. Xcode does not print any results in the console. Tested with Xcode 26.4 (17E192) and Swift Playground Version 4.7 (2088). Wrapping the as
1
0
247
3w
App Store Connect rejects com.apple.deviceactivity.monitor for Device Activity Monitor Extension
I’m submitting an iOS app that uses Family Controls / DeviceActivity APIs, and App Store Connect rejects the archive during distribution with this error: Invalid Info.plist value. The value of the NSExtensionPointIdentifier key, com.apple.deviceactivity.monitor, in the Info.plist of “activity-tracking.app/PlugIns/ScheduleMonitorExtension.appex” is invalid. What I’ve already verified: Family Controls capability is approved for our team App IDs and distribution provisioning profiles were regenerated The source Info.plist for the extension contains: NSExtensionPointIdentifier = com.apple.deviceactivity.monitor The archived .appex inside the .xcarchive also contains the same exact value Signed entitlements in the archived .appex include: com.apple.developer.family-controls = true app group entitlement Main app archive is signed correctly as well Latest stable Xcode used This makes it look like the archive is configured correctly, but App Store Connect still rejects the Device Activity Monitor extension p
1
0
171
3w
DeviceActivityMonitor extension rejected by App Store Connect validator — NSExtensionPointIdentifier "com.apple.deviceactivity.monitor" invalid (IrisAPI -19241)
Hi everyone, I'm building an iOS app that uses a DeviceActivityMonitor app extension as part of the Screen Time / Family Controls API. Every time I try to upload my IPA to App Store Connect, the validation fails with this error: Invalid Info.plist value. The value of the NSExtensionPointIdentifier key, com.apple.deviceactivity.monitor, in the Info.plist of 'Alexandria.app/PlugIns/AlexandriaActivityMonitor.appex' is invalid. Error Domain=IrisAPI Code=-19241, iris-code=STATE_ERROR.VALIDATION_ERROR What I have verified (everything looks correct): NSExtensionPointIdentifier = com.apple.deviceactivity.monitor NSExtensionPrincipalClass = AlexandriaActivityMonitor.AlexandriaActivityMonitorExtension (correctly resolved in the compiled binary, verified with plutil -p) The Swift class correctly subclasses DeviceActivityMonitor CFBundleShortVersionString matches the main app Both the main app and extension provisioning profiles explicitly contain com.apple.developer.family-controls = true (verified by inspecting embedde
6
0
524
3w
Reply to Xcode 26.4: IBOutlets/IBActions gutter circles missing — cannot connect storyboard to code (works in 26.3)
Ya the connection bubbles are gone in source files it seems. I wouldn't be terribly surprised if this was on purpose as a optimization / way to clean out source from Xcode to make room for ...er never mind. You can still connect outlets/actions by just writing the property in your interface: @property (nonatomic, weak) IBOutlet NSTextField *label; -(IBAction)methodName:(id)sender And then making the connection in Interface Builder from the Connections Inspector. I use to use the Assistant editor and make connections the way you describe all the time back in the day when I was learning UIKit but I do find it faster to just type the property with IBOutlet and then connecting it in the Connections Inspector in IB. A shame not to see those nice little connection bubbles anymore in source files. I don't care what anyone says about live previews or whatever...IB was the thing. It's a shame Apple doesn't make improvements to it anymore but I still find it useful.
3w
Different app behavior when running on device from Xcode
I have an app I am working on that makes a REST call, updates the UI with the info, and sends a notification. When I run Build and Run my app from Xcode using my iPhone as the destination, it works exactly as I want it to - my REST calls and notifications continue to work when the app is in the background. However, when I run my app that has been installed on my iPhone from the Xcode build/run directly (without Xcode in the picture), it does NOT behave correctly and only works when my app is in the foreground. What am I missing?
6
0
434
3w
Reply to Different app behavior when running on device from Xcode
@briggr1 Thanks for the post, it's not a bug that Xcode does not allow Timer to run in the background. I would recommend to read my answer again about how the background process works but I may have failed to explain it well, I have been known to make that mistake, let me try it again. When you launch an app via Xcode (Build and Run), the Xcode debugger attaches to your app's process. To prevent the debugger from randomly disconnecting, iOS disables standard background suspension rules. Your app is allowed to run continuously in the background, consuming as much CPU and battery as it wants, so you can debug it. Now this is not the way on released apps. I think previously I have recommended to other users to move the process to as server to avoid using the device as to process the work. Also I think have previously recommended to go over this great documentation about how to use background processing: https://developer.apple.com/documentation/uikit/preparing-your-ui-to-run-in-the-bac
Topic: Community SubTopic: Apple Developers Tags:
3w
actionGroupCell Y coordinates are corrupted. The overlay for 'Save to Files' doesn't expose no valid id's for testability.
I am using Maestro framework for testing iOS. For our tests we need to save pdf's to files. When opening the 'QLOverlayDefaultActionButtonAccessibilityIdentifier' the buttons on the overlay are way off, the coordinates got corrupted. When opening the files app, the next screen has no coordinates for testing. I checked with xcode inspector and the same issue persists.
Replies
1
Boosts
0
Views
453
Activity
3w
Kernel panic when using fclonefileat from ES
Hi, I am developing instant snapshot backup solution for macOS using Endpoint Security. We have stumbled upon a Kernel Panic when using fclonefileat API. We are catching a kernel panic on customer machines when attempting to clone the file during ES sync callback: panic(cpu 0 caller 0xfffffe002c495508): apfs_io_lock_exclusive : Recursive exclusive lock attempt @fs_utils.c:435 I have symbolized the backtrace to know it is related to clone operation with the following backtrace: apfs_io_lock_exclusive apfs_clone_internal apfs_vnop_clonefile I made a minimal repro that boils down to the following operations: apfs_crash_stress - launch thread to do rsrc writes static void *rsrc_write_worker(void *arg) { int id = (int)(long)arg; char buf[8192]; long n = 0; fill_pattern(buf, sizeof(buf), 'W' + id); while (n < ITERATION_LIMIT) { int file_idx = n % NUM_SOURCE_FILES; int fd = open(g_src_rsrc[file_idx], O_WRONLY | O_CREAT, 0644); if (fd >= 0) { off_t off = ((n * 4096) % RSRC_DATA_SIZE); pwrite(fd, buf, sizeof(buf
Replies
5
Boosts
0
Views
212
Activity
3w
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
Hi @DTS Engineer - we have re-applied for the capability however upon submitting the form we got a Server 500 error. Could you advise what to do in this situation? Nothing seems to have changed in XCode either. Thanks
Replies
Boosts
Views
Activity
3w
Live Activity creates successfully but never displays on lock screen or Dynamic Island ( iOS 26.4.1, Xcode 26.4)
Environment: Xcode 26.4 (17E192) iOS 26.4.1 iPhone 15 Pro Project uses PBXFileSystemSynchronizedRootGroup (Xcode 26 format) Setup: Widget Extension target named ModusWidgetExtension Bundle ID: com.calvin.Modus.ModusWidget NSSupportsLiveActivities = YES in both main app and widget extension Info.plist Live Activities enabled in Settings → Modus Live Activities enabled in Settings → Face ID & Passcode → Allow Access When Locked Background App Refresh enabled Push Notifications capability on both targets ActivityAttributes struct added to both targets via file target membership Behaviour: ActivityAuthorizationInfo().areActivitiesEnabled returns true Activity.request() succeeds and returns a valid activity ID No error is thrown Nothing appears on lock screen or Dynamic Island in foreground or background Widget preview in Xcode renders correctly for all presentations (compact, minimal, expanded, lock screen) Console output from liveactivitiesd filtered logs: Foreground process is per
Replies
1
Boosts
0
Views
146
Activity
3w
Reply to Live Activity creates successfully but never displays on lock screen or Dynamic Island ( iOS 26.4.1, Xcode 26.4)
Thanks for the post, this is extremely interesting to me. Can you post as much code as possible to see how you use the LiveActivitiy and is configured in the main entry? So the system successfully registers the activity from the main app, but when it asks to render it, the Widget Extension fails to provide a matching ActivityConfiguration? And your Xcode previews work, the UI code is valid, but it is not being successfully exposed to the system at runtime? Even if your Live Activity code is perfectly written and included in the target, the system will not know it exists unless it is explicitly instantiated in your extension's main entry point. Can you provide the code for that for me to review? If you have standard home screen widgets alongside your Live Activity, you must include both in the bundle. If the LiveActivity is missing from this bundle, the OS will create the activity in the background, but the extension will silently fail to render it, resulting in the error you are seeing I believe. Loo
Replies
Boosts
Views
Activity
3w
SwiftData property marked ephemeral getting persisted in CloudKit
Am I misunderstanding the expected behavior here, or is there a bug in the behavior of @Attribute(.ephemeral) tagged SwiftData model properties? The documentation for .ephemeral says Track changes to this property but do not persist. I started using .ephemeral because @Transient was inhibiting SwiftUI from reacting to changes to the property through @Observable. I am updating the value of my @Attribute(.ephemeral) property about once a second and I am seeing corresponding console log output showing the property as part of the generated CKRecord object. I then confirmed in the CloudKit dev portal that the .ephemeral property was added to the Record schema and contains real values. The behavior seems as though the .ephemeral property is being completely ignored. This is observed in a new Xcode project using SwiftData with CloudKit, Xcode 16.2, macOS 15.3.1 and during Build & Run testing on physical devices.
Replies
3
Boosts
0
Views
966
Activity
3w
Reply to Provisioning profiles marked "Ineligible" for Contactless Pass Provisioning even though entitlement is present in profile
[quote='884233022, DTS Engineer, /thread/821961?answerId=884233022#884233022'] I’m talking with the right folks about this [/quote] I now have specific advice for folks in this situation: Please re-apply for the Contactless Pass Provisioning capability. The approval folks will then assign you the Contactless Pass Provisioning (deprecated) capability, which you can use right now. Once this Xcode issue is resolved (FB22439399), they will assign you the newer Contactless Pass Provisioning (SharableCredential) to use going forward. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
3w
macOS DNS Proxy system extension makes device stop processing MDM commands until reboot
Hi, I see an interaction issue between a DNS Proxy system extension and MDM on macOS: after some time the device stops processing MDM commands until reboot, while DNS filtering continues to work. Environment: macOS: 15.x / 26.x (reproduced on multiple minor versions) App: /Applications/MyMacProxy.app System extension: NEDNSProxyProvider as system extension Bundle id: com.company.agent.MyMacProxy.dnsProxy Deployment: MDM (SimpleMDM) DNS proxy config via com.apple.dnsProxy.managed Devices: supervised Macs Steps to reproduce: Enrol Mac into MDM. Install MyMacProxy app + DNS proxy system extension via pkg and apply com.apple.dnsProxy.managed profile. DNS proxy starts, DNS is filtered correctly, user network works normally. After some hours, try to manage the device from MDM: push a new configuration profile, remove an existing profile, or install / remove an app. 5.MDM server shows commands as pending / not completed. On the Mac, DNS is still filtered via our DNS proxy, and general network acces
Replies
1
Boosts
0
Views
150
Activity
3w
LLDB RPC server crashes when running top-level async code in Playground files
When running top-level async code in Swift Playgrounds, the LLDB RPC server crashes. For example, when running the following code from Concurrency section of The Swift Programming Language book: func fetchUserID(from server: String) async -> Int { if server == primary { return 97 } return 501 } let userIDs = await withTaskGroup(of: Int.self) { group in for server in [primary, secondary, development] { group.addTask { return await fetchUserID(from: server) } } var results: [Int] = [] for await result in group { results.append(result) } return results } print(userIDs) Xcode reports that the LLDB RPC server has crashed. The Swift Playground app reports “There was a problem running this playground.” However, in the case of the Swift Playground app, results are populated as expected. For example, the console shows “[97, 501, 501]”. Xcode does not print any results in the console. Tested with Xcode 26.4 (17E192) and Swift Playground Version 4.7 (2088). Wrapping the as
Replies
1
Boosts
0
Views
247
Activity
3w
App Store Connect rejects com.apple.deviceactivity.monitor for Device Activity Monitor Extension
I’m submitting an iOS app that uses Family Controls / DeviceActivity APIs, and App Store Connect rejects the archive during distribution with this error: Invalid Info.plist value. The value of the NSExtensionPointIdentifier key, com.apple.deviceactivity.monitor, in the Info.plist of “activity-tracking.app/PlugIns/ScheduleMonitorExtension.appex” is invalid. What I’ve already verified: Family Controls capability is approved for our team App IDs and distribution provisioning profiles were regenerated The source Info.plist for the extension contains: NSExtensionPointIdentifier = com.apple.deviceactivity.monitor The archived .appex inside the .xcarchive also contains the same exact value Signed entitlements in the archived .appex include: com.apple.developer.family-controls = true app group entitlement Main app archive is signed correctly as well Latest stable Xcode used This makes it look like the archive is configured correctly, but App Store Connect still rejects the Device Activity Monitor extension p
Replies
1
Boosts
0
Views
171
Activity
3w
DeviceActivityMonitor extension rejected by App Store Connect validator — NSExtensionPointIdentifier "com.apple.deviceactivity.monitor" invalid (IrisAPI -19241)
Hi everyone, I'm building an iOS app that uses a DeviceActivityMonitor app extension as part of the Screen Time / Family Controls API. Every time I try to upload my IPA to App Store Connect, the validation fails with this error: Invalid Info.plist value. The value of the NSExtensionPointIdentifier key, com.apple.deviceactivity.monitor, in the Info.plist of 'Alexandria.app/PlugIns/AlexandriaActivityMonitor.appex' is invalid. Error Domain=IrisAPI Code=-19241, iris-code=STATE_ERROR.VALIDATION_ERROR What I have verified (everything looks correct): NSExtensionPointIdentifier = com.apple.deviceactivity.monitor NSExtensionPrincipalClass = AlexandriaActivityMonitor.AlexandriaActivityMonitorExtension (correctly resolved in the compiled binary, verified with plutil -p) The Swift class correctly subclasses DeviceActivityMonitor CFBundleShortVersionString matches the main app Both the main app and extension provisioning profiles explicitly contain com.apple.developer.family-controls = true (verified by inspecting embedde
Replies
6
Boosts
0
Views
524
Activity
3w
Reply to Xcode 26.4: IBOutlets/IBActions gutter circles missing — cannot connect storyboard to code (works in 26.3)
Ya the connection bubbles are gone in source files it seems. I wouldn't be terribly surprised if this was on purpose as a optimization / way to clean out source from Xcode to make room for ...er never mind. You can still connect outlets/actions by just writing the property in your interface: @property (nonatomic, weak) IBOutlet NSTextField *label; -(IBAction)methodName:(id)sender And then making the connection in Interface Builder from the Connections Inspector. I use to use the Assistant editor and make connections the way you describe all the time back in the day when I was learning UIKit but I do find it faster to just type the property with IBOutlet and then connecting it in the Connections Inspector in IB. A shame not to see those nice little connection bubbles anymore in source files. I don't care what anyone says about live previews or whatever...IB was the thing. It's a shame Apple doesn't make improvements to it anymore but I still find it useful.
Replies
Boosts
Views
Activity
3w
Different app behavior when running on device from Xcode
I have an app I am working on that makes a REST call, updates the UI with the info, and sends a notification. When I run Build and Run my app from Xcode using my iPhone as the destination, it works exactly as I want it to - my REST calls and notifications continue to work when the app is in the background. However, when I run my app that has been installed on my iPhone from the Xcode build/run directly (without Xcode in the picture), it does NOT behave correctly and only works when my app is in the foreground. What am I missing?
Replies
6
Boosts
0
Views
434
Activity
3w
Reply to Different app behavior when running on device from Xcode
@briggr1 Thanks for the post, it's not a bug that Xcode does not allow Timer to run in the background. I would recommend to read my answer again about how the background process works but I may have failed to explain it well, I have been known to make that mistake, let me try it again. When you launch an app via Xcode (Build and Run), the Xcode debugger attaches to your app's process. To prevent the debugger from randomly disconnecting, iOS disables standard background suspension rules. Your app is allowed to run continuously in the background, consuming as much CPU and battery as it wants, so you can debug it. Now this is not the way on released apps. I think previously I have recommended to other users to move the process to as server to avoid using the device as to process the work. Also I think have previously recommended to go over this great documentation about how to use background processing: https://developer.apple.com/documentation/uikit/preparing-your-ui-to-run-in-the-bac
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
3w
Xcode 26 with simulator 16 ?
mac mini xcode 26.4, but the simulator version is 16. how can i update the simulator to version 26?
Replies
2
Boosts
0
Views
136
Activity
3w