Apple Maps Guides

Yeah, this isn’t super surprising. errOSAInternalTableOverflow isn’t something I have a lot of experience with but it seems like it’s primarily associated with AppleScript’s garbage collector. At least one of the places that raise this error logs relevant info to the system log, so you should have a rummage around in there to see if anything interesting pops out. See Your Friend the System Log for my advice on how to wrangle the system log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='876196022, omeriadon, /thread/812607?answerId=876196022#876196022, /profile/omeriadon'] Are we not allowed to add a package normally and the judging computer download the package? [/quote] In the fine print we specifically state that your playground is expected to work without a network connection. For other hints and tips on this topic, see my reply on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m glad to hear you got this sorted out. I recommend that you read the following, which might explain some of the pathologies you encountered: Creating distribution-signed code for macOS (specifically, the bit about not using sudo) The Care and Feeding of Developer ID Resolving errSecInternalComponent errors during code signing Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The documentation for our low-level APIs is quite scattered, something I going into detail in in Availability of Low-Level APIs. In this specific case a good start is the header itself, which has this key titbits: Note that the validity of the addresses returned correspond to the validity reader You’re passing in NULL, which gives you the in-memory reader, which returns everything directly, and thus doesn’t need to be deallocated. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m glad to hear that you got this sorted. [quote='876168022, kjw1978, /thread/815604?answerId=876168022#876168022, /profile/kjw1978'] Do NOT add the entitlement to app.json. [/quote] Correct. [quote='876168022, kjw1978, /thread/815604?answerId=876168022#876168022, /profile/kjw1978'] Apple now treats MusicKit as a Runtime Service [/quote] The word “now” is misleading, in that it suggests that this changed at some point. That’s not the case. MusicKit has never used entitlements. Indeed, trying to use an entitlement for this is one of the common mistakes I call out in Determining if an entitlement is real. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If you search the ’net for “Unsupported Swift Architecture”, you’ll find a bunch of helpful advice on this front. My additions to that are: If you’re using third-party tooling or libraries, seek help from the support channel for the relevant vendor. TN3117 Resolving architecture build errors on Apple silicon describes best practices for your build architecture settings. Check your settings to make sure you’re following them. If you get stuck, try to isolate the problem into a small test project and then share that here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If you search the ’net for “Unsupported Swift Architecture”, you’ll find a bunch of helpful advice on this front. My additions to that are: If you’re using third-party tooling or libraries, seek help from the support channel for the relevant vendor. TN3117 Resolving architecture build errors on Apple silicon describes best practices for your build architecture settings. Check your settings to make sure you’re following them. If you get stuck, try to isolate the problem into a small test project and then share that here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I can’t comment about specific third-party libraries, so let me answer with some general guidance: As mentioned in the fine print, your playground is expected to work without a network connection. One consequence of that is that, if you rely on a third-party library, you have to vendor [1] that library, that is, copy the code into your own sourcebase. Whenever you use a third-party library, you have to make sure that your use is compatible with its licence. Finally, on a mechanical front, rather than delete the .git directory my advice is that you use git export to export a specific tag or version branch, and then try to avoid modifying the library code [2]. That’ll make it easier for Future You™ to understand how your playground is set up (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] The origina of this term are interesting, and if you search the ’net for “what is vendoring a library” you’ll find a bunch of backstory. [2]

This is with an Xcode playground, right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, that’s annoying. We have a bug to track this internally (r. 170381800). We’re hoping to fix it sooner rather than later but, as always, I can’t offer a concrete timeline. If you want to be notified when the fix starts seeding, file your own bug in Feedback Assistant and ask that it be marked as a duplicate of the above-mentioned bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s discuss this 26.3 regression in the specific thread you created for it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The correct value to put in the entitlement is url-filter-provider. Annoyingly, this hasn’t yet made it to the documentation (r. 164079609) but Xcode’s Signing & Capabilities editor does the right thing. Regarding KayleeSC’s bug about app submission (FB19582905) I continue to monitor that internally, but I’ve nothing concrete about its status other than that it remains un-fixed )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s continue this on the other thread that you found. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Looks like you already found the thread about this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve not seen a lot of reports like this previously. My best guess is that something is borked on the client side. I recommend that you do all the usual browser-y things, like retry in private browsing mode, or with a different web browser, or from a different machine. If that doesn’t help, you can see formal support via Apple > Developer > Contact Us > Development and Technical > Entitlements. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com