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.

Me neither. The $0 IAP feels awkward from a user perspective, and a backend-managed trial with a single paid unlock would be much cleaner. The problem is the lack of clarity in the guidelines. Without confirmation from Apple, it feels risky to (try to) ship anything beyond the documented workaround.

I attached a focused test project to the Feedback item FB21078443, along with device diagnostics and screen recording. But if you don't have access to Apple's Feedback system, you can create the project by creating a new iOS app in Xcode, then replace ContentView.swift with the code in my first post. Then be sure to run it on a physical device.

Yeah, just wanted to make sure Apple’s aware of it, so officially reported it. And it looks like it already had some activity: *Recent Similar Reports now shows "Less than 10". Thanks for the workaround—I’ll give that a try!

Since my initial post, I learned it's probably best to not suppress reading of the text inside an image (see this post). It’s a device-level VoiceOver setting, so if someone has it on, they want to hear it—we probably shouldn’t override that.