build disappears

Under iPadsOS 26.0 and 26.1, if a view controller is presented with a presentation style of fullScreen or pageSheet, and the view controller is setup with a UISearchController that has obscuresBackgroundDuringPresentation set to true, then when cancelling the search the view controller is being dismissed when it should not be. To replicate, create a new iOS project based on Swift/Storyboard using Xcode 26.0 or Xcode 26.1. Update ViewController.swift with the following code: import UIKit class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() view.backgroundColor = .systemBackground title = Root navigationItem.rightBarButtonItems = [ UIBarButtonItem(title: Full, primaryAction: .init(handler: { _ in self.showModal(with: .fullScreen) })), UIBarButtonItem(title: Page, primaryAction: .init(handler: { _ in self.showModal(with: .pageSheet) })), UIBarButtonItem(title: Form, primaryAction: .init(handler: { _ in self.showModal(with: .formSheet) })), ] } private func showModal(with sty

I am seeing this when trying to load the TestFlight page: We can’t process your request. Try reloading the page. If the problem persists, contact us. b12f62a4-c608-4b5f-8a8c-23a9fa405943 This was immediately after I accidentally uploaded a build with a duplicate build number.

If the extension uses manifest v3 and a background script in the form of a service worker, then in Safari it is not possible to open the background script debugging window. If I expand the Developer menu in Safari, there is nothing under Web Extension Background Data (or disappear after click), which is an error. In other browsers (Edge, Chrome, Opera, Firefox) this works correctly. If I switch the background script back to non-persistent script mode, everything works fine and from the Developer menu and the Web Extension Background Data submenu I am able to open the background script debugging window for the extension. Am I doing something wrong?

Beta reviews have historically taken only a few minutes. Ours has been in review for a day at this point. The Production build is already approved, but our Beta testers still don't have access. Is there anything we can do?

Good afternoon, I have a project called 'Minha Ufal'. When I try to generate the build, I'm asked to log in to Apple Developer. After that, I get the following error: Log in to your Apple Developer account to continue √ Apple ID: ... wilamis@****** › Restoring session C:Userswill.app-storeauthwillcookie √ Logged in Local session ✖ Failed to register bundle identifier br.edu.ufal Apple 403 detected - Access forbidden. This request is forbidden for security reasons - You currently don't have access to this membership resource. Error: build command failed. I currently have App Manager, Customer Support, and Sales permissions. Could you help me or give me some insight on how to solve this problem? I thank you in advance and await your response.

Hi there, I don't know why I am missing the add button for build section. I can verify under TestFlight that all builds are Ready to submit status I am not sure if it's because the version issue or what.

My project build failed in Xcode Cloud(works well in my local Mac), and the error shows: Preparing build for App Store Connect failed The error message is not clear enough to help us find the solution to fix it. Can anyone help with it?

We are integrating Xcode Cloud into a larger CI/CD pipeline and ran into a serious limitation that makes proper build status reporting nearly impossible. Currently, Xcode Cloud provides only the following custom script phases: • ci_post_clone.sh • ci_pre_xcodebuild.sh • ci_post_xcodebuild.sh However, if a build fails during the actual Xcode build phase (for example, due to a compilation error, unit test failure, or signing issue), the ci_post_xcodebuild.sh script does not run. This means there is no guaranteed way to execute cleanup steps or send external notifications (e.g., updating build status in Bitbucket, Slack, or any external CI system). In any robust CI/CD setup, it’s critical to have a “finally” or “always run” hook that executes regardless of build success or failure — similar to post blocks in Jenkins, finally steps in GitHub Actions, or after_script in GitLab CI. Without such a mechanism, we cannot reliably integrate Xcode Cloud with the rest of our au

When Home tab opened, there is some white shadow on the bottom and the top sides of the list. But when switching to other tab or return to Home tab this shadow disappearing for a second and appearing again. Actual for iOS 26.0.1 on simulator and on real device. Below is short example code that can reproduce issue. When change let pages = UIPageViewController(transitionStyle: .scroll, navigationOrientation: .horizontal) to let pages = UIPageViewController(transitionStyle: .pageCurl, navigationOrientation: .horizontal) issue is not reproduced. import SwiftUI @main struct GlassTestApp: App { var body: some Scene { WindowGroup { MainView() .ignoresSafeArea() } } } struct MainView: UIViewControllerRepresentable { func makeUIViewController(context: Context) -> UITabBarController { let controller = UITabBarController() let home = Home() home.tabBarItem = UITabBarItem(title: Home, image: UIImage(systemName: house), tag: 1) let settings = UIHostingController(rootView: Settings()) settings.tabBarItem = UITa

Hi everyone, I’m building a simple sticky notes app that allows users to place a note widget on their home screen. Each widget displays a user-created sticky note. To let users choose which note to show, I’ve implemented an Intent that presents a list of existing sticky notes. The list is built using IntentItems, and for each item I assign an image to visually represent the note. Each sticky note can have a different background color and optional image, so I generate a small PNG (150×150, ~30 KB) and include it in the app bundle. However, when I try to display the selection list, I get the following error: The action Select sticky note could not run because an unknown error occurred. If I tap OK and try again, the intent selector appears and works. Here’s what I’d like to understand: What could cause this unknown error when using images in IntentItems? Are there known limitations on image size, source, or format for intent item images? Can I supply a unique image per sticky note, or must all intent i