build disappears

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.

Thank you for your detailed answer. I reproduced your steps and see different outcomes. Let me answer your first two questions and then describe how I reproduced your steps and where I see differences. Answers The first divergence I see is at this step. I don’t have your accessory on my network so no local traffic is generated, so there’s no local network alert Indeed that checkbox makes the app itself send similar data than our hardware, using multicast. I don’t understand how that’s possible if this is a “clean install” of macOS. Where could it possible get a different usage string? I should have been clearer. It shows the string This will allow the app to discover, connect to and collect data from devices on your network. which we did not set ourselves. I could not figure out if it comes from an other app, or if it's the default usage description. Reproduction steps Here's a Dropbox link to our app (zipped): https://www.dropbox.com/scl/fi/btnpz64u8rz7y7t0dicbu/FM-Mac-App-Test-5.1.zip?rlkey=8g43pvph7qrld12h

How exactly were you able to build on devlopment, I'm trying to build and test on my devlopment entitlement but it's not working right now

Thank you for your post and description. It appears that Apple Care support provided you with a valuable insight that seems to be the underlying issue. Have you attempted to create a new project file using the latest version of Xcode? This simple test can help identify whether your project file contains settings that require correction. Additionally, I recommend verifying that you are logged into the same Apple ID on each device and checking the available iCloud storage to ensure it is not full. Lastly, please ensure that you are utilizing the most recent version of Xcode, and identify the specific build version you are using. While I still believe that creating a new Xcode project and incorporating your existing source files can be beneficial, as it may address underlying corruption issues, I concur with Apple Care Support’s assessment that the issue lies within your existing project. Please let us know the results of your troubleshooting. Albert Pascual
  Worldwide Developer Relations.

Thank you for your post, which is indeed quite interesting. It appears that the update to macOS Tahoe 26.2 and Xcode 26.2 may have reset some of your configurations or introduced a bug affecting the saving of Model Providers. Have you installed Xcode 26.2 from the App Store or have you downloaded it from the developer’s website? What’s the build number? This issue has only occurred once after installation, and since then, it has been functioning correctly. However, it is important to determine whether this is a recurrence issue or if it has resolved itself after selecting the model. Ensure that your project settings are correctly pointing to your Model Provider. Sometimes updates can revert or misplace these configurations. Double-check that there is no additional update for Xcode 26.2.1 or later that might address this specific issue. Has anyone else experienced this issue? Albert Pascual
  Worldwide Developer Relations.

Thank you for the post and the image. Those have proven to be extremely helpful. I have two thoughts in mind regarding your situation. First, have you installed the latest version of Xcode available on the App Store? Second, are you targeting the release versions of iOS and watchOS? If both of these conditions are met, the next and most crucial step is to ensure that you have filed a bug report using the sysdiagnose tool from your machine. Additionally, it is essential to have the logs from the Xcode build that indicate the errors. My apologies that you are using Xcode Cloud quota. I will be honest that I do not know how that part works, but I will get familiar with it soon. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

This app is built with Ionic 8 / Capacitor 5. Below is the output on the Warnings from the Build. For what it's worth my application code is built in Javascript. Capacitor plugins probably use Swift/Objective-C, but that's at a lower level than my code, and I'm not using any plugins in this project that I haven't used successfully before in approved apps. App /Users/vic/dev/nx-myapp-oem/apps/myapp-mobile-app/ios/App/App.xcodeproj Update to recommended settings App Run script build phase '[CP] Embed Pods Frameworks' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking Based on dependency analysis in the script phase. /Users/vic/dev/nx-myapp-oem/apps/myapp-mobile-app/ios/App/App/Assets.xcassets /Users/vic/dev/nx-myapp-oem/apps/myapp-mobile-app/ios/App/App/Assets.xcassets:./Splash.imageset/(null)[2d][splash-2732x2732-1.png] The image

@DTS Engineer thanks for the information. you must build your app against the iOS 26.2 and iPadOS 26.2 SDKs and later, with Xcode 26.2 (17C52) and later But a clarification needed: is using Xcode 26 required only to access all API ? Can you confirm that to keep the app updatable on AppStore, it is enough to update meta data on age ratings and submit the app, even if compiled with Xcode 16 ?

Never mind. Building locally revealed the real problem.