TipKit Q&A

Is there any news on Help Bundle issues from macOS 26? FB17996362 FB19414854 FB17996178 FB17460960

I have a section near the bottom of a ScrollView / LazyVStack. I want to show a popoverTip anchored to a button in that section, but only once the user has actually scrolled to it not on view load (otherwise the tip shows floating at the bottom of the screen). I tried to use onAppear but it fires as soon as the view is inserted into the hierarchy which on a LazyVStack can happen slightly before the view is truly in the viewport. I fell back to using onScrollVisibilityChange to write the @Parameter only when the section is actually visible: .onScrollVisibilityChange { isVisible in MyTip.sectionVisible = isVisible } This correctly gates visibility, but on some older devices I noticed that writing/reading @Parameter mid-scroll causes hitches. Is there a recommended TipKit pattern for this use case: showing a popoverTip only when its anchor has been scrolled into view that doesn't require a reactive write during active scroll? thanks

Is there a way to expose to users a reset all tips after tip center is setup? Think a 'help' 'faq' or 'onboarding' where the user might want to see it again during the current app run, not after the next launch. I didn't see anything like this back in 2024 when I wrote this feedback so I assume it isn't a supported workflow with the current API. FB14080356

My designers like TipKit, especially the newer flavor we can control the content. What are some best practices or tips and tricks to share with product owners when designing around what the framework is capable of doing? Concepts that might be relevant: Onboarding FAQ Progressive disclosure of new features HELP / support workflows