build disappears

One screen in my app uses a navigation bar with some buttons added to the titleView and some buttons added as a customView of a single rightBarButtonItem. In iOS 26 (beta 9), if I switch to the home screen and back again, the titleView and rightBarButtonItem disappear and an overflow button (three dots) appears instead. Nothing happens when I click the overflow button. Here's a screen capture: https://youtu.be/tthRnMz98kA This also happens when I switch to another app, when I rotate the device or when I resize the app window. In all cases, there is enough room to show all the buttons, but they still disappear. I overrode the viewWillTransition function in my view controller and logged when that runs. I can see that if I switch to the home screen and back again before that runs (within one or two seconds), there's no problem. But once that runs, the navigation bar items disappear and the overflow button appears. I have not done anything to set up the overflow button and don't have an

Problem Description: In a SwiftUI application, I've wrapped UIKit's UIPageViewController using UIViewControllerRepresentable, naming the wrapped class PagedInfiniteScrollView. This component causes navigation bar elements (title and buttons) to disappear. This issue only occurs in Low Power Mode on a physical device. Steps to Reproduce: Enable Low Power Mode on a physical device and open the app's home page. From the home page, open a detail sheet containing PagedInfiniteScrollView. This detail page include a navigation title and a toolbar button in the top-right corner. PagedInfiniteScrollView supports horizontal swiping to switch pages. Tap the toolbar button in the top-right corner of the detail page to open an edit sheet. Without making any changes, close the edit sheet and return to the detail page. On the detail page, swipe left and right on the PagedInfiniteScrollView. Expected Result: When swiping the PagedInfiniteScrollView, the navigation title and top-right toolbar button of the detail pag

Has anyone else received the email “Final reminder: Answer the updated age ratings questions.” even though all live apps were updated for the age ratings months ago? We only have one new app that we created, but we haven’t even set up age ratings for it yet. The app has never had a build uploaded. Did we receive this email because of this app? We also deleted some apps in the past. Could the email have been sent because of those deleted apps?

I uploaded a build to testflight and released it to Internal testers, however when the testers tried downloading the app a alert dialog shows the following: Could not install [App] The requested app is not available or doesn't exist. Also tried to submit it via external testers but getting another error.

The latest version of Xcode available on: https://developer.apple.com/download/applications/ is Xcode 26.2 build 17C52. It was released today, December 12, 2025. However, uploads are failing with error: Validation failed. This bundle is invalid. Apple is not currently accepting applications built with this version of Xcode. I have verified my Xcode is not beta: I think that at least the non-release candidate, latest version of Xcode should be allowed to submit apps.

Hi everyone, I’m looking for some help or clarification regarding repeated rejections under Guideline 3.1.3 - Business - Payments - Other Purchase Methods. In earlier versions of our app we did experiment with using in-app purchases for our eSIM-related service (which App Review treats as a physical good/service). After the first rejections, we fully reworked the payment flow. In the current build we have: Completely removed any use of the in-app purchase API / StoreKit and removed all UI elements and wording mention in-app purchases. Detached all in-app purchase products and marked all previously created IAP products as “removed from sale”, so they are no longer available to users. Moved all payments to an external outside of the in-app purchase API, which (as I understand it) is exactly what Guideline 3.1.3 requires for physical goods/services. Despite this, the app is still being rejected with the same 3.1.3 message about using in-app purchases for physical goods, without any new details or update