Dear Apple Customer Support, I’m developing a new Swift iPadOS app and I want the app to run in landscape only (portrait disabled). In Xcode, under Target > General > Deployment Info > Device Orientation, if I select only Landscape Left and Landscape Right, the app builds successfully, but during upload/validation I receive this message and the upload is blocked: “Update the Info.plist: Support for all orientations will soon be required.” Could you please advise what the correct/recommended way is to keep an iPad app locked to landscape only while complying with the current App Store upload requirements? Is there a specific Info.plist configuration (e.g., UISupportedInterfaceOrientations~ipad) or another setting that should be used? Thank you,
Search results for
build disappears
50,294 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello, my app is designed for frequent travelers. It's kind of a collectors book. The user collects continents, countries, states, cities, sub-cities, rivers, seas etc. All the required data for that were well provided by CLPlacemark ... I also understand, that you try to provide good quality in the presentation of the (postal) addresses. The new API looks quiet good for this purpose. I never constructed a postal address by my own, as I understand the difficulties to build a proper postal address based on the users local needs. For that I used the postalAddress of CLPlacemark. Are there other ways to get this detailed informations? I really enjoyed the detailed data/Infos of the CLPlacemarks. Used to that richness of content and now seeing the puristic MapItem address strings is similar to be used to modern HDR-TVs and suddenly fall back to a Black&White TV from the 1960. So far new APIs were allways some kind of a better way to achieve something. Well some better, some not so good.. but it was a
Topic:
App & System Services
SubTopic:
Maps & Location
Tags:
I've been working on UI Tests for a month or two and things have been great. But I believe there was a recent update to Xcode [running Version 26.2 (17C52)] and since then about 80% of the time when I try to view the test results so I can see the screenshots and video, Xcode crashes hard and I have to open it again. I've tried cleaning the Build folder and Derived Data and all sorts of stuff like that. Restarted Xcode, restarted my computer, etc. Any idea of how I can avoid these crashes?
Hello, We're developing endpoint security software using the Endpoint Security framework, and we've encountered challenges with the behavior change in macOS 15 regarding provisioning UDIDs in cloned VMs. The Change Prior to macOS 15, cloning a VM preserved its UDID (format: 0000FE00-9C4ED9F68BBDC72D). Starting with macOS 15, cloned VMs receive a new UDID generated from the host's Secure Enclave (format: b043d27202c7ac37ca3c6b82673302225485cae9), making each clone effectively a new device. Our Workflow We maintain a clean base VM image and clone it for each test run. We add the base VM's UDID to our provisioning profile once, then create clones which (previously) retained that same UDID, allowing us to start new testing cycles without re-registering devices. This is essential because our product involves low-level system integration through the Endpoint Security framework, and if something goes wrong during development, it has the potential to affect system stability. To prevent any cascading issues between te
Topic:
App & System Services
SubTopic:
Core OS
Tags:
macOS
Provisioning Profiles
Code Signing
Virtualization
One of the biggest ongoing frustrations with Apple’s App Review process is inconsistency across builds of the same app version. We regularly encounter the following situation: A build of a new version is reviewed and approved. Shortly after, we submit another build of the same version, often containing only a minor bug fix. This second build is suddenly rejected for an issue that was never mentioned in the previously approved build. After explaining the situation and resubmitting, the build is usually approved. While this may seem manageable on paper, in practice it causes unnecessary delays, especially for time-critical patches and hotfixes that need to reach users quickly. The core issue is predictability: If a guideline violation exists, it should be identified consistently across all builds of that version. If functionality is effectively unchanged, review outcomes should not vary based on reviewer interpretation. Developers should not have to
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
When using App Intent, I noticed that we cannot process the image directly within the invoked UI. It appears that this is restricted by Apple’s privacy protections—any attempt to handle the data immediately results in the background privacy indicator showing a blocked status. Therefore, App Intent does not seem to meet our need to process user-provided images directly. This sounds like you implemented a UI snippet as part of your intent, and not all SwiftUI features are available in a UI snippet — for example, these snippets aren't interactive. Details here matter, so to discuss how you can build an intent that works for your needs, it'd be helpful to have a test project or test code that demonstrates what you tried and where you ran into trouble so that we can more fully explore this. — Ed Ford, DTS Engineer
Topic:
App & System Services
SubTopic:
Automation & Scripting
Tags:
I have a Apple Developer accounts for development purposes only and that is also used for testing builds via TestFlight. Is the Age Ratings Responses updates due by the end of January 2026 still required even to send builds to TestFlight?
I think this is because TestFlight disables certain sandbox flags for regulatory features. Apple might treat TestFlight builds as production like for some entitlements.
Topic:
App & System Services
SubTopic:
General
Tags:
As a follow up, three further points: I tried this on someone else’s machine. Same issue. So it’s not a config issue with my Xcode / machine. Secondly, one doesn’t need to go thru the archive step, just run the executable produced for the Xcode run. Issue not seen if a debug build is used.
Topic:
Media Technologies
SubTopic:
Video
Tags:
Can confirm, based on what customer support said and my actions, it seems all I had to do was add a new version in App Store Connect to get the app in an editable state to edit the age ratings. After submitting the age ratings, the warning message at the top (about updating the age ratings) did not immediately disappear, but when I checked back maybe 20 minutes later, it had gone, so it seems it worked. Did not have to upload a new build, etc, although my current builds appear expired.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Hi everyone, I’ve completely removed my App Clip: Deleted all Advanced App Clip Experiences Removed the App Clip target from my build Removed App Clip references from my apple-app-site-association file Deleted the meta tag from my website: However: When scanning the QR code, the App Clip card still appears with: This App Clip is not currently available in your country or region. This link still works for my App Clip, which is not what I expected: https://appclip.apple.com/id?p=com.example.appclip Does anyone know why the App Clip card is still showing and how to fully remove it? Thanks!
Hi everyone, I’ve removed my App Clip completely: Deleted all Advanced App Clip Experiences Removed the App Clip target from my build Removed App Clip references from my apple-app-site-association file Deleted the meta tag from my website: But when I scan the QR code, the App Clip card still appears with: This App Clip is not currently available in your country or region. Does anyone know why this is still showing and how to fully remove it? we need to show our website when this QRCode is scanned. Thanks!
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?
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
SKStorefront.countryCode always returns US in TestFlight and sandbox, even when sandbox Apple ID is set to a different country. Is this expected behavior? Is SKStorefront guaranteed to return the correct storefront only for production App Store builds?
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
Tags:
StoreKit Test
StoreKit
In-App Purchase
TestFlight
Hi @DTS Engineer Albert, can you please help to resolve issue with submitting build made with 26.2 for review to release TestFlight build to external testers? I'm always getting This build is using a beta version of Xcode and can’t be submitted. I tried everything from cleaning DerivedData to fully reinstalling xCode and tools to 26.2. Nothing helps and I can't share my first app with volunteers to test.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: