Account Locked

It is July 2025, we are getting the same 401 forbidden when calling registerMerchant API using the top level Account Holder account. We are blocked in building out labs and prepping production environment until resolved.

OK, here’s what I did today: I created a new VM with a macOS 15.5 guest, and then installed Xcode 16.4. I ran through the OS and Xcode setup processes, doing minimum configuration at each step. I chose English as the language because I very much doubt that this issue is related to your chosen language. In Xcode, I created a new project from Xcode’s macOS > App template. In Signing & Capabilities, I confirmed that Sign to Run Locally was selected [1]. I chose Product > Archive. I looked at the contents of the resulting archive: % cd /Users/quinn/Library/Developer/Xcode/Archives/2025-07-21 % ls -al Test788895 21-07-2025, 05.11.xcarchive/Products/Applications/Test788895.app/Contents/_CodeSignature total 8 drwxr-xr-x 3 quinn staff 96 21 Jul 05:11 . drwxr-xr-x 7 quinn staff 224 21 Jul 05:11 .. -rw-r--r-- 1 quinn staff 2200 21 Jul 05:11 CodeResources As you can see, the permissions are set correctly. You should be able to run this test locally, and I suspect that you’ll see the same results as I do. If yo

We didnt have 2 sessions of our plug-in/Photoshop being invoked. The admin user was just physically logged in for other purposes. So, only 1 instance was running of Photoshop/our plug-in/background process always under the Standard user account. To answer your questions the following is the code we use for finding/launching is below - [[NSWorkspace sharedWorkspace] openApplicationAtURL:app_path configuration: configuration completionHandler:^(NSRunningApplication* app, NSError* error) if (error) { NSArray *directory_path_arr = NSSearchPathForDirectoriesInDomains(NSApplicationSupportDirectory, NSLocalDomainMask, YES); NSString *filePath = nil; if(directory_path_arr) { NSString *directory_path = [directory_path_arr objectAtIndex:0]; NSString *filePath = [directory_path stringByAppendingPathComponent: [NSString stringWithUTF8String:(const char *)gAppSupportFolderName]]; if(filePath) [[NSWorkspace sharedWorkspace] launchApplication:filePath]; } NSLog(@Failed to run the app: %@, error.localizedDescription

(reposted from thread #759802 to match your repost of the question) You can disable the cpu hog that is CursorUIViewService with sudo defaults write /Library/Preferences/FeatureFlags/Domain/UIKit.plist redesigned_text_cursor -dict-add Enabled -bool NO and restart. This service is the world's most over engineered capslock indicator, and if you toggle caps lock a lot, it loses its mind. Unfortunately for me, I rest my left pinky finger on the caps lock key and toggle it nervously when I'm thinking. Do NOT kill the running process, doing so can freeze the UI forcing a power-cycle.

disable the cpu hog that is CursorUIViewService with sudo defaults write /Library/Preferences/FeatureFlags/Domain/UIKit.plist redesigned_text_cursor -dict-add Enabled -bool NO and restart. This service is the world's most over engineered capslock indicator, and if you toggle caps lock a lot, it loses its mind. Unfortunately for me, I rest my left pinky finger on the caps lock key and toggle it nervously when I'm thinking. Do NOT kill the running process, doing so can freeze the UI forcing a power-cycle.

This happened to me twice. I solved it by holding down the keys that you normally hold down to get the “slide to power off“, and nothing happened… However I held it down for like 30 seconds anyway. Then I went to the kitchen to do some cooking when I came back the iPad had restarted it just took a long time. After that I Long-pressed the Amazon Prime app and made it locked, so that it requires the passcode, this was to prevent me from ever launching it again. Also I did report this bug.

Let me know if: • The red sphere is visible • Movement now feels trackable • You want right-stick support for turning (rotation) • Or we need to tweak scale/speed/clipping/etc You’re close — this should lock it in. ME: Yes, I see the red sphere, and It moves forward, backwards, left and right. Still no actual camera movement though. AI: Excellent — that means everything except the viewpoint shifting is working. The red sphere is tied to the camera, and it’s moving… so your entity is moving — but your headset camera (what the user sees) is staying fixed. Here’s why: ❗ RealityView doesn’t use your custom camera for rendering RealityView always renders from the user’s head position (i.e., the Vision Pro headset) unless explicitly told to use another camera — and currently, Apple doesn’t expose a public API to set the “view camera” in a RealityView. ME: (To myself - are you KIDDING me, that we can't move a camera in a 3d scene, but the solution is to move the 3d scene around the camera? ARE YOU KIDDING M

(continued from above, as I hit the 7000 text limit) I kindly (HA) remind the AI that the code continues to crap out a the content.camera = camera line, with the error Cannot assign value of type PerspectiveCamera' to type 'RealityViewCamera' and to confirm, with 100 percent certainty, that this is even doable. The response: Thank you for your patience — you’re absolutely right to demand clarity here. Let’s clear up the confusion once and for all. ⸻ ✅ The Short Answer: Yes, it is 100% doable to move the camera in an immersive RealityView using gamepad input — and you’re already doing it correctly with your most recent working code (which uses a PerspectiveCamera parented under a named entity like CameraRoot and moves that entity based on gamepad stick input). ⸻ ❌ The Misleading Part: content.camera = camera // ❌ ERROR: Cannot assign value of type 'PerspectiveCamera' to type 'RealityViewCamera' This line is not supported with PerspectiveCamera. It only works with a specific wrapper type used for dynamic camera

So the System was not popping up Do you want to provide access to the Desktop etc folder etc. in this condition to the Standard User. Where did the Message/Window to confirm access to the folder vanish to? There are more questions on this below, but I suspect what's going on here is you have two plugin instances (because Photoshop is running as a separate process in the two different login sessions) which are both talking to the same background process. I don't know how you ended up in that state, but it's impossible for the same process to work in different login sessions. The moment the Admin User was physically logged off the Mac, everything started working for the Standard User even under Screen Sharing. This makes us wonder if this is an edge case macOS bug? No, I don't think this is a macOS bug. Questions I need answered here are these: How are you doing this? Is the background app a launch agent or something else? Also, what exactly is your background app? Is it a true (presumably faceless) app that ru