yeah, manual price conversion for all regions is prohibitively time consuming.

If you do not update the ge rating and submit a new version before Jan 31 2025, the next time that you need to update that app it will trigger a "significant change" which presumably a more difficult review process. This is specified at the end of the email that you received from Apple. "Please also note that the Texas SB2420 legislation goes into effect January 1, 2026. Under this law, making an age rating change to apps distributed in Texas would be considered a significant change. If you update your age rating after this date, you may need to trigger the significant change consent process."

What happens if we submit a new version of the app after the deadline and at that time update the Age Rating?

Looks like Apple has fixed the following in watchOS 10.5 beta 4 FB13758450: AppIntent-based widgets no longer render on watchOS 10.5

Thanks you for summarizing this and submitting these reports. I spent half a day on this. I hope they fix this soon because a lot of people install these iOS beta versions and they blame the app developer for the iOS bugs.

I have the same problem. Did you figure out how to address this? I am using Xcode 15.1

This problem seem to exist even under watchOS 10 beta 3. So, since perform() is not called, widgets of watchOS cannot be interactive and they launch the associated watch app.

I am running Xcode 15 beta 3 and iOS 17 beta 3 and this bug still exists Remedy is to comment out the new style preview and add the old style preview. //#Preview { // ContentView() //} struct ContentView_Previews: PreviewProvider { static var previews: some View { ContentView() } }

iOS 17 beta 3 (July 11) still has this problem

BTW, throughout all this time the Apple Server Status website showed no problem related to iCloud. The website also did not indicate any problem when this problem happened last year (and lasted for months) for people who were affected

This is a server side problem and it is an embarrassment for apple not to even acknowledge the problem let alone fixing it. All developer-facing tools are hostile and issues filed using feedback assistant are completely ignored.

It's ridiculous that this issue is still unresolved after several months. People actually use iCloud Drive. If it does not work, Apple should just tell us so that we find other solutions.

Please let me know if you find a solution. I am in the same situation. My app (which uses iCloud Drive) has been working work years but this problem has started affecting some of my users in the past few days.

If you have found a solution for this, can you please post here? This problem is affecting only some of my users and I cannot re-produce it on my side.