eskimo

[quote='809562021, hpux735, /thread/809562, /profile/hpux735'] Has the functionality been walked back such that extensions can only be loaded in iOS from within the single app bundle? [/quote] I wouldn’t say “walked back” because full ExtensionKit support was never a feature of iOS. Well, I guess you could considered it to be walked back relative to macOS… Anyway, see my replies on this thread for the current state of affairs. [quote='809562021, hpux735, /thread/809562, /profile/hpux735'] What's the best way to achieve this? [/quote] There’s no way to achieve that goal for native code. If you’re willing to entertain the idea of non-native code then you have various options, the most obvious being: Support JavaScript via JavaScriptCore. Support Wasm with your own runtime [1]. Keep in mind, however, that this is only the technical side of this coin. On the business side, I want to be clear that I don’t work for App Review and thus can’t give definitive answers about this policy. I recommend that you review thei

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

Let’s focus this discussion on your earlier thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Cool. And, yeah, based on reports here on the forums, that seems to be a common pattern. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='868615022, Charita, /thread/805901?answerId=868615022#868615022, /profile/Charita'] It would be helpful if you could suggest a way in which this can be handled at my end. [/quote] I can suggest various options, but there are no good options here. I outlined the reasons for that in my previous post. Ignoring all the build-time stuff for the moment, let’s focus purely on the runtime aspects. You only want one version of this vendor’s code in the client app’s process. Where should that code be? If you statically link it in your framework then the client can’t access it in the normal way. If the client statically links it into their app then your framework can’t easily access it. There’s no standalone framework available from the vendor, so that’s not an option. I see three potential options: You statically link the code into your framework and provide the necessary infrastructure for the client to access it from there. You create a standalone framework from this code, ship it to your clients, and have bo

[quote='868450022, DTS Engineer, /thread/808875?answerId=868450022#868450022'] This gels with my understanding of how things should … work [/quote] Actually, that understanding was wrong. It seems that things only end up on Apple’s ‘naughty’ list if they’re revoked for the right (well, wrong) reasons, specifically, for compromised keys [1]. So, to test this stuff you need to check a certificate that the system really thinks is revoked. A good example is this: https://global-root-ca-revoked.chain-demos.digicert.com/ Using that I crafted a small test program that gets a server’s certificate chain and checks it for revocation. The code is at the end of this post. When I run this on macOS 15.7.1, I see this: will run task, url: https://example.com challenge NSURLAuthenticationMethodServerTrust will check chain did check chain, success: true did run task, status: 200, bytes: 513 will run task, url: https://revoked.badssl.com challenge NSURLAuthenticationMethodServerTrust will check chain did check chain, success:

[quote='868602022, ygbykov, /thread/808088?answerId=868602022#868602022, /profile/ygbykov'] Apple may want to reconsider how it interprets users force-quitting apps. [/quote] If you want to get your “two cents” in front of the folks who have the power to enact change, I suggest you put them in an enhancement request. One of the reasons why these behaviours are not documented is that Apple reserves the right to change them. This has happened in the past, and it’s not hard to imagine it happening again in the future. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You posted the same comment on that other thread and I’m gonna reply there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Bummer. In that case my advice is that you file an enhancement request against App Store Connect help asking for that RSS feedback. 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

[quote='868482022, Apple_Fox, /thread/807599?answerId=868482022#868482022, /profile/Apple_Fox'] Is SharePoint a server one that would cause issues with downloading docx files directly? [/quote] I expect that’ll depend on how the server is configured. I recommend that you write a small test project to fetch the URL and see what you get back. Usually this yields one of three results: The request succeeds with a 2xx status code and returns the right data. The request fails with a 4xx status code, indicating that you have to log in. In this case you may be able to gets things working using the authentication challenge mechanism in URLSession. The request success with a 2xx status code but the actual data is a login page. This is hard to deal with. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] I already feel bad asking you again [/quote] No worries. It gives me a good excuse to brush up on my debugging skills (-: [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] It turns out that MTE and Malloc Stack Logging cannot be enabled at the same time. [/quote] Bah. This isn’t super surprising, and it’s the sort of thing I’d know if I had an iPhone 17 to play with. It’s definitely time to ping my boss about that. [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] Unfortunately, I didn't really understand where/what to look for in Xcode. [/quote] OK. Lemme run you through a non-MTE example: Using Xcode 26.1 on macOS 15.7.1, I created an iOS app with two buttons wired up to these two methods: var memory: UnsafeMutableRawPointer? = nil func mallocAction() { self.memory = malloc(1024) } func freeAction() { free(self.memory) } In the scheme editor, I enabled

[quote='868407022, Mohsenomar, /thread/773903?answerId=868407022#868407022, /profile/Mohsenomar'] i have iPad generation 10 but I updated ipados 26.2 I need get back ipados 18 now… [/quote] Once you’ve updated to a new version of iOS, there’s no supported way to roll back to a previous version. The only exception to this rule is if the new version is a beta seed, in which case you can roll back to the previous public release. For advice on how to do that, see Apple Beta > FAQ > Support > How do I leave the Apple Beta Software Programme? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Ah, yes, sorry about that. That was a mix up on our part. The request is for you to: Enable additional logging by installing the following profiles: Wi-Fi for iOS/iPadOS VPN (Network Extension) for iOS/iPadOS FaceTime for iOS/iPadOS You can find all of these on our Bug Reporting > Profiles and Logs page. Reproduce the problem. Trigger a sysdiagnose log (see the Sysdiagnose for iOS/iPadOS instructions). Attach that to your bug report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can find my general advice for problems like this in Investigating Third-Party IDE Code-Signing Problems. But I also want to address this specific point: [quote='809448021, nickblair, /thread/809448, /profile/nickblair'] I can create an ipa file with vs using the wildcard bundle identifier [/quote] There’s no such thing as a “wildcard bundle identifier”. A bundle ID is always explicit. If you’re trying to use a * in your bundle ID, stuff is not going to work. There is such a thing as a wildcard App ID, but App IDs and bundle IDs are not the same same thing. An App ID is a key input to a provisioning profile; it determines the apps to which that profile applies. I talk about this more in TN3125 Inside Code Signing: Provisioning Profiles. A wildcard App ID creates a wildcard provisioning profile that authorises execution of all App IDs that match the pattern. However, each app’s bundle ID, and hence its App ID, must be explicit. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @

If you create a minimal package using productbuild — see Packaging Mac software for distribution for the exact command — does it exhibit the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com