dsym file

Do this: Launch Xcode 26.3rc. File > New > Project. At the top, select iOS. In the main list, select App Playground. Complete the workflow from there. Good luck with your submission! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thank you, Albert. I have updated FB21797091 with the following information: App ID: 59S472WZMN.com.kyujinbox.app Team ID: 59S472WZMN App Store URL: https://apps.apple.com/jp/app/id1635254205 Reproduction steps using the published app Since our app is already on the App Store with all the necessary entitlements and AASA configurations in place, I believe this would be the most efficient way for your team to verify the issue without requiring a separate sample project. Could your team first try reproducing the issue using our published app? If a focused sample project is still required after that, please let me know your team's App ID (format: TEAMID.bundleid) and I will: Add it to our AASA file Create and attach a minimal sample project to FB21797091 Thank you for your continued support in resolving this issue.

If I understand correctly your problem, the simulators you can use depend on the minimum deployment you've defined for your app. Select the app in file navigator panel of Xcode select Targets select general Then set the minimum deployment to iOS 18 or lower if you want to use such simulators. Then, in the top bar of Xcode window, select the simulator as usual.

I've put a config.json file into ~/Library/Developer/Xcode/CodingAssistant/ClaudeAgentConfig awsAuthRefresh: aws sso login --profile ai, env: { AWS_PROFILE: ai, AWS_REGION:ap-southeast-2 CLAUDE_CODE_USE_BEDROCK:1, ANTHROPIC_MODEL:au.anthropic.claude-sonnet-4-5-20250929-v1:0, ANTHROPIC_SMALL_FAST_MODEL:au.anthropic.claude-haiku-4-5-20251001-v1:0, CLAUDE_CODE_MAX_OUTPUT_TOKENS:4096, MAX_THINKING_TOKENS:1024 } } These are the env vars I use for Claude Code. I'm not sure how that relates to Claude Agent within Xcode or whether it is even possible to use Bedrock from within Xcode.

Quinn, Thank you so much for taking the time to reply to my query. Your detailed response did the trick! I doubt that anyone else on earth will be interested in how this works re. FM runtimes in particular, but perhaps the code might be of interest to someone wrestling with app plugin notarization elsewhere; therefore, I have attached my (can’t believe I’m saying this) working .sh files. Thanks again. Regards, Lar build_all.sh.txt notarize_dmg.sh.txt build_dmg.sh.txt repair_and_sign.sh.txt build_config.sh.txt

Thank you for your insight - that's a good piece of the puzzle! I found the DarkWake session: WWDC 2012, Session 711, Power Management with Ethan Bold and Soren Spies. Sadly, I can't blame DarkWake because it has been around since 2012, but I only see this unexpected wake on newer macOS. Since I'm using StartCalendarInterval on different versions, here's what I see: macOS 12 and earlier behave as expected; sleep through the CalendarInterval macOS 15 & 26 dark wake at the CalendarInterval Perhaps Apple changed launchd to be capable of scheduling a dark wake. My guess is there is a Launch[Agent|Daemon] *.plist key that can be used to change this behavior. I'll fire up BBEdit and go spelunking through /System/Library/LaunchDaemons/ to see if I can find a relevant key. Of course, if this was documented, I wouldn't be left wondering if I should file a bug report!

@naftaly I submitted a somewhat relevant feedback a few years ago. FB9616844 - MetricKit: MXDiagnostic, MXDiagnosticPayload and MXMetricPayload should have 'identifier' properties I mostly wanted a unique identifier built-in because IPS files have them and then I wouldn't need to decorate the MetricKit payloads myself and it would be just built in. If you want to correlate runtime data you captured against a payload, your best bet is to do this with diagnostics since those are truly the PID at time of diagnostic--well at least I assume. I've never bothered to check. This could easily be tested by crashing and check the PID in the IPS crash file against that identified in the MXDiagnosticPayload metadata. The metadata is required in the diagnostic payload but it isn't in the metrics payload. While I have not in practice seen the metrics metadata object to be empty in a metric payload, you're right that you can't do much for variation over time. The API just simply doesn't have a way to repres

Hi Michael, Thank you for the previous suggestion about using AnchorEntity(.head) with trackingMode = .once for positioning entities relative to the user's gaze — that approach worked great for our immersive menu positioning. Now I'm running into a different issue with 360° video playback. When rendering an equirectangular video on a sphere using VideoMaterial and MeshResource.generateSphere(), there is a visible black seam line running vertically on the sphere. This appears to be at the UV seam where the texture coordinates wrap from 1.0 back to 0.0. The same video file plays without any visible seam in other 360° video players on Vision Pro, so the issue is not with the video content itself. Here is the relevant code: private func createVideoSphere(content: RealityViewContent, player: AVPlayer) { let sphere = MeshResource.generateSphere(radius: 1000) let material = VideoMaterial(avPlayer: player) let entity = ModelEntity(mesh: sphere, materials: [material]) entity.scale *= .init(x: -1, y: 1, z: 1)

Spotlight exposes files in Suggestions and Recents (Cmd+3) I meant (Cmd+2)

@sergey_nikitin we noticed a huge issue: the events started to fire (reach the threshold) in the DeviceActivityMonitorExtension prematurely, almost immediately after scheduling. This is a known issue in iOS 26, which is actively investigated. I encourage you to file a Feedback report of your own using Feedback Assistant, then post the Feedback ID here. By filing a bug report, you’ll be able to track the issue, update Apple Engineering with additional information, learn if the issue is already known, and get notified of problem resolution.