build disappears

Feedback number: FB20451665 When building with Xcode 26, Voice Over is reporting an extra tab when swiping through tabs. Please see the sample project below: /* This is a Sample project to show that I believe there is a Voice Over bug in iOS 26. When swiping through tabs with Voice Over active, there always appears to be an extra tab. Here I have 5 tabs, when on tab one VO reads out tab 1 of 6, then tab 2 of 6, all the way to the last tab, when voice over reads out tab 5 of 6. Never tab 6 of 6. Is there a possibility that voice over is picking up the underlying `more` tab and reading that out? This has also been reportedly found in the Files app here: https://www.applevis.com/comment/195441#comment-195441 */ struct ContentView: View { var body: some View { TabView { /// Activating this has Voice over telling us there are 6 Tabs. Tab(RootTab.home.title, systemImage: circle.fill) { Text(This is the (RootTab.home.title.capitalized) screen) } .accessibilityLabel((RootTab.home.title.capitalized) tab) .acc

I have an iOS app with a QuickLook extension. I also added Apple Vision Pro in the target's General > Supported Destinations section. About one year ago, I was able to run the app on iPhone, iPad and Apple Vision Pro Simulators. Today I tried running it again on Apple Vision Pro with Xcode 26.0.1, but Xcode shows this error: Try again later. Appex bundle at ~/Library/Developer/CoreSimulator/Devices/F6B3CCA8-82FA-485F-A306-CF85FF589096/data/Library/Caches/com.apple.mobile.installd.staging/temp.PWLT59/extracted/problem.app/PlugIns/problemQuickLook.appex with id org.example.problem.problemQuickLook specifies a value (com.apple.quicklook.preview) for the NSExtensionPointIdentifier key in the NSExtension dictionary in its Info.plist that does not correspond to a known extension point. I tried again later a couple times, even after running Clean Build Folder Immediately, without any change. I can reproduce this with a fresh Xcode project to which I add a Quick Look Preview Extension and Apple Vision Pro

Hi Apple team, For our iPhone app (App Store build), a small subset of devices report DCAppAttestService.isSupported == false, preventing App Attest from being enabled. Approx. impact: 0.23% (352/153,791) iOS observed: Broadly 15.x–18.7 (also saw a few anomalous entries ios/26.0, likely client logging noise) Device models: Multiple generations (iPhone8–iPhone17); a few iPad7 entries present although the app targets iPhone Questions In iPhone main app context, what conditions can make isSupported return false on iOS 14+? Are there known device/iOS cases where temporary false can occur (SEP/TrustChain related)? Any recommended remediation (e.g., DFU restore)? Could you share logging guidance (Console.app subsystem/keywords) to investigate such cases? What fallback policy do you recommend when isSupported == false (e.g., SE-backed signature + DeviceCheck + risk rules), and any limitations? We can provide sysdiagnose/Console logs and more case details upon request. Thank you, —

Hi Please when we upload our App from Xcode to App Store Connect, we do receive upload message but when we go to App store Connect interface, there we see our app being in process but it gets disabled and never goes to next step, and we waited for more than 2 hours, also we haven't received any email when we upload the app and when we refresh the page, the build in processing gets disappeared.

I built a TestFlight version of my unpublished app. While using it, I wanted to test out the subscription purchase and when I did, I used my real production Apple ID and not a Sandbox test account to purchase the subscription. I was surprised to see that it worked and I was able to use the test subscription in the app. However, I now have no way of canceling it. It has renewed every day at the same time due to the accelerated TestFlight subscription rate (it's a monthly sub). I read that it should stop auto-renewing after the 6th time, but I believe it's been over a week now and it still hasn't cancelled. I understand that it's not a real purchase, but I would still like to cancel it so I can try it without the purchase again using this account and also use it with a different Sandbox account. Can someone help me with canceling it? Since the account I used was not a Sandbox account, I can't just clear the purchase history in App Store Connect. Also, I can't go into my personal account settings to remove the s

Since legacyScreenSaver is still the thing running screensavers we make, and it's still buggy, why won't they give us a new template for building screensavers that run in the new engine? And hopefully they don't require them to blend in with the desktop, because most of us don't want that. A wallpaper is a wallpaper, and a screensaver is a screensaver.

FB20444423 was already filed, please help us on: Is it possible to fix the following issue on new Macos version? Is there any AppStore configuration that can mitigate this issue? Similar issues: https://developer.apple.com/forums/thread/778746 https://developer.apple.com/forums/thread/781317?page=1#836167022 Reproduce Version: Macos 15.3.2 and above. Reproduce Steps: Copy and run the following desktop watermark app(attachment); 2.After the watermark app running a watermark window is showing at the left top corner. 3. Open App Store and try to install any app, after the confirm installation dialog appears, move the App Store window to desktop watermark area, the confirm installation button will disappear. On some Mac, we can see a different app installation behavior, as the following picture shows, with the following behavior the app installation works on Macos15.3 and above. #import #import int main(int argc, const char * argv[]) { @autoreleasepool { // insert code here... NSLog(@App started); //TO

Hi After several successful development builds of my iOS app (built with Adobe Animate 24.0 Build 305 + AIR SDK 51.2.2.4), I moved to the distribution stage. The build was rejected by App Review due to crashing. To investigate, I uploaded the app to TestFlight and tested it myself. It immediately crashes on launch. To rule out my project code, I created a minimal build containing only one image (no code), but that also crashes in TestFlight. Development builds run fine on my device when using a development provisioning profile — the issue only occurs with TestFlight / distribution builds. Is there a way to identify the crash reason from Apple’s side? Or does iOS no longer support Animate / AIR SDK builds in distribution? I have crash logs (.ips) available and can share them if needed. Any guidance would be greatly appreciated. Thanks in advance.