dsym file

Are there any plans to introduce its system registers to HVF’s EL2 support? We can't talk about The Future™ [1], but if you'd like to see this change I encourage you to file an enhancement request describing your requirements. 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 [1] See tip 3 in Quinn's Top Ten DevForums Tips.

Thanks for filing FB9972410. I took a quick look at its with the right folks. Beyond that, I’ve no info to share as to if or when something like might land. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi, Sorry to hear you are occasionally having problems with foundation models and previews working. The best next step will be to file a feedback with diagnostics the next time you hit this so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diagnostics button in that banner; or (b) if you're not seeing an error but you still want to provide diagnostics you can get the same diagnostics window by going under the Editor menu in the menu bar, then selecting the Canvas submenu, then selectin

[quote='875443022, Midnite630, /thread/814338?answerId=875443022#875443022, /profile/Midnite630'] Apps tested and showing this issue are Safari, Chrome, Mail to start. [/quote] Ah, OK, I thought that this might be an issue specific to an app that you’re developing. The Apple Developer Forums are primarily focused on helping developers with the APIs in Apple’s various platform SDKs. With an issue like this, where you’re having problems with system behaviour that affects all apps, your best path forward is to file a bug in Feedback Assistant. And it seems that you’ve done that already (FB21483619), which is great. Thank you! [quote='875443022, Midnite630, /thread/814338?answerId=875443022#875443022, /profile/Midnite630'] After doing some testing, I determined the possible issue. [/quote] Interesting. When you find new factoids like this, please make sure to update your bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I can confirm there is something crashing my Apps that only have Launchscreen storyboards. I use Autoresizing and not Autolayout. And guys please, make a real effort to build a Launchscreen component in SwiftUI. It makes no sense in 2026, always ten years after and we still have a storyboard file messing/crashing our Apps in Swift.

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!