“eskimo”

My understanding is that you can withdraw your submission using the status page mentioned here. Once you do that, you’ll be able to re-submit. And you can repeat that process as many times as you want until the deadline. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Oh, hey, look at that! I had assumed that, if you set the app icon via the General tab of the playground editor, it would do the right thing. However, as soon as I switch it from Placeholder to Custom it adds the asset catalogue and I get that warning. That’s… suboptimal. Given that, I don’t think there’s much you can do about this. You have the choice of that warning or giving up on your pretty icon, and that’s no choice. I had a bit of a rummage and I couldn’t find any existing bug report about this warning. Given that, I encourage you to file your own. Please post your bug number, just for the record. And you can then also include the bug number in the comments when you submit. [quote='877417022, islandrose, /thread/816816?answerId=877417022#877417022, /profile/islandrose'] but it looks like each attempt actually posted afterward. [/quote] Yeah, that’s a known issue with the forums platform (r. 165521402)-: [quote='877417022, islandrose, /thread/816816?answerId=877417022#877417022, /profile/islandrose'] I’

[quote='877433022, mlgiPhone7plus, /thread/812911?answerId=877433022#877433022, /profile/mlgiPhone7plus'] Could it be okay to leave a note in the Other comments section of the form for the judges to run apps on a live iPhone or iPad? [/quote] Leaving a note is OK, obviously, but I can’t promise that it’ll have any effect. There are two ways to submit your app. One of them guarantees that your submission will be run on device, but it has a significant limitation. I just posted a summary of the current state of affairs here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

vasultm, It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. As to the main issue, I haven’t yet driven it to a conclusion but, for the moment, my historical advice stands: There’s no supported way to transfer app group IDs between teams. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I can’t really help you with MDM stuff. If you need help in that space, you can try over in Business & Education > Device Management but you might have more luck over in the Apple Support Community, run by Apple Support, and specifically in the Business and Education topic areas. However, I can help you with this: [quote='877476022, Leo_Nagano, /thread/815340?answerId=877476022#877476022, /profile/Leo_Nagano'] on that MDM‑managed macOS 14.4 (Apple Silicon) device the app still cannot be launched. [/quote] That sounds less like an MDM issue and more like a Gatekeeper issue. [quote='877476022, Leo_Nagano, /thread/815340?answerId=877476022#877476022, /profile/Leo_Nagano'] codesign -dvv confirms the app is signed with our Developer ID Application certificate and has … [/quote] I see no mention of the App ID (com.apple.application-identifier) and Team ID (com.apple.developer.team-identifier) entitlements. Any app that uses restricted entitlement should be signed with those entitlements because they tie the

You wrote: [quote='877374022, pnelson, /thread/808121?answerId=877374022#877374022, /profile/pnelson'] When using notifyEncryptionRequired running as an app causes the central to receive the Encryption is insufficient. [/quote] and: [quote='877374022, pnelson, /thread/808121?answerId=877374022#877374022, /profile/pnelson'] This also happens when run as a launch agent. [/quote] So, it being a launchd agent isn’t a factor. That suggest that this is a Bluetooth issue rather than something related to your execution context. I’m gonna invite my Bluetooth colleague [1] to wade in here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, Bluetooth expert colleague. AFAIK he doesn’t actually a Bluetooth transceiver in his head (-:

[quote='817008021, liyuwei, /thread/817008, /profile/liyuwei'] Hopefully, it can be fixed in the official release. [/quote] Rather than hope it’s better to actually file a bug about the issue. I followed the link you posted and I don’t see a bug number there, so it’s not clear whether anyone has done that yet. If this is your product, I encourage you to file a bug about the issue yourself. See Bug Reporting: How and Why? for lots of detailed advice on how to do that. If you’re just someone using this product, I recommend that you ask the developer if they’ve filed a bug. Either way, please post the bug number here, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='816956021, mbisque, /thread/816956, /profile/mbisque'] Every recent attempt to create a Installer certificate has failed [/quote] Clearly it hasn’t failed completely, in that you’ve hit the limit so you must’ve actually created the certificates. So, it’s not a failure to create the certificates, but rather that something has gone wrong after you’ve created them. It’s hard to say what that is without more info. In general, Developer ID signing identities are precious and you have to manage them carefully. I have a lot to say about this in The Care and Feeding of Developer ID. As explained in that post, the best way to resolve this is to recover the private key associated with your existing certificates and thus recover your ability to sign your installer. The post has a lot of suggestions for how you might do this. Once you’re able to form a signing identity by pairing up the private key and its certificate, if you’re still having problems signing then post back here with the details and I should be ab

[quote='816939021, TarMac_, /thread/816939, /profile/TarMac_'] I would like to ask if it's possible to set this webcredentials in a different way in the app? [/quote] No. The associated domain feature is based on entitlements which are in turn authorised by a provisioning profile. These are baked into your app when you build it. There’s no way to provide equivalent information at runtime. [quote='816939021, TarMac_, /thread/816939, /profile/TarMac_'] The reason for this is that we are developing a native app and our on-premise customers have their own web servers. [/quote] Keep in mind that the AASA file must be placed on a public webserver so that it can be accessed by the Apple CDN. That limits your option when it comes to associated domain choices. If your app is commonly deployed to managed environments, you might consider other authentication options. I’m a huge fan of the recently released ManagedApp framework. For a quick intro, watch WWDC 2025 Session 203 Get to know the ManagedApp Framework. But ther

The term personal account is confusing, so let me start by clarify that. The developer programme has three tiers [1]: Any Apple Account can be used for basic development. Xcode shows this as a Personal Team. This comes with significant limitations. For the details, see Developer > Support > Choosing a Membership. You can pay to join the developer programme, which makes for an Individual team. A company can pay to join the developer programme, which makes for an Organization team. You can learn more about these in Developer > Program and related pages. If you join the Individual programme you can upgrade your team to an Organization team later on. See Developer Account Helper > Membership > Updating your account information > Updating an individual membership to an organization membership. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There’s also the enterprise programme, but that’s not relevant to t

[quote='816877021, Pushpak-Ambadkar123, /thread/816877, /profile/Pushpak-Ambadkar123'] inquire about the process for obtaining approval for the following entitlement in my iOS/macOS app [/quote] There is no approval process for this. Most NE entitlements, including the one for content filters, are available to all (paid) developers. Note Historically there was an approval process for this but that’s not been the case for almost 10 years now. See Network Extension Framework Entitlements. There are, however, significant deployment restrictions for content filters on iOS. I cover those in TN3134, which I mentioned in my reply on your previous thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I just wanted to stop by and drop some links: There’s a previous DevForums thread about this issue. And Cyrille created Swift Forums thread as well. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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

[quote='816946021, hellnola5, /thread/816946, /profile/hellnola5'] when iOS or iPad OS connected to a Wi-Fi with captive portal [/quote] Is this a captive network that you control? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Right. The submission form has two options: Swift Playground 4.6 or later Xcode 26 or later (with a note saying “Xcode app playgrounds are run in Simulator.”) In the first case, your submission must necessarily be run on an iPad. In the second, your submission will be run on the simulator, not a real device. There are some caveats here: In the first case, the Swift Playground app doesn’t yet include support for the iOS 26 SDK )-: See this thread. In the second case, the form doesn’t currently say whether it’ll be an iPhone on iPad simulator. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com