Search results for

“file uri scheme”

81,738 results found

Post

Replies

Boosts

Views

Activity

Reply to Multiple Apple Pay relationships with differing apple-developer-merchantid-domain-association files
Well I figured it out - for anyone still encountering this issue: My company has one domain to service multiple locations/storefronts. Each location has it's own separate Payment Processing account, requiring a unique Apple Pay Payment Processing Certificate/MerchantID. The docs and responses here made me think subdomains would be required, which is a headache in itself - especially since the Apple Pay Session must be started from that subdomain (not the parent domain). SOLUTION: If you register multiple MerchantIds within a single Apple Developer Identifier - all Domain Association Files tied to a certain domain are the same. So if you verify for one MerchantID, then add that same domain to another - it will count it as already verified. No need for subdomains. No need for swapping out Domain Association files. Really wish that Apple had made that clear.
1w
Multiple Apple Pay relationships with differing apple-developer-merchantid-domain-association files
I've encountered an issue where we need multiple domain associations with separate Apple Pay implementations. Briefly, we have a /.well-known/apple-developer-merchantid-domain-association already setup with Stripe, and now we need another, different version of the file to get setup with FreedomPay. FreedomPay insists this file represents a three-way relationship between all parties and I have no reason to disbelieve them. I'm wondering if anyone has encountered this or if there is a standard procedure. I'm currently trying to find documentation on the exact way Apple Pay verification interacts with this file to see if we can produce it dynamically.
10
0
4.6k
1w
Reply to Clipboard issues with simulators
Thank you for your posts. While the script was definitely a long shot, considering that I have not used that script for some time, I believe this thread warrants a bug filing as looks like is happening to all of you. I would appreciate it if one of you could file a bug report and provide the FB number here. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Lets get it resolved as fast as possible. Albert Pascual
  Worldwide Developer Relations.
1w
HTTP 500 when attempting to resolve SCM repo connectivity issue.
Hello, I'm unable to kick off builds in Xcode Cloud today due to an error connecting to our SCM repo. Repository Issue Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds. I can see that this is due to an HTTP 500 error on the /scm-repositories endpoint, which would normally indicate an issue in Xcode Cloud. If on the contrary this indicates an issue on my side, I'd like to hear details and what the resolution might be. Filed an issue here: FB22314855 (Xcode Cloud: HTTP 500 when connecting to SCM provider)
2
0
55
1w
Reply to 26.4 beta and RC versions are unable to be created on anything but 26.4 beta host OS
During the beta cycle, developers can get the required MobileDevice by installing the latest Xcode seed. That's problematic on macOS 15.x because Xcode 26.4 now requires macOS 26.2. However, would it be possible to open the Xcode.app/Contents/Resources/Packages/MobileDevice.pkg manually on a macOS 15.x machine to get the required mobile device files? Once the OS is released, either: That doesn't seem to match my experience. macOS 26.4 is now out, and I've updated to macOS 15.7.5 (24G624), but when I try using the restore image of the release version of macOS 26.4 to make a VM, I'm still prompted to install the mobile device files and it still says that they aren't available from the software update server.
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. We implemented your own HTTP protocol on top of NetworkConnection. OK, cool, that’s kinda what I expected but I’m glad you confirmed it. We are very eager to send HTTP requests over Wi‑Fi Aware using URLSession — is this achievable? No. I recommend that you file an enhancement request for that. Please post your bug number, just for the record. Coming back to your throughput issue, I don’t have an immediate answer to that. I’m gonna do some digging and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1w
pkgbuild on Tahoe fails to build packages if any directory name contains non-ascii characters
pkgbuild on Tahoe (26.3.1) fails to build packages if any directory name contains non-ascii characters. pkgbuild is able to build successfully with the same source data on previous versions on macOS, so this is a regression and prevents us from build able to build our products on macOS 26. Example that demonstrates the issue: mkdir -p MyAppData/Taishōgoto echo Testing >> MyAppData/Taishōgoto/Content.txt pkgbuild --identifier com.example.MyAppData --install-location '/Library/Application Support/MyAppData' --root MyAppData myappdata.pkg Error messages: parent directory ./Taishōgoto does not exist pkgbuild: error: Cannot write package to myappdata.pkg. (The file “package.bom” couldn’t be saved in the folder “NSIRD_pkgbuild_52fPuN”.) I have submitted this via Feedback Assistant (FB22312299). I have not found a workaround. Tried copying pkgbuild from Sequoia but the problem persisted, probably because the buggy code is in PackageKit rather than the tool itself.
3
0
69
1w
Code Signing "Invalid", No Reason Given
Hello, At work, we want to release a new version of our cross-platform desktop application this week. Unfortunately, I've had issues getting the dmg signed by the Apple notary service, which will delay the release until it's successful. However, I remade and successfully signed the previously released version (also dmg) with the same credentials, so I know it's not a problem with the file format or my account. I have tried the following to no avail: Lots of Googling Running xcrun notarytool submit with the -v option (verbose) to see more error messages Going to the URL given (appstoreconnect.apple.com/notary/v2/submissions/{submission_id}) and examining the file it downloaded (not much info, let alone helpful info) Contacting Apple developer support over the phone (they couldn't help with this particular issue, since it's code-level support) The only big change we made this time was switching to Maven for our build tool and dependency management (we previously used Ant with manual dependency
3
0
263
1w
Reply to How to write a persistent token to unlock FileVault with a smart card?
[quote='820314021, Ludovic, /thread/820314, /profile/Ludovic'] As far as I understand for preboot I need to provide a persistent token [/quote] No, you’ve got that backwards. CryptoTokenKit supports two different types of token: Smart card tokens Persistent tokens A smart card token is backed by hardware; a persistent token may be entirely virtual. A smart card token subclasses TKSmartCardToken. A persistent token subclasses TKToken directly. Because a smart card token is backed by hardware, it can work at login time. In a persistent token, the information about the credentials in the token is stored in the user’s home directory, and thus it can’t be used to log in. It’s a chicken’n’egg problem. My understanding is that you have a smart card token working for general login, and now you’re trying to get that work for FileVault unlock. There’s no way to make that work. It’s another chicken’n’egg problem. Your app is stored on the encrypted volume, so it can’t be accessed until the user has unlocked that. This w
Topic: App & System Services SubTopic: Core OS Tags:
1w
new rsync version not working as expected
after upgrade macos version to 15.4 the rsync start failing that cause the xcodebuild fail and not generate ipa rsync: on remote machine: --extended-attributes: unknown option rsync error: syntax or usage error (code 1) at main.c(1802) [server=3.4.1] rsync(73444): error: unexpected end of file rsync(73444): error: io_read_nonblocking rsync(73444): error: io_read_buf rsync(73444): error: io_read_int rsync(73444): warning: child 73445 exited with status 1
2
0
282
1w
Reply to Clipboard issues with simulators
Thanks for the post. This is interesting now you can't copy and paste from the same machine to the simulator? Before we file a bug, can you try something for me? Open your Mac Terminal. Paste and run this command: xcrun simctl spawn booted launchctl kickstart -k system/com.apple.pboard Try pasting in the Simulator again. Let me know the results. Thanks, Albert Pascual
  Worldwide Developer Relations.
1w
Reply to Multiple Apple Pay relationships with differing apple-developer-merchantid-domain-association files
Well I figured it out - for anyone still encountering this issue: My company has one domain to service multiple locations/storefronts. Each location has it's own separate Payment Processing account, requiring a unique Apple Pay Payment Processing Certificate/MerchantID. The docs and responses here made me think subdomains would be required, which is a headache in itself - especially since the Apple Pay Session must be started from that subdomain (not the parent domain). SOLUTION: If you register multiple MerchantIds within a single Apple Developer Identifier - all Domain Association Files tied to a certain domain are the same. So if you verify for one MerchantID, then add that same domain to another - it will count it as already verified. No need for subdomains. No need for swapping out Domain Association files. Really wish that Apple had made that clear.
Replies
Boosts
Views
Activity
1w
Multiple Apple Pay relationships with differing apple-developer-merchantid-domain-association files
I've encountered an issue where we need multiple domain associations with separate Apple Pay implementations. Briefly, we have a /.well-known/apple-developer-merchantid-domain-association already setup with Stripe, and now we need another, different version of the file to get setup with FreedomPay. FreedomPay insists this file represents a three-way relationship between all parties and I have no reason to disbelieve them. I'm wondering if anyone has encountered this or if there is a standard procedure. I'm currently trying to find documentation on the exact way Apple Pay verification interacts with this file to see if we can produce it dynamically.
Replies
10
Boosts
0
Views
4.6k
Activity
1w
Reply to Clipboard issues with simulators
@eddyvinck Yes definitely a horrible experience working with simulators. Lets get the ball rolling fast and file a bug so that issue can be resolved quickly. Thanks Albert Pascual
  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
1w
Reply to Scheduled events reach threshold almost immediately on iOS 26.2
[quote='875340022, DTS Engineer, /thread/814559?answerId=875340022#875340022'] I encourage you to file a Feedback report of your own using Feedback Assistant, then post the Feedback ID here. [/quote] Here is my feedback report: FB18061981
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Clipboard issues with simulators
Thank you for your posts. While the script was definitely a long shot, considering that I have not used that script for some time, I believe this thread warrants a bug filing as looks like is happening to all of you. I would appreciate it if one of you could file a bug report and provide the FB number here. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Lets get it resolved as fast as possible. Albert Pascual
  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
1w
HTTP 500 when attempting to resolve SCM repo connectivity issue.
Hello, I'm unable to kick off builds in Xcode Cloud today due to an error connecting to our SCM repo. Repository Issue Xcode Cloud is unable to connect to the repository “”. Reconnect the repository to resume builds. I can see that this is due to an HTTP 500 error on the /scm-repositories endpoint, which would normally indicate an issue in Xcode Cloud. If on the contrary this indicates an issue on my side, I'd like to hear details and what the resolution might be. Filed an issue here: FB22314855 (Xcode Cloud: HTTP 500 when connecting to SCM provider)
Replies
2
Boosts
0
Views
55
Activity
1w
Reply to 26.4 beta and RC versions are unable to be created on anything but 26.4 beta host OS
During the beta cycle, developers can get the required MobileDevice by installing the latest Xcode seed. That's problematic on macOS 15.x because Xcode 26.4 now requires macOS 26.2. However, would it be possible to open the Xcode.app/Contents/Resources/Packages/MobileDevice.pkg manually on a macOS 15.x machine to get the required mobile device files? Once the OS is released, either: That doesn't seem to match my experience. macOS 26.4 is now out, and I've updated to macOS 15.7.5 (24G624), but when I try using the restore image of the release version of macOS 26.4 to make a VM, I'm still prompted to install the mobile device files and it still says that they aren't available from the software update server.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. We implemented your own HTTP protocol on top of NetworkConnection. OK, cool, that’s kinda what I expected but I’m glad you confirmed it. We are very eager to send HTTP requests over Wi‑Fi Aware using URLSession — is this achievable? No. I recommend that you file an enhancement request for that. Please post your bug number, just for the record. Coming back to your throughput issue, I don’t have an immediate answer to that. I’m gonna do some digging and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1w
pkgbuild on Tahoe fails to build packages if any directory name contains non-ascii characters
pkgbuild on Tahoe (26.3.1) fails to build packages if any directory name contains non-ascii characters. pkgbuild is able to build successfully with the same source data on previous versions on macOS, so this is a regression and prevents us from build able to build our products on macOS 26. Example that demonstrates the issue: mkdir -p MyAppData/Taishōgoto echo Testing >> MyAppData/Taishōgoto/Content.txt pkgbuild --identifier com.example.MyAppData --install-location '/Library/Application Support/MyAppData' --root MyAppData myappdata.pkg Error messages: parent directory ./Taishōgoto does not exist pkgbuild: error: Cannot write package to myappdata.pkg. (The file “package.bom” couldn’t be saved in the folder “NSIRD_pkgbuild_52fPuN”.) I have submitted this via Feedback Assistant (FB22312299). I have not found a workaround. Tried copying pkgbuild from Sequoia but the problem persisted, probably because the buggy code is in PackageKit rather than the tool itself.
Replies
3
Boosts
0
Views
69
Activity
1w
Code Signing "Invalid", No Reason Given
Hello, At work, we want to release a new version of our cross-platform desktop application this week. Unfortunately, I've had issues getting the dmg signed by the Apple notary service, which will delay the release until it's successful. However, I remade and successfully signed the previously released version (also dmg) with the same credentials, so I know it's not a problem with the file format or my account. I have tried the following to no avail: Lots of Googling Running xcrun notarytool submit with the -v option (verbose) to see more error messages Going to the URL given (appstoreconnect.apple.com/notary/v2/submissions/{submission_id}) and examining the file it downloaded (not much info, let alone helpful info) Contacting Apple developer support over the phone (they couldn't help with this particular issue, since it's code-level support) The only big change we made this time was switching to Maven for our build tool and dependency management (we previously used Ant with manual dependency
Replies
3
Boosts
0
Views
263
Activity
1w
Reply to Orphaned 9GB Simulator Runtime in /System/Library/AssetsV2 - Cannot Delete (SIP protected)
matthewruzzi wrote: Report a bug Exactly! See Bug Reporting: How and Why? for lots of hints and tips about filing effective bug reports. Also, if you do file a bug, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1w
Reply to How to write a persistent token to unlock FileVault with a smart card?
[quote='820314021, Ludovic, /thread/820314, /profile/Ludovic'] As far as I understand for preboot I need to provide a persistent token [/quote] No, you’ve got that backwards. CryptoTokenKit supports two different types of token: Smart card tokens Persistent tokens A smart card token is backed by hardware; a persistent token may be entirely virtual. A smart card token subclasses TKSmartCardToken. A persistent token subclasses TKToken directly. Because a smart card token is backed by hardware, it can work at login time. In a persistent token, the information about the credentials in the token is stored in the user’s home directory, and thus it can’t be used to log in. It’s a chicken’n’egg problem. My understanding is that you have a smart card token working for general login, and now you’re trying to get that work for FileVault unlock. There’s no way to make that work. It’s another chicken’n’egg problem. Your app is stored on the encrypted volume, so it can’t be accessed until the user has unlocked that. This w
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to new rsync version not working as expected
The temporary solution is to change the uploadSymbols value in the plist file to false.
Replies
Boosts
Views
Activity
1w
new rsync version not working as expected
after upgrade macos version to 15.4 the rsync start failing that cause the xcodebuild fail and not generate ipa rsync: on remote machine: --extended-attributes: unknown option rsync error: syntax or usage error (code 1) at main.c(1802) [server=3.4.1] rsync(73444): error: unexpected end of file rsync(73444): error: io_read_nonblocking rsync(73444): error: io_read_buf rsync(73444): error: io_read_int rsync(73444): warning: child 73445 exited with status 1
Replies
2
Boosts
0
Views
282
Activity
1w
Reply to Clipboard issues with simulators
Thanks for the post. This is interesting now you can't copy and paste from the same machine to the simulator? Before we file a bug, can you try something for me? Open your Mac Terminal. Paste and run this command: xcrun simctl spawn booted launchctl kickstart -k system/com.apple.pboard Try pasting in the Simulator again. Let me know the results. Thanks, Albert Pascual
  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
1w