Post not yet marked as solved
In the last month or so (probably since the release of iOS 17.2), I've started getting a lot of reports of users losing all their NSUserDefaults as well. I never had a problem with the prewarming stuff from iOS 15 - this is a completely new issue.
Has anyone else been experiencing anything like this on iOS 17? @eskimo - have there been any recent changes to iOS that might affected NSUserDefaults?
How did you manage to archive a build for visionOS? When I archive, it seems to always archive just the iOS version, even though I've added visionOS as a supported destination. When I try to archive for the visionOS simulator, it says "invalid run destination".
Post not yet marked as solved
This appears to be fixed in the 10.1 beta.
Post not yet marked as solved
I ran into this same issue as well. If you update your project to migrate to a single WatchKit target, you should be able to force immediate updates again. Be warned though, the migration introduced a bunch of build errors into my project that took a couple hours for me to fix, and there are other bugs that you will run into that are specific to a single target watch app: ClockKit complications will break and need to be reinstalled, and location updates will fail if you delete then reinstall your watch app. Quite a mess.
Post not yet marked as solved
I am seeing this error all the time now when trying to test purchases on the sandbox. I'm using StoreKit 1. Only started happening in the last few weeks.
Post not yet marked as solved
Any chance this is fixed in watchOS 10.0.1?
I am seeing the same error. Have you filed a feedback with Apple yet?
Post not yet marked as solved
I'm seeing the same thing when trying to output speech to a buffer via writeUtterance:toBufferCallback.
Post not yet marked as solved
Yes, this just started happening for me as well.
Post not yet marked as solved
And now I just got this myself at my home location.
Post not yet marked as solved
I was just able to reproduce this using the following request: /v1/weather/en-US/41.925/-87.64?dataSets=currentWeather,forecastNextHour,forecastHourly,forecastDaily
Tried again a little later and it worked just fine.
Post not yet marked as solved
It seems to always be the same users, but I even tried having them go through a proxy server and they are still getting the error. Whenever I try the same request for the same location, though, it loads just fine. So I'm not really sure what's going on.
Here's one of their requests in case it helps: /v1/weather/en-US/42.047/-96.163?dataSets=currentWeather,forecastNextHour,forecastHourly,forecastDaily
And I submitted this as FB11577100 in case you need the ticket for internal tracking purposes.
Post not yet marked as solved
The API limits definitely haven't been exceeded - I have subscribed for 2m calls per month and have used just 40k of them so far. And calls from other users are going through just fine.
I am seeing the same thing. Works fine without using a token, gives an error when the token is included.
Post not yet marked as solved
I'm seeing the same thing for the Modular Duo face now on the Series 7.
