I have the same problem. Before this happens, The review popped up is kinda annoying when in development. In recent days, I do not see the pop up and thought my code is wrong. Yes, the review request was working fine before, but it doesn't work recently. I think it is Ventura-specific issue as well.

I ran into this problem as well. Here is what I found that helps me fix this issue. Make you your iphone and apple watch are unlocked Connect your iphone to your Mac Open Xcode It is important that Xcode is not opened before (1) and (2). This is just from me experience, I have no other explanations.... Hope it might help.

I have a similar problem on real devices. When I edit complications on Apple Watch, it works fine. I can see my widget preview when selecting what complication I want to add to watch face. But, in the watch app on iPhone, the complication preview is blank on My Faces. But when I tap into individual face, I can see my widget complications. However, the information on my widget complication is wrong. It's supposed to be information from my snapshot but it's not. Very buggy indeed.

I'm also experiencing this problem on my mac catalyst app. This problem didn't happen before.... it started to happen about 3-4 months ago. Interestingly, it happens to some of my views but I still cannot figure out what causes it.

Update! It is working as expected as of May 2023. My Settings: Mac Ventura 13.3.1(a) Xcode 14.3 Works on both real device and simulator with iOS16.4. Now we can get back to work. lol

Same here and still couldn't figure it out. But...if I wait for hours (not more than 24 hrs), and restart my Apple Watch few times, the widget finally reads correct data from userDefaults. Here what I got. When I first install app on Apple Watch, in the AW app itself I can see correct data in userDefaults that are sent from iPhone. This is working right away. But, when the widget renders, it does not use the latest updated data in userDefaults. It uses default value in userDefaults. (the values that I initialize it with) Now... I have to wait for hours, with a help of free restart the Apple Watch. Once the widget renders correctly, that is it using the latest updated data from userDefaults, it will continue to use this. Subsequent widget rendering will have no issue. userDefaults in Apple Watch's app and the widgets are the same. Still don't know how to fix this.. Right now I just advice users to wait.....

I have experienced the same. widgets on watchOS won't use latest data in userDefaults. Even though the AW's app itself uses the latest data in userDefaults. However, from my experience, if I wait for hours (but not more than 24 hours.) the widget uses correct latest data from userDefaults. And subsequent widget rendering will also use latest data in userDefaults. Can anyone confirm that if you wait for says 4-5 hours or overnight, the widget will read correct data?

I have similar problem. Just happen to me on iOS 17.0.3 and macOS Sonoma. I have an incident where calendar full access permission is granted in Settings>Privacy, but in the app it says No calendar access (status NotDeterminded). But I mean... in the Settings app it is clear that the permission is granted. I thought once the permission is granted, no matter what my code does or if there is any error in my code, the Full Access Permission should stay the same, no?

Problem fixed. Well..... Not sure if this is the cause of this problem but after applying this fix I don't see this error anymore.. It turns out that I have error in accessing EKEventStore. Xcode gives me this error: "Client tried to open too many connections to calaccessd. Refusing to open another." In my app, I have carelessly initialized EKEventStore() many times. While this had no problem in iOS16, it caused me the above error in iOS17 let eventStore = EKEventStore() The fix is to create a new class like this: class EventStoreManager: ObservableObject { static let shared = EventStoreManager() let eventStore: EKEventStore private init() { eventStore = EKEventStore() } } Then when I want to access the EKEventStore either in View Struct or function, do this: let eventStore = EventStoreManager.shared.eventStore After doing this I have no error from Xcode anymore. And no issue with access to EKEventStore. Hope this might help.

I don't know the reason why but #available(iOSApplicationExtension 17.0, macOSApplicationExtension 14.0, *) doesn't work for me. Well, it sometimes works sometimes doesn't work. By 'Work' I mean the widgets get refreshed correctly. I have to change it to #available(iOS 17, macCatalyst 17, *) And it works like a charm.

I experience the same. I think it is a bug because it used to be working fine prior to watchOS10. I have also tested a few of third party widgets and they have the same problem - not redacted when not worn. Only Apple's own widgets like calendar seems to be working just fine though.

I have the same issue. Using Version 15.0.1 (15A507) I have both iOS and macOS version. The macOS version went through fine. Only iOS faces this issue.

I have the same problem. I use English as as my development language and set it as base language. Then I localize into Japanese with String Catalog in Xcode 15. I also localize the plist file and it works just fine as well. I don't know why it shows 0 Files Localized for both English and Japanese. But the app works just fine. Even the one I download from Live App Store still provides the two languages. But on App Store it displays only Japanese like this. Looking for answer.

In the same place you set Localization Prefers String Catalogs. Have you enabled Use Compiler to Extract Swift Strings? And you need to build your project in order for the text to be displayed in the catalog.

Problem fixed. Well..... Not sure if this is the cause of this problem but after applying this fix I don't see this error anymore.. It turns out that I have error in accessing EKEventStore. Xcode gives me this error: "Client tried to open too many connections to calaccessd. Refusing to open another." In my app, I have carelessly initialized EKEventStore() many times. While this had no problem in iOS16, it caused me the above error in iOS17 let eventStore = EKEventStore() The fix is to create a new class like this: class EventStoreManager: ObservableObject { static let shared = EventStoreManager() let eventStore: EKEventStore private init() { eventStore = EKEventStore() } } Then when I want to access the EKEventStore either in View Struct or function, do this: let eventStore = EventStoreManager.shared.eventStore After doing this I have no error from Xcode anymore. And no issue with access to EKEventStore. Hope this might help.