Apple Maps Guides

Hello, Other developers have reported similar issues. As mentioned in that thread, we're unable to provide support on behalf of Roblox and encourage you to report this behavior to them so they can address it. Generally speaking these forums are for providing code-level guidance for developers using Apple's frameworks.

Hi @Mattreg, ShazamKit for android 2.1.1 does support 16KB memory page addresses. In branch fix-16k you have correctly imported the latest ShazamKit for android version. I checked this via md5:a6426940b80c4ec5f18a644e4f59193f. As good measure I have also explicitly verified your shazamKit .aar library for 16KB memory compatibility, and I confirm it's 16KB compatible. Steps: unzip the .aar, navigate to the jni folder run (adjust for your environment) ~/android-sdk/ndk/29.0.14033849/toolchains/llvm/prebuilt/darwin-x86_64/bin/llvm-objdump -p libsigx.so | grep LOAD LOAD off 0x0000000000000000 vaddr 0x0000000000000000 paddr 0x0000000000000000 align 2**14 LOAD off 0x000000000005afe0 vaddr 0x000000000005efe0 paddr 0x000000000005efe0 align 2**14 LOAD off 0x000000000005bca0 vaddr 0x0000000000063ca0 paddr 0x0000000000063ca0 align 2**14 2**14 is means it is supporting 16KB pages , see https://developer.android.com/guide/practices/page-sizes. I did also run ~/android-sdk/build-tools/36.0.0/zipalign -v -c -P 16 4

It took some time but we have your bug back on track (-: @KayleeSC , Our bugs folks just sent you a request for more info via FB19582905. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hello Kanazawa Kenta, The Enterprise APIs aren't available to individuals; however, your university may qualify for research purposes. Please work with your university's administration to contact us to create an Enterprise Apple Developer Account for research purposes. See the Get in touch button.

I'd really like to have a way to integrate with Spotlight in the interim. Understood. I supported Spotlight importers back in the day, and as part of that I created infrastructure to make the whole task easier. I never got around to shipping that as sample code that because I expected CSImportExtension would come online and make it redundant. It seems like I was overly optimistic )-: My code was written in Objective-C, but I spent yesterday converting it to Swift [1]. There are two parts to this: QCFPlugIn — This is a generic mechanism for building different types of CFPlugIn implementations [2]. QSpotlightPlugIn — A type-specific subclass that handles Spotlight. QCFPlugIn.txt QSpotlightPlugIn.txt To use this, subclass QSpotlightPlugIn: private final class MySpotlight: QSpotlightPlugIn { override func importFrom(_ url: URL, type contextTypeUTI: UTType, updating attributes: NSMutableDictionary) throws { … your code here … } } and then invoke the infrastructure from your entry point: @_cdecl(MySpotlightFactory)

Welcome to the forum. Do you hope anyone here to know ??? You'd better contact Apple support.

@Verara20 May we ask which app/AppClip is affected in your case? We are currently only experiencing this error with one AppClip, but another one (for a completely different app/development team) is working fine. So we are still trying to figure out why one works and the other doesn't. The app that isn't working for us is an unlisted app. At first, we thought that might be the reason, but we simply don't know. It's depressing that we can't do anything at the moment to get the solution working again with iOS26. The console log shows that there are some requests that are going wrong and that didn't happen with iOS18. error 15:05:16.940931+0200 appstored AMSURLSession: [F50720EC] Session decoder failed. Result = (null); Error = Error Domain=ASDErrorDomain Code=507 Invalid Response Status: 14501 UserInfo={NSDebugDescription=Invalid Response Status: 14501} error 15:05:16.940942+0200 appstored AMSURLSession: [F50720EC] Task completed with error = Error Domain=ASDErrorDomain Code=507 Invalid Response Status: 14501 Us

could any of the following override this setting? My understanding is: Using certain third-party SDKs that might have their own encryption. -> YES The presence of specific Apple frameworks like CryptoKit or CommonCrypto, even if not used for non-exempt purposes. -> YES Standard HTTPS calls made through WKWebView. -> NO A temporary bug or caching issue in App Store Connect. -> Always possible, but unlikely.

@Claude31 All devices, physical and simulated. The code I provided consistently doesn't work. @Tomato I found a workaround involving measuring the screen aspect ratio to determine whether a device is an iPhone SE or not. Not the most elegant solution, but does the job. Your answer is interesting because I've always assumed that Apple didn't allow developers to access specific information like device name, etc. due to privacy concerns, so it never really occurred to me to just look up the model name and go from there. This is really useful information to me as it will allow me to tweak UI on a per-device basis, and more. Thank you!