“We are unable to process your request”

[quote='881346022, alex_strong, /thread/820155?answerId=881346022#881346022, /profile/alex_strong'] I tried to put this in a comment [/quote] It’s better to reply as a reply, rather than as a comment; see Quinn’s Top Ten DevForums Tips for this and other titbits. [quote='881346022, alex_strong, /thread/820155?answerId=881346022#881346022, /profile/alex_strong'] Fetching the Notary Log was exactly what I was looking for. [/quote] Yay! [quote='881346022, alex_strong, /thread/820155?answerId=881346022#881346022, /profile/alex_strong'] Any idea how to request signed artifacts from Maven? [/quote] No, sorry, I don’t have any experience with Java build systems (just their output :-). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[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

Hi Michael, As requested, I updated the sample app to use ToggleImmersiveSpaceButton instead of a manual open/close button. I rebuilt the app, distributed it via TestFlight, and reproduced the issue on Apple Vision Pro. The issue still occurs consistently. Attachments: Screen recording demonstrating the issue - TestFlight distributed Build. Sysdiagnose captured after reproduction of the issue. Updated sample project. Steps to reproduce: Archive and upload a build to TestFlight. Install the application via TestFlight. Tap Show Immersive Space. Lock the window. Tap Hide Immersive Space. Tap Show Immersive Space. The red cube is missing and even immersive space and window disappears for a brief moment and then appears. Device: Apple Vision Pro visionOS 26.0 Xcode: Version 26.3

[quote='820277021, Great_Om, /thread/820277, /profile/Great_Om'] Since it was not possible using the UserDefaults class [/quote] What’s not possible? Reading a user default from a specific domain, like com.apple.Finder? You are correct that UserDefaults can’t do that, but running the defaults tool is not the best alternative. Rather, use CFPreferences. For example: import Foundation func main() { guard let obj = CFPreferencesCopyAppValue(ShowHardDrivesOnDesktop as NSString, com.apple.Finder as NSString), CFGetTypeID(obj) == CFBooleanGetTypeID(), let showHardDrivesOnDesktop = obj as? Bool else { fatalError() } print(showHardDrivesOnDesktop) } main() WARNING Unless otherwise documented, system preferences like this are an implementation detail. It might be OK to use them in a limited scope — like in a managed environment where you control all the copies of the code — but you should not rely on implementation details in a product that you deploy widely. The code above won’t work if your app is sandboxed. Then ag

I've been working with CoreML extensively across macOS 26.x betas and can confirm this regression affects audio processing models as well, not just diffusion architectures. After investigating with Metal GPU capture, the pattern strongly suggests a stride alignment issue in the MLMultiArray backing store when the compute unit dispatches to GPU/ANE. Here are the workarounds I've found while waiting for an official fix: Force CPU-only execution as a temporary fix: let config = MLModelConfiguration() config.computeUnits = .cpuOnly let model = try MyModel(configuration: config) This avoids the corrupted GPU/ANE path entirely. Performance takes a hit, but results are correct. If you need GPU performance, pin to CPU+GPU and avoid the ANE: config.computeUnits = .cpuAndGPU // excludes Neural Engine In my testing, the corruption is most severe on the ANE path. CPU+GPU gives roughly 70% of the full .all performance without the scrambled outputs. Runtime validation to degrade gracefully across OS versions: func

Dear Support, We would greatly appreciate your assistance with the error received in Apple Pay In-App Provisioning process, as described in FB22280049. Thank you.

Hi, Still in TestFlight: ciphermld Failed to fetch Token Issuer Directory. { URL: https://gateway.icloud.com/pat-issuer-directory?issuer=pir.**.* Status Code: 404, ... pir-tester looks good: ./PirTester query --pir-server-url https://pir.. --privacy-pass-url https://issuer.. --pir-usecase .url.filtering --user-token **** --ohttp-config-url https://ohttp.*****.***/.well-known/ohttp-gateway --ohttp-gateway-url https://ohttp.*****.***/.well-known/ohttp-gateway .com/url-filter-test PIR Server URL: https://pir..** Privacy Pass URL: https://issuer.**. PIR Use Case: *****.app.url.filtering User Token: ***** Fetching OHTTP key configuration from https://ohttp.*****.***l/.well-known/ohttp-gateway... OHTTP enabled, gateway: https://ohttp.*****.***/.well-known/ohttp-gateway Running full PIR lookup (fetching tokens, config, keys, and querying)... Querying keyword: ***.com/url-filter-test ✓ PIR query completed successfully, value=1 Result for '***.com/url-filter-test': 1 ✓ Full PIR lookup completed successfully I wrote C

@AJAS_M_M My app, which was stuck in Apple's review process as mentioned. After that my App rejected multiple times due to the complex login procedure of my app requiring additional further explanation. However, it was finally approved on February 18, 2026. Regarding Apple's comment on January 26th: Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us. I actually followed the link provided there and requested an expedited app review by navigating to contact us > Get help with a new issue > App Review > request an expedited app review. Based on my experience, I believe this is the only thing we can do on our end in such situations. I hope your review process concludes successfully as well.

21 days and counting...Has anyone tried anything other than expediting the process? Any luck calling?