Search results for

Apple Maps Guides

154,023 results found

Post

Replies

Boosts

Views

Activity

Build/Archive failure in Xcode 16.2 after updating macOS to 26.2
We are encountering a build and archive failure in Xcode after updating our development machine to macOS 26.2. Environment: macOS: 26.2 Xcode: 16.2 iOS Deployment Target / Runtime: iOS 18.5 App Type: Production iOS app (App Store distribution) Issue: Before updating macOS, the project built and archived successfully. After the macOS 26.2 update, archiving fails consistently, even though no major changes were made to the project code or configuration. Certificates, provisioning profiles, and signing settings are correctly configured. The issue appears to be related to the macOS/Xcode environment rather than application logic. Steps to Reproduce: Open the existing iOS project in Xcode 16.2. Select the App Store distribution scheme. Attempt to Archive the project. Archive/build fails. Expected Result: Successful archive allowing upload to App Store Connect. Actual Result: Archive fails after macOS 26.2 update. Additional Info: This post is linked to Apple Developer Technical Support Case-ID: 18413014.
2
0
79
5d
Reply to Build/Archive failure in Xcode 16.2 after updating macOS to 26.2
Thank you for your response. We have updated our development environment to the latest versions: • macOS: 26.2 • Xcode: 26.2 • iOS Runtime / Deployment Target: iOS 18.5 Following your instructions, I exported the full build report. Due to file size limitations, I am including the relevant error messages below: error: Build input file cannot be found: '/Users/tech27systems/Library/Developer/Xcode/DerivedData/goneet_app-bfahpcjyjdsvwgecotulyqyigvpy/Build/Products/Debug-iphonesimulator/react-native-maps/ReactNativeMapsPrivacy.bundle/ReactNativeMapsPrivacy'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'react-native-maps-ReactNativeMapsPrivacy' from project 'Pods') error: Build input file cannot be found: '/Users/tech27systems/Library/Developer/Xcode/DerivedData/goneet_app-bfahpcjyjdsvwgecotulyqyigvpy/Build/Products/Debug-iphonesimulator/glog/glog_privacy.bundle/glog_privacy'. Did you forget to declare this file as an outpu
5d
How do I get access to the Accessory Setup Kit?
Hi! I would like to experiment with the Accessory Setup Kit, but I am not sure how I can add the required entitlement to my Apple Developer account. I added the following to the plist file: NSAccessorySetupKitSupports WiFi NSAccessorySetupWiFiSSIDPrefix test_ test And the following to the entitlements file: com.apple.developer.accessory-setup-kit But I am unable to build as my provisioning profile doesn't include com.apple.developer.accessory-setup-kit entitlement. On the developer portal, I navigated to “Certificates, Identifiers & Profiles” > “Identifiers” > “”, but I don't see it under Capabilities or App services, nor under requests. How do I configure my profile so that I am able to make use of this kit?
2
0
68
6d
AVAudioSession.outputVolume does not reflect system volume changes made while app is in background
I have a question regarding the behavior of AVAudioSession.sharedInstance().outputVolume. Observed behavior: When the app is in the foreground, I read audioSession.outputVolume (for example, 0.1). The app is then moved to the background. While the app is in the background, the user changes the system volume using the hardware buttons (for example, to 0.5). When the app returns to the foreground, audioSession.outputVolume still reports the previous value (0.1). From my testing, outputVolume only seems to update when the system volume is changed while the app is in the foreground. Volume changes made while the app is in the background are not reflected when the app returns to the foreground. Questions: According to Apple’s documentation for AVAudioSession.outputVolume: “The systemwide output volume set by the user.” https://developer.apple.com/documentation/avfaudio/avaudiosession/outputvolume However, based on our testing on iOS 18.6.2 and iOS 18.1, the observed behavior seems to differ from this desc
1
0
165
6d
Reply to Stuck in "Waiting for Review" for 11 Days - Missed Critical Launch Date
Hot take: Apple needs to ditch the '90% of apps reviewed in 48 hours' metric and just give us a worst-case ETA. It’s basic UX psychology: underpromise and overdeliver. If you tell me it takes a week and I get approved in two days? I’m stoked. But right now, the second that 48-hour mark hits, I’m stuck spamming F5 and doom-scrolling dev forums, looking for clues and convinced I’ve fallen into that cursed 10% with bad RNG. The 'Waiting for Review' status is a total black box—it tells you nothing. I saw some poor soul on Reddit who’s been in review limbo for three months... makes waiting a couple of weeks feel like a nothingburger. Honestly, just give us a hard upper limit. It’s way better for our sanity and actually lets us plan our roadmap around the worst-case scenario.
6d
Reply to 年間料金の支払いについて
Do you have access to the latest source code for your project? That's really the key question here. I agree with the poster above — when I've done development in the past, the app owner has their own Apple Developer account and invites the developer to join their team. The app should be submitted to App Review through the owner's account, not the developer's. A couple of other things to be aware of: if the annual Developer Program fee isn't paid and the account lapses, Apple will remove your app from the store. Once that happens, it's much harder to recover, so time is important here. Also, check any contracts you have with the development company. You may have rights to the source code, which could matter if the company's assets are being handled through bankruptcy proceedings. Without the source code, you'd essentially be starting over from scratch. The good news is that if you do manage to get the code and set up your own developer account, Apple has an app transfer process in Ap
Topic: Community SubTopic: Apple Developers Tags:
1w
Reply to Stuck in "Waiting for Review" for 11 Days - Missed Critical Launch Date
I've been in Waiting for Review since Jan 27 with no movement. We missed our launch date as well. Originally, we submitted on Jan 23, mistakenly assumed there was an issue because our app didn't move, and resubmitted on Jan 27. In hindsight, it likely lost 4 additional days. After submitting 3 requests to Apple Support, just to confirm our app was queued, they got back to us saying it was and that no additional action was required on our side. We're burning a ton of cash daily on back-end services that are running so Apple's reviewers can test all features, and our devs are sidelined until we get word on Apple's decision (first-time app submission). We anticipated the real challenges would begin once our app launched, and never thought they would start with Apple's review process. For what it's worth, it's the lack of communication and clarity from Apple that's been frustrating. Honestly, if they simply said we're backlogged and actively working to clear the queue,
1w
Reply to Developer Control Question
Hi there, You're on the right track in wanting to retain full control of your Apple Developer account while working with a freelancer. The best and most modern approach is to add the developer to your App Store Connect account with the Developer role. This allows them to access the necessary signing tools in Xcode without needing your personal credentials, and they can submit the app directly through App Store Connect. Sharing certificates and private keys (as your developer suggests) can be risky and is no longer considered best practice. Instead, you should handle signing through Xcode and App Store Connect, which ensures both security and control. This way, your app remains under your Apple Developer account, and you retain long-term control while allowing the developer to work without compromising security. Hope that helps! -Dean Reyburn, reyburnengineering.com iOS/MacOS app developer
1w
Developer Control Question
Hi everyone, I’m new to the Apple Developer side of things and I want to make sure I’m handling this correctly. I hired a freelance iOS developer to build my app. I have my own Apple Developer account (Individual), and I want the app published under my account. The developer says he needs me to create a Certificate Signing Request (CSR), then he will generate the distribution certificate on his end and send me the .cer file back. From there, he would use that for signing and submitting the app. My questions: 1. Is this the correct and modern way to handle app signing? 2. Should I instead just add him to my App Store Connect account with Developer access and let him manage signing through Xcode? Dev claims this won’t work, which I haven’t been able to prove or disprove. ChatGPT says it does,but other AI tools says it doesn’t. 3. Is there any risk in sharing certificates like this? 4. What is considered best practice in 2026 for working with freelancers while keeping full control of the accoun
1
0
60
1w
Regarding renewal of annual app registration fees
I've requested app development and am currently publishing it, but I can't contact the app development company and am unable to pay the annual fee to Apple. I don't know my registered account, so what should I do? I contacted Apple Japan, but they only handle personal inquiries and cannot handle business app development requests, so they suggested I post a question on this website. Thank you in advance.
1
0
242
1w
Developer Program enrollment still pending after payment
Hi everyone, I subscribed to the Apple Developer Program on Tuesday evening, November 4th, 2025. The payment has already been charged to my bank account, but my account still shows the status “Pending” with the message “Subscribe your membership”. It’s now been several days, and I haven’t received any confirmation email or any request for additional information. I already contacted Apple Support by email, but I’d like to know if other developers have experienced the same situation and how long it took before their account was activated. Thanks in advance for your help and feedback! — Martin
56
0
5.7k
1w
Reply to Unusually long “Waiting for Review” times this week (App Store + TestFlight delays?)
My team has also encountered a similar situation. In mid-January, the build (App ID: 1552207792) was submitted for review and remained in the Waiting for Review state for several days. The status did not change, so we tried resubmitting the build, but that did not help. A week later, we resubmitted it again after accepting the new Terms of Use in App Store Connect, thinking that might have been the cause of the delay. Currently, the app has been stuck in Waiting for Review since February 4th — it has now been 10 days. A request for an expedited review and contacting Apple have not had any impact on the situation.
1w