calendar

Seattle and SF are in the same time zone, so why would they have different timezoneOffset values? Also, what does -29359 even mean? It translates to -8.1527… hours, which isn’t a meaningful time zone offset. Since you are curious, this is an app I started developing in 2011, and it was beleaguered with every imaginable edge case with regard to time zones and daylight saving time. My app is all about converting solar time to whatever time zone you want to look at sometime from, in whatever calendar, in any time past or present, which often involves crossing every possible arbitrary human-made boundary in time and space. Being able to create a standardized time zone based on the location (converted to seconds from GMT), allowed me to do certain data conversions to get the day without having to worry about whether or not daylight saving was in effect at one calendar date but not another that the date picker might choose. And it worked fine for many years until the latest iOS. Presumably Apple h

When querying the data, we do not receive a response, and the code enters an infinite loading state without completing the request. Assuming that you meant your initialResultsHandler was never triggered after your query was executed (healthStore.execute(query)), I believe that's a HealthKit bug because, in any case, HKStatisticsCollectionQuery should call the initial results handler after a period of time; if there is an error, it should call the handler with the error. I’d hence suggest that you file a feedback report with a sysdiagnose and share your report ID here for folks to track. For the instructions of how to capture a sysdiagnose, see here. I don't see anything that can work around the issue, but for debugging purpose, I am guessing that the issue may be related to the dataset on the device's HealthKit store. You might check if the following is relevant: The anchor date components. I see that you set anchorComponents.hour to 0. I'd expect that the other components, such as anchorComponents.minute and

Right, so 72 entries is a sort-of limit. That should maybe be mentioned somewhere in the developer documentation to avoid anyone hitting issues. However, as this the Simulator and a development device those limits shouldn't apply. Anyway, thanks, but that still doesn't help. Even if I change the timeline to have just one day of 72 timeline entries (every 20 minutes for 24 hours), the widgets are still out of whack after just a few minutes. Due to the way timers work in SwiftUI, we developers are having to write a ton of fragile code to work around Apple's limited implementation. I want to show my users a countdown timer that has something like 12 days, 13:45:18. If I use the standard Text.init(date, style: .timer) I will get something like 301:45:18. The developer docs show this example: Example output: 2:32 36:59:01 Who in their right mind would ever want to see a countdown of 36 hours 59 minutes 1 second? No one. Users want to see 1 day 12 hours 59 minutes 1 second, or a friendlier 1 day, 12:59:01. And I ca

Same problem for me. Running stable iOS 18.1.1 on an iPhone 14 Pro, and recurring reminders that I've deleted are showing up multiple times a day in Calendar.

@darkpaw the following code is giving me the above error: struct GetIntent: ForegroundContinuableIntent { ... @Parameter var date: Date? ... } ... class MyShortcuts: AppShortcutsProvider { static var appShortcuts: [AppShortcut] { AppShortcut( intent: GetIntent(), phrases: [ Get (.applicationName) for (.date) ], shortTitle: Get, systemImageName: calendar) } }

IOS 18 is the worst update yet, and I hope that the developers at Apple see this and make notes. The most egregious features are definitely the new control panel, emojis and the photo app. I am largely disliking the changes to the control panel: the exit button is WAY too small, and instead of swiping at the bottom to enter the new categories, would it have been difficult to instead have the user swipe left? The format is also incredibly overwhelming—whatever Apple had before was perfectly fine, I’m not sure why they touched it. The new photo app: I’m not sure why everything needs to be in the same page. It’s unnecessary and unneededly clunky. I’m not sure if Apple was going for a ’minimalist aesthetic vibe’, but the new format gives me a migraine. Please revert these changes. And, finally, the new emoji panel. I am also unsure as to why this was messed with: the old one was perfectly fine. The sizing of the emojis needs to go back to how it was before. Right now, I feel like a grandmother with -10 vision try

FWIW when a nasty problem with Exchanged-based calendars from iOS 18 was fixed in 18.1, it was not in the release notes either... but it was still fixed.