Search results for

“file uri scheme”

81,725 results found

Post

Replies

Boosts

Views

Activity

Reply to Xcode 26.4 rc
Thank you for sharing your post. I understand that it can be frustrating, especially when the job is impacting your daily routine. I am eager to assist you in any way I can. I have a potential idea, but I would like to request a bug filing for further investigation. Typically, authentication tokens expire after a few hours. In a stable build, Xcode silently uses a “refresh token” to obtain a new session in the background. Consequently, the system may be terminating your session when the initial token expires. This is an issue that requires immediate attention. However, I am only speculating about the cause. Given that this issue is occurring across two separate computers and began specifically in beta 3, it is highly probable that the problem lies within the beta itself rather than a misconfiguration on your end. Instead of simply signing out and signing back in, I recommend completely deleting the integration from Xcode. Navigate to Xcode > Settings > Accounts (or the specific Claude Agent set
6d
Reply to SwiftUI Chart scrolling on macOS
Thank you, I will file a bug report. For anyone else that finds this, the scrollbar: always shows on my Mac Mini (mouse and keyboard only) does not show on my Macbook Air (trackpad) automatically shows when I connect a bluetooth mouse to the Macbook Air, but still does not allow mouse interaction. When I turn off the bluetooth mouse, the scrollbar disappeared. The trackpad allows for scrolling the chart with 2-finger swipe gestures, with or without the bluetooth mouse connected.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
6d
Reply to SwiftUI Chart scrolling on macOS
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
6d
Matter OTA on TestNet: HomePod always replies "UpdateNotAvailable" (Device is already CSA Certified)
Hi Apple Team / Community, We are currently pulling our hair out over a TestNet OTA issue and could really use some help. Our Matter Door Lock (VID: 5424, PID: 513) has already obtained official CSA Certification, so we are 100% confident that our device firmware and OTA Requestor logic are completely solid. However, we simply cannot get Apple's TestNet to serve the update via HomePod. Here is exactly what is happening: Our device successfully sends a QueryImage command to the HomePod. The HomePod receives it, but immediately fires back a QueryImageResponse that essentially means UpdateNotAvailable, forcing the device into an 86400-second sleep timeout. Here is what we have verified so far: Local OTA works perfectly: If we use Nordic's chip-ota-provider-app locally with the exact same .ota file, the BDX transfer triggers instantly and the device updates without a hitch. DCL details are 100% accurate: We published a brand new version (1.0.4 / 16778240) which is strictly higher than the device's curren
3
0
96
6d
Reply to System-wide deadlock in removexattr from revisiond / APFS
Let me start by saying two slightly contradictory things: It's very likely that there is an APFS bug here, so if you haven't already, please file a bug on this and post the bug number back here. It's ALSO very likely that your ES client (possibly both ES clients) are required to actually experience this bug, and you should address it as well. Next, I think I want to be clear that some of what I'm saying is a bit of an educated guess. A big part of the problem here is that the data we're looking at is being collected LONG (2+ days) after the problem itself actually occurred, which means we don't REALLY know EXACTLY what happened. That doesn't invalidate what I'm describing above, but I do think it's important to have some awareness of the limitation of the data at hand and that, most importantly, new data could totally change our understanding of the overall state of things. Getting into the details: But here, I don't see such things. When EndpointSecurityEventManager is on the spindump, it's only bec
Topic: App & System Services SubTopic: Core OS Tags:
6d
Made for Kids flag stuck — cannot update my app
Dear Apple team, I am a developer who has been unable to update my app Mon Pain Quotidien for several months due to a stuck Made for Kids flag that I cannot remove. My app is a Bible study platform for all ages — it was never intended for children specifically. The flag was set by mistake. Every submission is rejected with error: Guideline 1.3 - Safety - Kids Category We noticed you selected the Kids Category for your app, but your app does not appear to be designed for kids aged 11 and under. Specifically, we noticed that your app is a educational app, which is not appropriate for use by children. Since apps in the Kids Category should be designed specifically for children, apps submitted to this category must be appropriate for kids aged 11 and under. Next Steps To resolve this issue, please resubmit your app without the Kids category designation. Resources See how to change your app's age rating, including the Made for Kids setting, on App Store Connect Help. Learn more about requirements for apps in the K
1
0
37
6d
Reply to Made for Kids flag stuck — cannot update my app
Thank you for your post. The App Store team does not monitor the forums, and I believe you set your app as “Made for Kids” for the first time when you deployed the app. Since your app is already live, the “Made for Kids” flag and the “Kids” category are often locked to prevent developers from changing an app’s target audience without parental consent. This will be a significant privacy issue as you can see. To resolve a locked metadata field like that, you need to contact App Store Connect Support, not App Review. Visit the Apple Developer Contact Us page. The representative can file an internal ticket directly to the App Store Connect engineering team to manually unstick the metadata field on your account if appropriate. Now, depending on your app and the people affected by that change, the engineering team will decide whether to make that change. I’m not in that team now I know their process. Once App Store Connect Support unlocks the field and you successfully uncheck “Made for Kids,” you can subm
6d
Reply to macOS 12.6 LightsOutManagement; address already in use
Hi, @Dominik_2 I'm a little late here but I'm having the same issue. Did you ever figure this out? I can't even get a 2019 Mac Pro to properly activate LOM and a 2023 Mac mini which gives me the same Address Already In Use error. Here's all my testing and info. Apple are you there??? Infrastructure: • Mac mini 2023 (M2, 10Gb Ethernet, MacMini.local, macOS 15.x Sequoia 15.7.4) — MicroMDM v1.13.1 • Mac Pro 2019 (MacPro7,1, Intel T2, MacPro.local, macOS 15.x Sequoia 15.7.5, T2 firmware 23P3120) • Both supervised via Automated Device Enrollment (DEP) through Apple Business Manager • Both enrolled: IsSupervised = 1, APNs working on both • Both are Controllers and Clients LOM Current State: Mac mini (Apple Silicon M2): • LOM profile installed ✓ • lom0 interface active ✓ • Port 55555 listening on * ✓ • LOMDeviceServerColsolidated path (Apple Silicon) ✓ • com.apple.AppleLOM.XPC active=1 ✓ • com.apple.AppleLOM.Watchdog active=1 ✓ • Mac Pro CAN reach mini's lom0 port 55555 — TCP connection established ✓ • BUT connectio
6d
Custom Capacitor 6 plugin with SPM: "plugin is not implemented on ios" despite being compiled
Hi everyone, I'm building an iOS app using Capacitor 6 with Swift Package Manager (SPM). I have a custom native plugin (AppleIAPPlugin) for StoreKit 2 In-App Purchases that lives in the App target (not as an SPM package). Despite compiling successfully, the JavaScript bridge throws: AppleIAP plugin is not implemented on ios Setup AppleIAPPlugin.swift: swift import Foundation import Capacitor import StoreKit @objc(AppleIAPPlugin) public class AppleIAPPlugin: CAPPlugin, CAPBridgedPlugin { public let identifier = AppleIAPPlugin public let jsName = AppleIAP public let pluginMethods: [CAPPluginMethod] = [ CAPPluginMethod(name: getProducts, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: purchase, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: restorePurchases, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: getCurrentEntitlements, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: openManageSubscriptions, returnType: CAPPluginReturnPromise), ] @objc func getProducts(_ call
1
0
33
6d
Reply to Kernel panic when using fclonefileat from ES
Regarding fclonefileat API, my expectations are actually met in macOS 26.4 now - I do expect that the Kernel is capable of rejecting invalid calls of clonefile API and does fail the operation. It is tricky to predict the future as there might be new regular file types that might not be clonable/will become clonable, so I always delegate the file clonability decision to the Kernel. So, stepping back for a moment, my larger advice here in terms of future proofing would actually be to avoid the direct call to clonefile and instead call copyfile. While kernel panic'ing is a relatively extreme failure, clonefile is a low-level syscall, and I'd fully expect that there can/are/will be edge cases where clonefile fails and copyfile does not. The difference here is a matter of API role - clonefile is only designed to do the specific task of sending a specific request to the VFS system, while copyfile() is designed around the broader job. If you specifically want to fail in any case where a file
Topic: App & System Services SubTopic: Core OS Tags:
6d
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, s
3
0
103
6d
Reply to Xcode 26.4 rc
Thank you for sharing your post. I understand that it can be frustrating, especially when the job is impacting your daily routine. I am eager to assist you in any way I can. I have a potential idea, but I would like to request a bug filing for further investigation. Typically, authentication tokens expire after a few hours. In a stable build, Xcode silently uses a “refresh token” to obtain a new session in the background. Consequently, the system may be terminating your session when the initial token expires. This is an issue that requires immediate attention. However, I am only speculating about the cause. Given that this issue is occurring across two separate computers and began specifically in beta 3, it is highly probable that the problem lies within the beta itself rather than a misconfiguration on your end. Instead of simply signing out and signing back in, I recommend completely deleting the integration from Xcode. Navigate to Xcode > Settings > Accounts (or the specific Claude Agent set
Replies
Boosts
Views
Activity
6d
Reply to SwiftUI Chart scrolling on macOS
Thank you, I will file a bug report. For anyone else that finds this, the scrollbar: always shows on my Mac Mini (mouse and keyboard only) does not show on my Macbook Air (trackpad) automatically shows when I connect a bluetooth mouse to the Macbook Air, but still does not allow mouse interaction. When I turn off the bluetooth mouse, the scrollbar disappeared. The trackpad allows for scrolling the chart with 2-finger swipe gestures, with or without the bluetooth mouse connected.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
6d
Reply to SwiftUI Chart scrolling on macOS
Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
6d
Matter OTA on TestNet: HomePod always replies "UpdateNotAvailable" (Device is already CSA Certified)
Hi Apple Team / Community, We are currently pulling our hair out over a TestNet OTA issue and could really use some help. Our Matter Door Lock (VID: 5424, PID: 513) has already obtained official CSA Certification, so we are 100% confident that our device firmware and OTA Requestor logic are completely solid. However, we simply cannot get Apple's TestNet to serve the update via HomePod. Here is exactly what is happening: Our device successfully sends a QueryImage command to the HomePod. The HomePod receives it, but immediately fires back a QueryImageResponse that essentially means UpdateNotAvailable, forcing the device into an 86400-second sleep timeout. Here is what we have verified so far: Local OTA works perfectly: If we use Nordic's chip-ota-provider-app locally with the exact same .ota file, the BDX transfer triggers instantly and the device updates without a hitch. DCL details are 100% accurate: We published a brand new version (1.0.4 / 16778240) which is strictly higher than the device's curren
Replies
3
Boosts
0
Views
96
Activity
6d
Reply to System-wide deadlock in removexattr from revisiond / APFS
Let me start by saying two slightly contradictory things: It's very likely that there is an APFS bug here, so if you haven't already, please file a bug on this and post the bug number back here. It's ALSO very likely that your ES client (possibly both ES clients) are required to actually experience this bug, and you should address it as well. Next, I think I want to be clear that some of what I'm saying is a bit of an educated guess. A big part of the problem here is that the data we're looking at is being collected LONG (2+ days) after the problem itself actually occurred, which means we don't REALLY know EXACTLY what happened. That doesn't invalidate what I'm describing above, but I do think it's important to have some awareness of the limitation of the data at hand and that, most importantly, new data could totally change our understanding of the overall state of things. Getting into the details: But here, I don't see such things. When EndpointSecurityEventManager is on the spindump, it's only bec
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
6d
Made for Kids flag stuck — cannot update my app
Dear Apple team, I am a developer who has been unable to update my app Mon Pain Quotidien for several months due to a stuck Made for Kids flag that I cannot remove. My app is a Bible study platform for all ages — it was never intended for children specifically. The flag was set by mistake. Every submission is rejected with error: Guideline 1.3 - Safety - Kids Category We noticed you selected the Kids Category for your app, but your app does not appear to be designed for kids aged 11 and under. Specifically, we noticed that your app is a educational app, which is not appropriate for use by children. Since apps in the Kids Category should be designed specifically for children, apps submitted to this category must be appropriate for kids aged 11 and under. Next Steps To resolve this issue, please resubmit your app without the Kids category designation. Resources See how to change your app's age rating, including the Made for Kids setting, on App Store Connect Help. Learn more about requirements for apps in the K
Replies
1
Boosts
0
Views
37
Activity
6d
Reply to Made for Kids flag stuck — cannot update my app
Thank you for your post. The App Store team does not monitor the forums, and I believe you set your app as “Made for Kids” for the first time when you deployed the app. Since your app is already live, the “Made for Kids” flag and the “Kids” category are often locked to prevent developers from changing an app’s target audience without parental consent. This will be a significant privacy issue as you can see. To resolve a locked metadata field like that, you need to contact App Store Connect Support, not App Review. Visit the Apple Developer Contact Us page. The representative can file an internal ticket directly to the App Store Connect engineering team to manually unstick the metadata field on your account if appropriate. Now, depending on your app and the people affected by that change, the engineering team will decide whether to make that change. I’m not in that team now I know their process. Once App Store Connect Support unlocks the field and you successfully uncheck “Made for Kids,” you can subm
Replies
Boosts
Views
Activity
6d
Reply to macOS 12.6 LightsOutManagement; address already in use
Hi, @Dominik_2 I'm a little late here but I'm having the same issue. Did you ever figure this out? I can't even get a 2019 Mac Pro to properly activate LOM and a 2023 Mac mini which gives me the same Address Already In Use error. Here's all my testing and info. Apple are you there??? Infrastructure: • Mac mini 2023 (M2, 10Gb Ethernet, MacMini.local, macOS 15.x Sequoia 15.7.4) — MicroMDM v1.13.1 • Mac Pro 2019 (MacPro7,1, Intel T2, MacPro.local, macOS 15.x Sequoia 15.7.5, T2 firmware 23P3120) • Both supervised via Automated Device Enrollment (DEP) through Apple Business Manager • Both enrolled: IsSupervised = 1, APNs working on both • Both are Controllers and Clients LOM Current State: Mac mini (Apple Silicon M2): • LOM profile installed ✓ • lom0 interface active ✓ • Port 55555 listening on * ✓ • LOMDeviceServerColsolidated path (Apple Silicon) ✓ • com.apple.AppleLOM.XPC active=1 ✓ • com.apple.AppleLOM.Watchdog active=1 ✓ • Mac Pro CAN reach mini's lom0 port 55555 — TCP connection established ✓ • BUT connectio
Replies
Boosts
Views
Activity
6d
Custom Capacitor 6 plugin with SPM: "plugin is not implemented on ios" despite being compiled
Hi everyone, I'm building an iOS app using Capacitor 6 with Swift Package Manager (SPM). I have a custom native plugin (AppleIAPPlugin) for StoreKit 2 In-App Purchases that lives in the App target (not as an SPM package). Despite compiling successfully, the JavaScript bridge throws: AppleIAP plugin is not implemented on ios Setup AppleIAPPlugin.swift: swift import Foundation import Capacitor import StoreKit @objc(AppleIAPPlugin) public class AppleIAPPlugin: CAPPlugin, CAPBridgedPlugin { public let identifier = AppleIAPPlugin public let jsName = AppleIAP public let pluginMethods: [CAPPluginMethod] = [ CAPPluginMethod(name: getProducts, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: purchase, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: restorePurchases, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: getCurrentEntitlements, returnType: CAPPluginReturnPromise), CAPPluginMethod(name: openManageSubscriptions, returnType: CAPPluginReturnPromise), ] @objc func getProducts(_ call
Replies
1
Boosts
0
Views
33
Activity
6d
Reply to Xcode's built-in AI chat feature (IDEIntelligenceChat) crashes.
Xcode should never crash, so filing bug reports through Feedback Assistant are encouraged.
Replies
Boosts
Views
Activity
6d
Reply to iCloud Sync not working with iPhone, works fine for Mac.
Bug report Filed - FB22343127
Replies
Boosts
Views
Activity
6d
Reply to Kernel panic when using fclonefileat from ES
Regarding fclonefileat API, my expectations are actually met in macOS 26.4 now - I do expect that the Kernel is capable of rejecting invalid calls of clonefile API and does fail the operation. It is tricky to predict the future as there might be new regular file types that might not be clonable/will become clonable, so I always delegate the file clonability decision to the Kernel. So, stepping back for a moment, my larger advice here in terms of future proofing would actually be to avoid the direct call to clonefile and instead call copyfile. While kernel panic'ing is a relatively extreme failure, clonefile is a low-level syscall, and I'd fully expect that there can/are/will be edge cases where clonefile fails and copyfile does not. The difference here is a matter of API role - clonefile is only designed to do the specific task of sending a specific request to the VFS system, while copyfile() is designed around the broader job. If you specifically want to fail in any case where a file
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
6d
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, s
Replies
3
Boosts
0
Views
103
Activity
6d