build disappears

One additional point in some cases we also needed to set: myNSButton.imagePosition = .imageOnly In places where we used only a button without a label (because the buttons position made function obvious) if .imagePosition = .imageOnly was set to something other than .imageOnly, the button would disappear.

Thank you for your response. However, the situation may still need further attention. The latest build (2.1.5) has just been rejected, and I have already submitted a detailed reply through App Store Connect. The rejection appears to be due to a misunderstanding of the app’s core functionality. The app’s design is centered around on-device audio practice using the user’s own imported materials. The optional sample audio and the optional on-device AI model are downloaded only when the user explicitly requests them, and they can be removed at any time. There is no dynamic server-driven content or remote app behavior. I am preparing a full clarification and will post it here shortly. Thank you again for your time and attention.

My current goal is to ship the PCIe DriverKit. I want my customers to be able to install our DriverKit without having to disable SIP or anything like that. Absolutely. Why is there a difference between the Apple Development value and the Developer ID value? The two different values happen because of the development only variant that's added to all accounts. (a) This is the development only configuration (which all accounts have): 0xFFFFFFFF&0x00000000 (b) And this is the specific configuration you were approved for, which is unique to your account: 0x00001916&0x0000FFFF Unfortunately, the portal and Xcode handling of these overlapping configurations doesn't work all that well. You can find a description of what's actually going on here. However, note that I don't think the flow described at the end of that post actually works today. However, according to the URL you provided, would manual signing using a provisioning file created with a Distribution Developer ID be better? First off, please file a bug

Thank you for your post and the comprehensive description, including the accompanying images. It is intriguing to note that the button will be absent in iOS 26. Your application appears to be well-designed. May I request that you create a simple focused project where you can reproduce the same issue in iOS 26? The button disappears unless you add the key to the Info.plist file to disable Liquid Glass. If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert Pascual
  Worldwide Developer Relations.

The stackoverflow discussion mentions uploading of a build. I haven't done that. I just created the app in the apps and deleted it.

My current goal is to ship the PCIe DriverKit. I want my customers to be able to install our DriverKit without having to disable SIP or anything like that. I tried the following value as suggested, and the build did indeed pass. 0xFFFFFFFF&0x00000000 After checking the contents of the downloaded provisioning file again, I was able to clarify the problem. The value in the file created in App Development wasn't set properly. Created a provisioning file with DriverKit App Development and checked the value of IOPCIPrimaryMatch. 0xFFFFFFFF&0x00000000 Created a provisioning file with the Distribution Developer ID and checked the value of IOPCIPrimaryMatch. 0x00001916&0x0000FFFF Why is there a difference between the Apple Development value and the Developer ID value? My account belongs to a corporate account. Is this related? Also, when I check your post, it seems like I've never created a provisioning file. That's strange. Is the local file on my PC invalid? As I mentioned at the beginning, I f

I installed the RC (replacing 26.1), tested my app, and went to create a release for an update that happens to need to be released pretty quickly. I recall from previous experience RC builds could submit apps to the App Store so figured I wouldn’t run into any problems. Now I’m blocked. I could go download Xcode 26.1 and redownload the iOS 26.1 Simulator and retest my app with that SDK version but that’s a lot of wasted time/resources only to release the update on a very soon to be out of date SDK. :/ Do you expect this RC build to be accepted in the near future?

Hi Albert, Thanks for the clarification. In past cycles, RC builds have typically been permitted for submission within a few hours, so this situation is a bit unusual. I’m assuming iOS 26.2 will likely ship next week, but ASC is also warning developers that they may be overwhelmed during the holidays and encouraging early submissions — which puts us in a difficult position when RC uploads aren’t yet allowed. Being able to submit with the RC would let us validate TestFlight builds ahead of time and ensure a smooth transition once 26.2 is released. At the moment, it isn’t even possible to test distribution builds, which makes it hard to prepare properly. Could you shed some light on why RC submissions are blocked this time around? Thanks again for your help.

Thank you for providing this information. You are correct that the 26.2 RC is still not permitted to submit builds. The team typically updates this page when it is ready and open to submissions. https://developer.apple.com/help/app-store-connect/release-notes/ On the release notes, you’ll see something like “You can now upload apps built with Xcode….” I understand that submitting with RC versions is often possible, and I acknowledge that this may be an inconvenience. Please continue to monitor the release notes for updates. Could you please provide any reasons why you are unable to submit with the previous released version? Albert Pascual
  Worldwide Developer Relations.