“translate scheme”

I fixed that by enabling Debug mode from Edit Scheme- Options - Enable Debug Mode

First up, I want to be clear that I don’t support third-party tools and libraries. I’m gonna provide general guidance here, but if you need help translating that to your chosen tooling then I recommend that you escalate that via the support channel for that tooling. macOS does let you embed a command-line tool in your app and then spawn it as a child process. However, the exact mechanics of this depend on whether your app is sandboxed or not: Mac App Store apps must be sandboxed. For apps that you distribute directly, using Developer ID signing, sandboxing is optional. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Someone (Andy) showed me a workaround (i guess?) by using the @Environment(.colorScheme) to update the proper color scheme for sheets (see the updated ContentView) BTW I still think this is a SwiftUI issue. Sheets should behave the same way other views are presented. Here is a working version of the sample: import SwiftUI enum AppTheme: Int { case system = 0 case dark = 1 case light = 2 var colorScheme: ColorScheme? { switch self { case .system: return nil case .light: return .light case .dark: return .dark } } } struct SettingsView: View { @AppStorage(theme) var appTheme: AppTheme = .system var body: some View { VStack(spacing: 8) { Button { select(theme: .system) } label: { Text(System) } Button { select(theme: .dark) } label: { Text(Dark) } Button { select(theme: .light) } label: { Text(Light) } } } func select(theme: AppTheme) { appTheme = theme } } struct ContentView: View { @AppStorage(theme) var appTheme: AppTheme = .system @State var isPresented = false @Environment(.colorScheme) var systemCo

BTW there is a missing word in the title. The correct title should be: View presented as sheet are NOT properly updated to correct color scheme

It feels you are talking here about withoutImplicitSecurityStore creation option instead of withoutImplicitStartAccessing resolving option. No, I'm talking about withoutImplicitStartAccessing. We explicitly say it does not apply to security-scoped bookmarks: This option causes an implicit call to startAccessingSecurityScopedResource() on the returned URL when it’s ready to use the resource. This option isn’t applicable to security-scoped bookmarks. In my tests, withoutImplicitStartAccessing does pretty much what it says on the tin. You're testing on iOS, not macOS. As I said earlier: If it's feasible, I'd recommend testing your code as a native macOS app (not the simulator or in compatibility mode). macOS is better at enforcing the right behavior, so code that works there will generally work on iOS. I'll state that more directly— the internal implementation of iOS means that some things work that really shouldn't. The right approach here is to use macOS as the guide. Breaking down a few specifics: Create a bo

First off, as a clarification, withoutImplicitStartAccessing does NOT mean don't call startAccessingSecurityScopedResource for me. It feels you are talking here about withoutImplicitSecurityStore creation option instead of withoutImplicitStartAccessing resolving option.. In my tests withoutImplicitStartAccessing does pretty much what is says on the tin. For example: create a bookmark (without specifying neither withoutImplicitSecurityStore nor withSecurityScope persist it somehow (the above test app writes it to user defaults) restart the app resolve bookmark specifying withoutImplicitStartAccessing access the url - that would fail. call startAccessingSecurityScopedResource on it - it returns true access the url again - that will now work if instead of 4 above you resolve the bookmark without specifying withoutImplicitStartAccessing, then access the url - that would work right away. Behind the scenes, what actually happens when you resolve a bookmark is Thanks a lot for those details, it's really helpful to s

There must be some reason... otherwise we wouldn't have withoutImplicitStartAccessing in the first place ;) First off, as a clarification, withoutImplicitStartAccessing does NOT mean don't call startAccessingSecurityScopedResource for me. To quote the documentation: Bookmarks that you create without security scope automatically carry implicit ephemeral security scope. ... When using this option, other processes can’t call startAccessingSecurityScopedResource on the resolved URL. Behind the scenes, what actually happens when you resolve a bookmark is: You pass the bookmark data to a daemon (ScopedBookmarkAgent). The daemon validates the security scope, resolves the bookmark, then passes the resolved URL back to you. ...and implicit ephemeral security scope is what then allows your app to call startAccessingSecurityScopedResource on the URL it just got. Your app then calls startAccessingSecurityScopedResource to take ownership of the resource. The open/save panel works exactly the same way, except they happen t

Sadly, I can’t read Chinese, so I’m answering based on a machine translation. It sounds like your goal is to create a Mac product to distribute directly, using Developer ID signing. If so, there are three basic steps: Created a Developer ID signed version of your product. Submit that for notarisation. On successful notarisation, staple the resulting ticket to your product [1]. We have documentation that covers all of this. A good place to start is: Creating distribution-signed code for macOS Packaging Mac software for distribution Once you’ve done these steps, I recommend that you test your product using the process described in Testing a Notarised Product. If you continue to have Gatekeeper problems, I have lots of advice on how to investigate that in Resolving Trusted Execution Problems. Finally, see the following forums posts for links to even more info: Notarisation Resources Code Signing Resources Trusted Execution Resources. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @

Welcome to the forum. A first comment: edit your text to make each question clear and post easier to read. And avoid asking so many questions on so different topics. Anyway, I'll try to provide some answers. Q1: How should I best start learning? For example, is Swift Playgrounds the right first step? My personal advice: start with tutorials from Apple like 'Develop in Swift fundamentals'. Or go and visit https://developer.apple.com/pathways/. If you want to learn SwiftUI, select it. Q2: How should I continue afterwards to gain further knowledge, possibly in areas like system architecture, cybersecurity, or cloud computing (even though I don’t want to commit too early to one direction)? You will find resources here again: https://developer.apple.com/pathways/. My advice to continue, after step 1, is to imagine and develop a complete (yet simple) app. That's how you will put what you learned in practice. And then, each time you fall on a problem, ask the forum for help. Q3: Can you recommend a learning schedule