“eskimo”

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 backs

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

I have one small correction here: [quote='875229022, DTS Engineer, /thread/809211?answerId=875229022#875229022'] The kernel can’t access the user context directly, so it has to ‘up call’ to a helper process running in the user context. [/quote] There are more layers to this onion that I originally thought, and a colleague informed me that it’s not the kernel doing the up call here but rather a daemon. This doesn’t really change my overall outline of the issue, but I wanted to post a correction because if you dig around in the system log you’ll notice this daemon in play. [quote='875908022, VictorPetitjean, /thread/809211?answerId=875908022#875908022, /profile/VictorPetitjean'] would you have an advice on how to make this issue happen less often? [/quote] Sadly no. [quote='875908022, VictorPetitjean, /thread/809211?answerId=875908022#875908022, /profile/VictorPetitjean'] By not opening the app too soon after startup [/quote] I experimented with this during my efforts to understand the reproducibility of the is

[quote='875945022, Gcenx, /thread/814383?answerId=875945022#875945022, /profile/Gcenx'] That would be FB15880492 [/quote] [quote='875994022, Gcenx, /thread/814383?answerId=875994022#875994022, /profile/Gcenx'] I was just informed that FB21763885 [/quote] Perfect. Thanks! I took a quick look as these and they definitely landed in the right place. Beyond that, there’s no much more info that I can share [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] As I explain in Quinn’s Top Ten DevForums Tips, Apple folks can’t talk about The Future™.

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. I’m not in a position to discuss the specifics of other folks apps. If you’re talking with that developer, I recommend that you ask them for details as to what this “Apple approval/permission” entailed. However, to the best of my knowledge there is no technical mechanism to bypass the content filter restrictions discussed in TN3134. Two things: It’s possible that they’re talking about the Screen Time case. The Family Controls capability is managed for distribution, that is, developers must be granted permission by Apple to distribute an app using Family Controls, and that could be constructed as “Apple approval/permission”. It’s also possible that they’re not using a content filter. I’ve seen folks implement content filtering using a packet tunnel provider. I consider this to be managerial abuse [1], and it’s not something that DTS supports. See TN3120 Expected use cases for Network Ext

[quote='815475021, krzsiwek, /thread/815475, /profile/krzsiwek'] Is this behavior known and expected? [/quote] Probably [1]. But it’s useful to have a specific benchmark to highlight this cost. I recommend that you file a bug describing the issue, how you’re testing the performance, and what results you got. Please post your bug number, just for the record. [quote='815475021, krzsiwek, /thread/815475, /profile/krzsiwek'] Is there anything we can do to mitigate [this] in our application? [/quote] Not that I can think of. There isn’t really much wiggle room here. Either the property is on or off and, assuming a specific flows hits your packet tunnel provider in both cases, it sees the same set of packets for that flow. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Historically the networking stack didn’t have fancy features like enforceRoutes, and there’s been decades of optimisation for that simple case.

Does this general a crash report? If so, please post an example here. See Posting a Crash Report for advice on how to do that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

See my response on the other thread you raised this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com