Good question! I am calling the Tips.configure in my App file in a .task { } the same way as done in the Apple docs try Tips.configure([ .displayFrequency(.immediate), .datastoreLocation(.applicationDefault) ]) I'm not doing anything fancy (as far as I know). I configured with my Console that the try is not throwing any errors via TestFlight build. It's just not showing anything regardless.

I am following the basic configuration in my App file in a .task { } as seen in the Apple docs. try Tips.configure([ .displayFrequency(.immediate), .datastoreLocation(.applicationDefault) ]) With the Console, I was able to confirm that the try is not throwing any errors.

Alas @melsam I have deleted and reinstalled the App multiple times and have confirmed the same issue (not showing) on several other fresh devices installing the TipKit build from TestFlight. Has anyone else experienced this issue? I imagine I must be doing something wrong but I'm a loss :(

@melsam Since the release I've been testing on Xcode Version 15.0 (15A240d) via App Store. My test device is now running iOS 17.0, with Beta Update disabled. I will try updating it to 17.0.1 and see if that changes anything...

Alas... still not showing on iOS 17.0.1 :(

Thank you so much @melsam. I really appreciate the help. It's good to know that not everyone is experiencing the same issue... there is hope for me yet!

I tried removing all the rules and donations in one of my TestFlight builds and - alas - they were still not showing. :'(

Thank you for the suggestion. I have confirmed our project scheme, build configuration settings (no differences between Debug & Release), installed fresh installs on multiple devices (as well as updated from existing versions), tried on iOS 17 beta & 17.0 & 17.0.1, toggled Low Power Mode, tested in English & French, tested in US & Canada region... No sign of TipKit :(

Thank you for the update! Very appreciated. :)

@Claude31 I am so sorry I did not see this response/suggestion sooner! Thank you so much. 100% calculating offset will always be the trickiest part here, especially if sometimes it can be on multiple lines given accessibility font sizes or localization (I am adding French support ASAP 😉). I was trying to get this working with a Grid but again without knowing the width of the GridItem it's hard to get the spacing correct... oh well!

Hi @Konsti_x08. We are also running into this same issue but considering we have our App translated in 14 languages we are also sad to have to do this manual work each time. Would it please be possible to confirm how you are calling these pluralized strings at the call site? Are you using NSLocalizedString or have you found a way to use String(localized: or another solution ? Thank you!