calendar

I don't know of such API (similar to isDateInYesterday). But it is should be easy to write an extension to Calendar to do it.

Same issue here. Some Macbook air have it working and have had it working. Some other don't. I was wondering if perhaps if you have more than one account that does scheduling, perhaps the Apple calendar, the caldav client has some kind of bug that does not behave as it should... Did you solve the issue?

Is the Calendars app utilizing UICalendarView? I do need to support iOS 15 - so probably can't go that route.

Check out the tab views used in Apples apps: Podcast, Music, Files... Switching between tabs is always instantaneous, by design. Personally I don't think a transition animation between the tabs would add any benefit. It could even get annoying for a user. If you really want to trigger some animation, you could use the onAppear of each tab to build some illusion... but this would mean that your views (within the TabView) would really need to know what view is being drawn left/right of it. I think you will end up writing your own version of TabView, not a good idea. See also the HIG to learn why and when to use tab bars (https://developer.apple.com/design/human-interface-guidelines/tab-bars) in iOS. But if you really need an animation... there is a possible way using the TabView in .page mode. The TabView will take care of the animation and will allow swiping between the screens, but you will have to add the bottom bar with all the buttons to switch between the pages. See the example below. struct ContentView:

The short answer here is that there is no safe way to use DateFormatter with a fixed dateFormat string without pinning the locale to en_US_POSIX. You can spend a bunch of time trying to understand the intricacies of how DateFormatter behaves but what does that buy you? The are two possible conclusions: You are able to find a specific set of parameters that seem to work today. You aren’t. The second conclusion isn’t a problem. You’ll go straight to en_US_POSIX and all will be well [1]. The problem is with the first conclusion. You might be tempted to use those parameters in production code but, if you do that, you’re exposing yourself to future binary compatibility problems. For example, while the en_GB locale currently implies the Gregorian calendar, that could change in the future [2]. If that happens, your code will start reporting dates that are off by roughly 500 years. And while this is not a very realistic possibility, weird stuff like this happens all the time [3] and the only way to protect y

I too am afflicted by this issue that was introduced in iOS 16 . It was not an issue in any operating systems prior. I’ve tried literally every setting Apple has provided and nothing works. I hoped since iOS 16.0 that one of the many eventual version updates would fix this but now we’re on iOS 16.4.1 with zero attention to this massive issue. I’ve turned off the iOS Calendar App toggle for ‘Event Alerts’ & ‘Events Affect Availability’ for every shared Google Calendar I’m subscribed to. And after a minute the iOS turns them all right back on again without any word to me that my settings are being ignored and overwritten. My phone’s battery is now suffering because of this. Many times per day my iPhone will start vibrating with notifications that don’t even pertain to me and it will vibrate for minutes on end. There was a time that it vibrated with Calendar notifications for a hour… using up 25% of my battery. My wife thinks I’m having an affair with another woman because my iPhon

use the newer ISO8601DateFormatter While ISO8601DateFormatter is fab, I always find myself running into problems like the one here, where it’s very slightly out of alignment with the requirements. Maybe that old tech note could use an update to mention ISO8601DateFormatter? QA1480 is in the documentation archive and so I can’t directly update it. Note that the key points from that doc have made it into the modern docs but I like linking to QA1480 because the Buddhist calendar example is a strong motivator. I could replace QA1480 wholesale but I don’t think that’s the right option. After spending years trying to document our way out of this problem my conclusion is that it simply won’t work. The dateFormat property is such an ‘obviously correct’ approach that folks never actually read the docs about it. IMO the path forward here is to deprecate dateFormat (r. 33988168) and replace it with localizedDateFormat and fixedDateFormat, where setting the latter forces the locale. However, that’s just my opini

I can't find out how to show a date picker that lets the user select the date and time. You need to be careful here. Our pickers traditionally work in terms of a Date value but that doesn’t necessarily mean that you should use a Date value in your model. For example, if you store a user’s birthday, you shouldn’t store it as a Date but rather as a DateComponents. That’s because a birthday isn’t an absolute fixed point in time, but rather a date whose time varies based on the context. Given this mismatch, you ofter have to convert between date components and a Date. Do that using Calendar. On the way in, test the the hour component to midday so that you don’t hit this issue touched on in Parsing Dates Without Times. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

hello,after 3 years later,did you fixed it? I’m recently trying to implement an infinite scrollable calendar, the principle is quite the same to yours. And also has the stutter issue when dragging.