I swear I’ve pushed builds soon after public Xcode releases before, but maybe I’m remembering wrong. 🤷 Still seems odd that a public Xcode release can’t submit apps when it ships.

Shoot, they beat me by 4 hours. I guess my search didn't find it because I was looking specifically for that error code or Xcode build number. Either way, this needs to be fixed. I don't install betas or even RCs to avoid headaches like this. Oh, well. :(

My guess is it’s less about keeping things under wraps and more about making sure the usual Simulator apps work well and look good. Supporting Duo in my relatively simple apps has already been kind of a PIA. Apple’s guidance still leaves some gaps, so I usually fall back to, “What does Apple do here?” That’s why seeing their apps in the sim is so helpful, especially since I’m not planning to buy a Duo.

I’m pretty sure that isn’t it. In my case, I’m confident it was moderated. The thread disappeared, my profile score dropped by about half, and Developer Support told me to repost it, though they didn’t have details on the specific takedown. My best guess is that it had something to do with linking to that thread from another thread, but I don’t actually know. That’s why I’m asking here. I’m looking for an official answer or a support contact who can explain what triggered the removal.

Thanks for the fast reply on this, possibly the fastest I’ve ever had. 🙏 I’ll keep an eye on it in Feedback Assistant. While I have your attention, is there any chance you or someone familiar with toolbar button behavior could look at these two issues? Both are still present in the latest iOS 27 dev beta: https://developer.apple.com/forums/thread/800099 https://developer.apple.com/forums/thread/804587

I went to implement this workaround and realized that using Image(systemName:) surfaces the icon-only toolbar button hit-target bug I reported here: https://developer.apple.com/forums/thread/800099 For my case, that’s a bigger issue than not having the tip, so looks like I'll keep waiting on this one. 😞

Just tried this, and using Image(systemName:) works! Not sure why I didn’t think of it before, but this may let me add the tip I originally wanted, back into the app. Thanks for the workaround! 🙏

Thanks for the workaround, I may have to give that a try. And yes, zoom transitions have been super-buggy. I've submitted feedbacks for both the issues mentioned in that thread, plus there's also this problem (can't prevent a back navigation): https://developer.apple.com/forums/thread/818848

Sure. I replied to that thread. (disabled toolbar buttons still bounce on tap)

Feels like “I can name that tune in 2 notes”…I can repro this bug in 14 lines! 😆

I think your analysis is correct, but I gave up on a workaround once I saw it in Apple’s own apps. I assume they’ll fix it, so any more time spent on a workaround feels wasted. I recommend filing a feedback in Feedback Assistant. I’ve been told the more reports they get, the more likely something is to be addressed…hopefully sooner rather than later. 🤞

@App Store Commerce Engineer Is this still the recommended workaround? Is there an update with the release of StoreKit 2?

I appreciate that, thanks! 🙏

@DTS Engineer, While I have your attention, would you mind taking a look at another post of mine that’s been unanswered for a couple of months—or helping route it to the right team? Free trial for one-time purchase: Is the $0 IAP workaround still recommended in 2026?

I only spent a little time looking for a workaround and didn’t find one. For now I’m just leaving it as is—it’s low stakes in my case and I’ve got higher-priority work to focus on.