Awesome! Thank you for sharing the workaround! Did you release it through the App Store?

Great to hear! Thanks for the follow up.

Yes, but App Store Connect doesn't see any purchases "Last Purchase" column is empty. I've found a workaround - I can show "manage subscription" screen on iOS and then I see my purchase, but I wonder if there is anything like that on macOS as not everyone has also iOS app.

Well, it seems like one of those information is outdated because they are contradicting :D. However, I checked and TestFlight purchases on macOS are not connected with my sandbox account, so I guess the note in the App Store is newer. I think in the past this account was used for TF purchases but it's no longer the case. I checked it purchasing a subscription when my sandbox account was set and the purchase did not appear in the App Store Connect next to my sandbox user.

Sandbox account isn't used for TestFlight purchases. If you open App Store -> Settings, you can see a note below the sandbox account: This account will only be used for testing your in-app purchases while developing locally. Your existing App Store account will be used for TestFlight apps.

I don't want to show a dock icon. Also, I think you tested it incorrectly - when you launch a "regular" app, it gets activated automatically, so if you show a new window then - it will be active. Launch the app by clicking on the binary (sometimes Xcode can mess up focus too), focus another app like Finder or Safari and then open a new window from the menu bar. It will appear below other windows even if the activation policy is set to regular. You can test it with my demo app :).

Done :)

Those functions work only on iOS. The same does not apply to macOS.

@t.hackbart I never wait more than 3 days. If the app is still waiting for review, just remove it from review and send a new build.

It seems like they just decided to clean up the queue and auto-approve everyone. My app was also approved within a couple of minutes.

Thank you very much for the advice. I'd love to find the root cause of this problem, so I'll try to get a sysdiagnose the next time it happens. I will also consider migrating the app to a LaunchAgent.

I'm using the latest iOS version. I meant my minimum supported iOS version is 16.

I confirmed on real device that this issue is reproducible using the sample project I included. This is a pretty nasty bug because it means that localization doesn’t work at all for widget configuration intents.

Another thing that proves it's watchOS bug - when you open the same widget configuration intent from Watch app on iOS, it displays texts correctly, but when you open that intent on watchOS it shows either localization keys or default/fallback value if provided.

I created a DTS ticket: 19597420. I think it's watchOS bug, there isn't much you can do wrong here - you just provide a localization key and add it in "xcstrings" file, just like all other translations in the app. And it works in the simulator, but for some reason the real device can't see translations inside the widet configuration intent. Maybe there is something wrong with the "Archive" step and it's not really about simulator vs real device.