“eskimo”

[quote='887174022, Tomato, /thread/825798?answerId=887174022#887174022, /profile/Tomato'] I would file a DTS request if I were you. [/quote] Yeah, that might be necessary, but first let’s see if we can do this in public. @skygate-technologies, Are you able to share an example installer package publicly? For example, by posting a link to a site where I can download it? If so, reply here with that link. If not, reply here anyway and I’ll explain the alternative path. Note When you go to post the link, do that in the clear. See tip 14 in Quinn’s Top Ten DevForums Tips. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So, the behaviour you’re seeing is expected. This capability is restricted to specific distribution models. To confirm that, follow the instructions in Finding a Capability’s Distribution Restrictions. As to what you should do about that, it kinda depends on how your product is deployed. You wrote: [quote='825833021, apisdk, /thread/825833, /profile/apisdk'] We are implementing an exam mode feature for an educational app used in schools [/quote] In-House (Enterprise) distribution is intended to be used for apps deployed within your enterprise. Presumably these schools are separate organisations, which means you must use some other distribution mechanism to distribute your app to them. What is that mechanism? The App Store? If so, the standard path forward here is to use your Organization team for both development and distribution. I see a lot of folks use In-House (Enterprise) for internal testing, and that’s not something I recommend [1]. Rather: Use Apple Development code signing for day-to-day debugging. U

Yeah, this is a pain. SecCode acts a bit like a subclass of SecStaticCodeRef, so in most cases you can pass the first when the system expects the second. This is fine in C-based languages but Swift’s strong type checking is much less happy. In most cases the solution is to call SecCodeCopyStaticCode to convert the first to the second. Note I’ve always treated this as Security framework lore but, on looking at it again today, I discovered that it’s actually documented pretty well. However, this falls apart for SecCodeCopySigningInformation where in some cases you must pass in the original SecCode object. And yeah, my workaround for that is an unsafeBitCast(…). Alternatively, if this particular part of your product has easy access to C-based code, you can write a wrapper in C. Finally, I’d appreciate you filing a bug about this. Forcing folks to use unsafeBitCast(…) is… well… suboptimal, and so it’d be nice if we could add an overlay to get around that. If you reply here with your bug number, I’ll add my own (i

For those following along at home, aishahhamman got a response on their specific thread. (Not the response they were hoping for, I’m sure, but an accurate response nevertheless.) Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Jpeasley, FYI, I fixed your thread’s title, changing it from “pp Store Connect …” to “App Store Connect …”. Normally I try to avoid fixing typos like this, but it was very triggering (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I think the droid you’re looking for is Express interest in Auth 2.0 for iCloud Mail, Calendar, and Contacts. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='886880022, JohannesD, /thread/825142?answerId=886880022#886880022, /profile/JohannesD'] This would be exactly what I need, right? [/quote] Not really. Note the user-selected component. The entitlement let’s you write non-quarantined executables to a path that the user selects using the save dialog. You could probably make that work for your use case, but it’s hardly ideal. Keep in mind that this entitlement is unrestricted [1], meaning that you can play with it without any special approval from Apple. So, if you’d like to explore this option you can do so via a quick prototype. [quote='886880022, JohannesD, /thread/825142?answerId=886880022#886880022, /profile/JohannesD'] What is a way to find out? [/quote] Not really. I don’t work for App Review, so I can’t give you definitive answers about their policy. My general advice: Consult their published guidelines. If that’s not sufficient, reach out to them directly. There have multiple paths for this, and I’m a big fan of the Appointment option. However,

[quote='886991022, DTS Engineer, /thread/825531?answerId=886991022#886991022'] the commandLine property in the VZBootLoader. [/quote] D’oh, I meant VZLinuxBootLoader. Sorry about the confusion. My experience with other Unix-y systems is that, once the kernel is loaded, it looks at its boot arguments to determine which file system to boot from. VZLinuxBootLoader lets you control both of those options. Hence my earlier suggestion. However, if you’ve tried this out and can’t make it work then I recommend that you file an enhancement request for the features you want. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So, if I were doing this I’d model the timer as an async sequence, which emits events each time the timer ‘fires’. And, in fact, the AsyncAlgorithms package already has this. Here’s a trivial example of how to use it: import AsyncAlgorithms func main() async { for await e in AsyncTimerSequence(interval: .seconds(1), clock: .continuous) { print(e) } } await main() Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So, yeah, the compiler is right to complain about this. That completion handler is intended to be called from the main thread. By passing it to a newly created task you allow it to be called from other contexts, which is Not Good™. There isn’t one true way of resolving this issue. The best option is gonna vary based on how you’ve set up your code. For example, the following is a very expedient option that kinda matches your existing design: @main final class AppDelegate: UIResponder, UIApplicationDelegate { … func application(_ application: UIApplication, handleEventsForBackgroundURLSession identifier: String, completionHandler: @escaping () -> Void) { let runCompletionHandler = { @MainActor in completionHandler() } Task { await GeoreferenceQueue.shared.addCompletionHandler(runCompletionHandler) } } } actor GeoreferenceQueue { static let shared = GeoreferenceQueue() func addCompletionHandler(_ h: (() async -> Void)) { … } } It works by wrapping the completion handler sync function in an async function t

Sorry about not replying earlier. I’m not sure how I missed this the first time around. Unfortunately I don’t have any immediate answers for you. I’m gonna do some digging and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='825685021, rbmanian75, /thread/825685, /profile/rbmanian75'] For mac os guests it is working. For linux guests it is not working [/quote] We kinda expect that macOS and Linux would behave the same in this regard, so I’m gonna recommend that you start out by filing a bug about this. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

fbartolom wrote: As a matter of fact I moved everything in the actor and the error went away. Cool. I’m glad you got this resolved. ps 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. [quote='887029022, Etresoft, /thread/825634?answerId=887029022#887029022, /profile/Etresoft'] none of the classes defined in any Apple API are actually sendable [/quote] Hmmmm, that’s a bit extreme. There are plenty of classes that are sendable in our various platform SDKs. For the ones that aren’t, there are two common reasons: The class really isn’t sendable. The class is probably sendable but hasn’t been annotated as such. Sadly, it’s hard to distinguish these cases. Which makes things tricky because the available paths forward vary by case: If the class really isn’t sendable, your only good option is, as you say, extract the data from the class into your own type that is sendable, send that, and then, if necessary, reconstruct the class instance on t

It took me a while — proving a negative is hard! — but I’ve confirmed that there’s no specific API to determine if you’re running as a guest user. As you’ve found, there might be ways you can do this implicitly, but I’m not a fan of such techniques because such correlations can break down as the system evolves. If this is something that your app would benefit from, I encourage you to file an enhancement request for such an API, making sure to describe why you need it, with a focus on the user-level benefit. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Can you explain more about what the issue is? Not everyone here on the forums has access to FB22712056. Also, you title says: I have the same and it’s not clear what you’re referring to. The same as what? ps Regarding the bug reporting process, you can learn a lot more about that in my Bug Reporting: How and Why? psot. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com