Search results for

Apple Maps Guides

154,091 results found

Post

Replies

Boosts

Views

Activity

Reply to Reproducible EXC_BAD_ACCESS in NEDNSProxyProvider when using async/await variants of NEAppProxyUDPFlow
[quote='815033021, AndriiSulimenko, /thread/815033, /profile/AndriiSulimenko'] Minimum Working Example [/quote] Hmmm, that’s a minimum failing example, right? That is, you wrote this code specifically to reproduce the crash, right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
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
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
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
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
Core Image for depth maps & segmentation masks: numeric fidelity issues when rendering CIImage to CVPixelBuffer (looking for Architecture suggestions)
Hello All, I’m working on a computer-vision–heavy iOS application that uses the camera, LiDAR depth maps, and semantic segmentation to reason about the environment (object identification, localization and measurement - not just visualization). Current architecture I initially built the image pipeline around CIImage as a unifying abstraction. It seemed like a good idea because: CIImage integrates cleanly with Vision, ARKit, AVFoundation, Metal, Core Graphics, etc. It provides a rich set of out-of-the-box transforms and filters. It is immutable and thread-safe, which significantly simplified concurrency in a multi-queue pipeline. The LiDAR depth maps, semantic segmentation masks, etc. were treated as CIImages, with conversion to CVPixelBuffer or MTLTexture only at the edges when required. Problem I’ve run into cases where Core Image transformations do not preserve numeric fidelity for non-visual data. Example: Rendering a CIImage-backed segmentation mask into a larger CVPixelBuffer can cause l
1
0
213
2w