Search results for

Apple Maps Guides

154,081 results found

Post

Replies

Boosts

Views

Activity

Reply to launchd StartCalendarInterval behavior changed
There are a bunch more factors in play here, including: For Macs with a battery, whether it’s connected to mains power or not. Various preferences in System Settings > Battery, and specifically those under Options. Lots of wacky options under pmset (see the pmset man page for more). But these are all implementation details. From an API perspective, launchd doesn’t guarantee anything about the power state of the system when it starts your job based on StartCalendarInterval. Usually daemons aren’t expected to interact with the user, and thus it doesn’t really matter what the UI state of the system is when the system starts your job. To offer more specific guidance here, I’d need to know more about what your job does. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: App & System Services SubTopic: Core OS Tags:
2w
Reply to Multicast Entitlement now not working
What Albert said plus… Some managed capabilities are granted to a specific App ID, while others are granted to your team as a whole. My experience is that the Multicast Networking capability is always granted to your team, so you can use it in any app from that team. And, presuming that you’re working in Team ID H________3, our records show no sign of it deviating from this standard practice. [quote='814969021, idrachman, /thread/814969, /profile/idrachman'] now multicast entitlement is no longer provisioned. [/quote] What do you mean by that? Is Xcode failing to build your app? Or are is your app failing to send or receive multicasts? If it’s the later, be aware that the vast majority of such problems are not tied to the Multicast Networking capability, but rather are caused by code-level problems. I have a bunch of advice about that in Extra-ordinary Networking > Broadcasts and Multicasts, Hints and Tips. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = e
2w
Reply to Notarized but Gatekeeper fails macOS 15 only?
[quote='814949021, ghutchis, /thread/814949, /profile/ghutchis'] How can notarization work for macOS 14 and 26, but not for macOS 15? [/quote] That’s not what’s happening here. Notarisation has worked, but your app is failing to pass Gatekeeper. This is actually pretty common. Notarisation and Gatekeeper are separate subsystems, and notarisation is necessary but not suffiient to pass Gatekeeper. It’s less common for this to vary by macOS version, but I’ve certainly see that before. You can find my general advice on this topic in Testing a Notarised Product. Specifically, by setting up a macOS 15 VM you can test this for yourself, which has a couple of benefits: It shortens your debugging cycle for this specific issue. It’ll help you avoid problems like this in the future. Finally, when it comes to debugging this issue I have a bunch of advice in Resolving Trusted Execution Problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
2w
Notarized but Gatekeeper fails macOS 15 only?
Okay, I just pushed a release and notarized. Works great on my test laptop (macOS 26.2) and my test desktop (macOS 14.x) But it seems to fail for a friend who's running macOS 15. I've been using the same GitHub actions successfully for months. How can notarization work for macOS 14 and 26, but not for macOS 15? I think everything looks okay as far as the signing? I've checked codesign -dvv Executable=/Applications/Avogadro2.app/Contents/MacOS/Avogadro2 Identifier=cc.avogadro Format=app bundle with Mach-O thin (arm64) CodeDirectory v=20500 size=11607 flags=0x10000(runtime) hashes=352+7 location=embedded Signature size=8986 Authority=Developer ID Application: Geoffrey Hutchison (…..) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=Feb 5, 2026 at 8:47:21 PM Info.plist entries=24 TeamIdentifier=….. Runtime Version=15.5.0 Sealed Resources version=2 rules=13 files=3306 Internal requirements count=1 size=172 And from spctl -a -vv /Applications/Avogadro2.app: accepted source=
1
0
356
2w
Reply to notarization stuck in progress > 24hrs
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
Reply to Notarization stuck "In Progress" for 48+ hours - 6 submissions (Team ID: Y7T24GD249)
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
All notarization submissions stuck "In Progress" — first-time notarization, 9 submissions over 16+ hours
I'm submitting my first macOS app (a native SwiftUI menu bar app, signed with Developer ID Application certificate, Hardened Runtime enabled) for notarization using xcrun notarytool submit with keychain profile authentication. All 9 of my submissions have been stuck at In Progress for up to 16 hours. None have transitioned to Accepted or Invalid. Logs are unavailable for all of them (notarytool log returns Submission log is not yet available). Environment macOS: 26.2 (25C56) Xcode: 26.1.1 (17B100) notarytool: 1.1.0 (39) App: Native SwiftUI, universal binary (x86_64 + arm64), ~2.2 MB DMG Bundle ID: com.gro.ask Team ID: 4KT56S2BX6 What I've verified Code signing is valid: $ codesign --verify --deep --strict GroAsk.app passes with no errors $ codesign -dvvv GroAsk.app Authority=Developer ID Application: Jack Wu (4KT56S2BX6) Authority=Developer ID Certification Authority Authority=Apple Root CA CodeDirectory flags=0x10000(runtime) # Hardened Runtime enabled Runtime Version=26.1.0 Format=app bundle with M
2
0
154
2w
Reply to All notarization submissions stuck "In Progress" — first-time notarization, 9 submissions over 16+ hours
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. [quote='814937021, JimWu01, /thread/814937, /profile/JimWu01'] 1- … but 16+ hours with zero feedback seems excessive. [/quote] My experience, based on reports I’ve seen here in the forums, is that when you hit the in-depth analysis path it can take a day or two to clear. I generally don’t bother investigating issues like this until a week has passed. [quote='814937021, JimWu01, /thread/814937, /profile/JimWu01'] 2- Is there any manual configuration Apple needs to do on their end to unblock my team for notarization? [/quote] No, that’s a different issue. [quote='814937021, JimWu01, /thr
Topic: Code Signing SubTopic: Notarization Tags:
2w
Reply to SWİFT STUDENT CHALLANGE iOS vers
[quote='815061021, alyme, /thread/815061, /profile/alyme'] iOS 19/iPadOS 19 [/quote] There is no iOS 19 O-: You can assume that your playground will be run on a released version of iPadOS 26 / macOS 26 [1]. AFAICT the fine print doesn’t specify what type of device will be used for testing, other than to confirm that on-device intelligence will be available [2]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] See my response here to the equivalent question from last year. [2] See this thread.
2w
Reply to Swift package in Xcode 26.3 rc
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
2w
Reply to Some question about Swift Student Challenge 26
Regarding your first question, I see that you found an older thread about this and my advice is that folks focus the discussion there. Regarding your second, this is a common question and I don’t have any answers for you )-: If that changes, I’ll post on update in this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
Some question about Swift Student Challenge 26
My playground may require that the device has downloaded some resources in advance, such as Apple's advanced voice, translation language... But this is not necessary. It is just an incidental function. If it is not downloaded, the app will prompt that this function is not available and most of the other functions can continue to be used. But I want to know whether the judge's device will download these things in advance, and if not, will the judges think that there is a problem with my app that can't be used normally, which will cause my work to be rejected directly? Because my app uses the API of iOS 26, it needs to run in Xcode, and the competition allows the Apple intelligent function, but it is stipulated that if it runs with Xcode, the app will be tested on the simulator. However, my app involves image playground and cannot run on the simulator. Does anyone have a good solution? Thank you!
1
0
221
2w
Can I submit the app I submitted to the app store to SSC at the same time?
Hi, I recently built an app and I’m planning to publish it on the App Store. Since the Swift Student Challenge (SSC) is coming up, I’m also considering submitting the same project by converting it into a Swift Playground (with some content trimmed to meet the rules). I believe both I and the project are eligible. My question: if I publish the app on the App Store first and then submit it to SSC, could that violate the rules or lead to rejection? I also have a concern: because I’m a minor, Apple requires the App Store developer name to be my mother’s. However, the app was entirely developed by me. my mother and anyone else did not participate(My mother can't even use a computer.). I’m worried this might create confusion and make judges think I copied someone else’s work, which I did not. Would you recommend publishing on the App Store now, waiting until after SSC, or taking a different approach? Thank you.
1
0
401
2w
Reply to Can I submit the app I submitted to the app store to SSC at the same time?
[quote='815002021, lijiaxu, /thread/815002, /profile/lijiaxu'] could that violate the rules or lead to rejection? [/quote] I’m not aware of any specific prohibition against this, but my advice for questions like this is always the same: Read the fine print! Specifically, these two pages: Developer > Swift Student Challenge > Eligibility and requirements Developer > Swift Student Challenge > Terms and Conditions Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w