I'm trying to release an app with this kind of business model right now. Review team is bullying me for my products, asking stupid questions like: "Please explain why free trial period is submitted as separated in-app purchase instead of being included in the paid 'Lifetime Unlock' in-app purchase." So tiresome -_-

Can we attract Apple support to this question?

It's available only as central and can connect up to 2 peripherals. Why this is limited? I don't know.

I wish we had access to that component that's used above keyboard in Safari or Notes.

I found a workaround! Will publish an open source solution when I have time. Please, poke me if you need it.

I had an idea that me and OP have this issue because we use shared App Group container. So I tried this workaround: Copied all fonts from shared container to Documents. Then install them from Documents. It didn't work. I suspect that even if we include fonts to the Bundle, skip UIAppFonts, add them using CTFontManagerRegisterFontsForURL - they will not work. 😔

Hi there! Same problem on WidgetKit complications extension. On Watch Series 10 it doesn't works - complication become blank, on Simulator however it does.

@darkpaw, any luck with this issue?

Test Wow! Looks like I can't delete this post. To mods: could you please enable post editing? I need to delete the .watchface link from the question.

I also have SE2 and constantly get various errors while debugging watchOS apps with Xcode. Connection is very unstable.

Similar issue: // Sending 'center' risks causing data races let granted = try await center.requestAuthorization(options: options) Silenced by using @preconcurrency: @preconcurrency import UserNotifications

I was able to resolve the issue by switching to URL Schema. The tricky part here, is that the schema should contain at least some path components. First I tried schemes like this: myapp-halloween:// And got the error when tried to save the Custom Product Page: ⚠️Your changes could not be saved. Try again later Initially it was unclear at all what's wrong here. I thought that maybe URL Schemes are not acceptable at all, so that's why we tried deeplinks. And got the similar error as OP: on the first attempt deeplink isn't activated even on iOS 18.2.1. But experementally I found that if you add some path components, like: myapp://halloween Then everything works fine. CPP submitted without issues and the scheme opens the app and the URL gets received.

I had the same issue, @SpaceGrey. You solved it by using "All Sizes", I solved it by staying at "Single Size" but replacing JPG with PNG.

@iphonegamedeveloper, any success? I guess if scheme isn't https or http that we can assume it's custom in most cases.

We ended up switching to another backend provider 😢 But I hope one day we will return to CloudKit, as it maturates and gets better.