Apple Maps Guides

Hi, we have PWA for which we´ve built a wrapper using PWA Builder tool and we are experiencing an issue with apple sign in. When we try to redirect the user to https://appleid.apple.com/auth/authorize?...params..., a bottom sheet login prompt appears and only once the user signs in using the prompt he is then redirected to the url where he needs to sign in again and then we get the callback. We want to get rid of that bottom sheet prompt. The code we´ve tried: ` iosButton.addEventListener('click', function () { window.location.href = https://appleid.apple.com/auth/authorize?client_id=xxxxx&redirect_uri=xxxxx&response_type=code%20id_token&scope=name%20email&response_mode=form_post; });` The alternative code we´ve tried for which it seems that nothing happens, we only see the Started alert, we´ve confirmed that there is no other error : `

hello i am new to apple ecosystem and development i have some coding experience with c# now i like to develop my game for iphone 16 and up(due to ability to run ai models) but i am having hard time figuring out what to use there is a lot of resources for scene-kit but on its doc page it says its deprecated so i look at the reality-kit docs and tutorials and its strictly tells how to develop for visionos and i am really confused about this since there is no tutorials that shows how to develop a game for ios with reality-kit that does not focus visionos. i just want to develop for iphone 16 and up but i cant find resources focuses at that.

Dear Apple engineers, We have developed a DriverKit (DEXT) driver for an HBA RAID controller. The RAID controller is connected to hosts through Thunderbolt (PCIe port of the Thunderbolt controller). We do plug/unplug tests to verify the developed driver. The test always fails in about 100 cycles with a MacOS crash (panic). The panic contains “LLC Bus error (Unavailable) from cpu0: FAR=0xa40100008 LLC_ERR_STS/ADR/INF=0x80/0x300480a40100008/0x1400000005 addr=0xa40100008 cmd=0x18(ACC_CIFL2C_CMD_RD_LD: request for load miss in E or S state)” At first we assumed that the issue is with hardware. But we did this test on different hosts (MacMini M3 and M4) with different units of our device. The error points to the same physical address FAR=0xa40100008 even if the hosts are different. The 2 full panic logs are attached (one for M4, another one for M3 host). Could you share your understanding of the crash and give any hints on how we can fix it? Please let us know if you need any additional data. Thank you M3

Hello, Our Xcode Cloud builds are successfully archiving but fail every time during the Export archive for app-store distribution step. The issue appears to be a persistent authentication failure with App Store Connect that we are unable to resolve. Primary Error: The build logs show a critical authentication failure. IDEDistribution.critical.log shows: App Store Connect request for store configuration failed for account Session Proxy Provider... Unable to authenticate with App Store Connect. DVTITunesSoftwareService.log specifies the error is DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy. The build process eventually terminates during the IDEDistributionSymbolsStep with an Rsync failed error, which we believe is a symptom of the earlier authentication failure. Troubleshooting Already Performed: We have already taken the following steps without success: Verified the account used for the integration has Account Holder and Admin roles. Confirmed th

I watched this year WWDC25 Read Documents using the Vision framework. At the end of video there is mention of new DetectHandPoseRequest model for hand pose detection in Vision API. I looked Apple documentation and I don't see new revision. Moreover probably typo in video because there is only DetectHumanPoseRequst (swift based) and VNDetectHumanHandPoseRequest (obj-c based) (notice lack of Human prefix in WWDC video) First one have revision only added in iOS 18+: https://developer.apple.com/documentation/vision/detecthumanhandposerequest/revision-swift.enum/revision1 Second one have revision only added in iOS14+: https://developer.apple.com/documentation/vision/vndetecthumanhandposerequestrevision1 I don't see any new revision targeting iOS26+

I'm experiencing an issue with Sign In with Apple integration in my React Native Expo app (Bundle ID: com.anonymous.TuZjemyApp). Problem Description: When users attempt to sign in using Sign In with Apple, they successfully complete Face ID/password authentication, but then receive a Sign-Up not completed error message. The authentication flow appears to stop at this point and doesn't return the identity token to my app. Technical Details: Frontend Implementation: Using expo-apple-authentication. Requesting scopes: FULL_NAME and EMAIL App is properly configured in app.json with: usesAppleSignIn: true Entitlement: com.apple.developer.applesignin Backend Implementation: Endpoint: POST /api/auth/apple Using apple-signin-auth package for token verification Verifying tokens with audience: com.anonymous.TuZjemyApp Backend creates/updates user accounts based on Apple ID Question: I'm not sure why the authentication flow stops with Sign-Up not completed after succ

Hi everyone, I recently acquired an app through an acquisition transaction. The process involved sending funds to an escrow service, ... unfortunately, the day I did that, the seller received an app transfer filter (apparently due to a spike in refund requests). As a result, I now own the codebase and Android version of the app, but I do not have access to the iOS version under the original developer account. My Questions: 1. Feasibility: Is it possible to take down or disable the existing iOS app (which has active subscribers) and republish it under my own Apple Developer account? If so, what are the steps and potential pitfalls? 2. Subscriptions: How would this transition affect active subscribers? Can I migrate them to a new app, or would they need to resubscribe? 3. Best Practices: Is this approach advisable, or are there better ways to handle this situation (e.g., negotiating with the seller, contacting Apple Support, etc.)? Additional Context: I have full access to the codebase and bac

Hi everyone, I’ve been exploring the process of building a food delivery app for iOS — something similar in concept to Uber Eats or DoorDash — and I wanted to get insights from this community on how to make it scalable, efficient, and user-friendly from a technical standpoint. I recently went through a really detailed guide on Food Delivery App Development that covers architecture, features, and cost estimation. It got me thinking about a few Apple-specific development challenges and opportunities: Optimizing real-time order tracking using MapKit + Core Location — how are developers here handling live driver updates efficiently without draining battery or hitting API rate limits? Push notifications & dynamic updates — what’s the best way to design these using Apple Push Notification service (APNs) to ensure timely delivery and minimal latency? Data synchronization across user roles (customer, restaurant, driver) — would CloudKit be a viable option for lightweight sync, or should

Hello, I currently have an app that includes the Sign in with Apple feature, and I need to transfer this app to another app team. I have reviewed all official documentation but have not found the answer I need. My situation has some specificities, and I hope to receive assistance. The .p8 key created by the original developer team has been lost, and the app’s backend does not use a .p8 key for verification—instead, it verifies by obtaining Apple’s public key. However, according to the official documentation I reviewed, obtaining a transfer identifier during the app transfer process requires a client_secret generated from the original team’s .p8 key. This has left us facing a challenge, and we have two potential approaches to address this issue: Q1: During the transfer, is it possible to skip obtaining the transfer identifier and proceed directly with the app transfer, without performing any backend operations? Is this approach feasible? Q2: If the above approach is not feasible, should we cr

I am facing an issue while trying to staple a notarization ticket to my signed macOS installer package. Details of my setup: The .pkg file is signed using my Developer ID Installer certificate. The app inside the package is signed using my Developer ID Application certificate. Notarization via xcrun notarytool completes successfully with status: Accepted. However, the stapler command fails with the following error: xcrun stapler staple -v /Users/mac-test/Desktop/IPMPlus_Arm_Installer_signed.pkg Processing: /Users/mac-test/Desktop/IPMPlus_Arm_Installer_signed.pkg Could not validate ticket for /Users/mac-test/Desktop/IPMPlus_Arm_Installer_signed.pkg The staple and validate action failed! Error 65. I verified that all other Apple notarization-related servers (api.apple-cloudkit.com, gs.apple.com, ocsp.apple.com, ocsp2.apple.com, crl.apple.com, developer.apple.com) are reachable. However, the domain cdn-apple-cloudkit.apple.com cannot be resolved from any network, including mobile or public Wi-F

I am posting here to express my significant concern regarding the excessive time my Apple Developer Program account application has been held under review. It has now been over a month. This application is for a non-profit church service app. I have provided every single piece of documentation requested—and then some. It honestly feels like I've submitted enough information that if they asked for the original blueprint of the church building, I could hand that over too. The entire process is currently stalled, preventing a service-oriented application from being deployed and ultimately hindering our outreach efforts. Has anyone else experienced a review period this long for a clear-cut non-profit application? More directly, to the Apple Developer Team: What is the current expected timeframe for approval, and why is this particular application still pending after more than 30 days, despite comprehensive documentation? This delay is beyond frustrating and needs an immediate resolution.