calendar

I've tried to write a test to further isolate the issue to the formatter. func testGivenFixedFormatDateAssertComponents() throws { var calendar: Calendar = Calendar(identifier: .gregorian) calendar.timeZone = TimeZone(identifier: UTC)! let dateComponents = DateComponents(calendar: calendar, year: 2023, month: 3, day: 8, hour: 12, minute: 10) let given = 08/03/2023 12:10 let actual = try DateFormatter.date(string: given) let expected = try XCTUnwrap(dateComponents.date) XCTAssertEqual(actual, expected) ///XCTAssertEqual failed: (2023-03-08 17:10:00 +0000) is not equal to (2023-03-08 12:10:00 +0000) }

I now had a chance to make the suggested code changes and test this again. Unfortunately, this hasn't solved the issue. Here is the new code: extension Date { /// Creates a `user-visible` date string with the given `template` for the given `locale` using the given `dateFormatter`. Effectively, this gives you 3 benefits: /// /// * You don't need to compute/guess the appropriate date format for every locale /// * You are guaranteed to always format a date that is localised to the user's locale /// * You respect user's preference on how to format a date /// /// The default arguments allow you to to create a `user-visible` date string that is localised to the user's current locale. /// /// Alternatively, use this method to create the correct date string for the given locale. e.g. /// /// Given a `template` of `yMMMMd` to create a `user-visible` date string that includes the year, full name of the month and day of the month for a `en_GB` locale, the string returned for a date representing April 1st in 1974 will be

Google calendar might take some time to sync the change. After doing this, try refreshing the phone calendar and then the Mac calendar. If after some time the change does not sync, please file a feedback request so we can investigate if this is a bug.

Try doing a GET HTTP request on the URL. It should send back an ICS file containing the events for the calendar. You could then parse this to find the events in the calendar. There's no EventKit api to parse an ICS file or to resolve an iCal URL to EventKit objects.

Any app using your library must provide the usage description string. There's no way around this. That's because malicious frameworks could otherwise provide a usage description and get access to calendar information without the app using the framework ever knowing. Note that on more recent versions of the OS the usage description string names have changed: TN3152: Migrating to the latest Calendar access levels | Apple Developer Documentation

There were some changes in UIDatePicker in iOS 16 with respect to how Calendar and Timezones are handled; if you find unexpected behavior, please send us a feedback through Feedback Assistant and attach a sample project to allow us to investigate it.

Make a note to post actual code, never pictures of code - you aren’t going to get many replies when people have to type in your script or debug formatting errors from the text recognition framework. The error is from trying to use Reminders to get the start date of a Calendar event. You need to target the appropriate application to use its terminology, for example: -- Set the names of your calendar and reminders set calendarName to appts set remindersName to appts -- Get the current date and time set currentDate to current date -- Get the events from the calendar tell application Calendar set calendarEvents to every event of calendar calendarName whose start date is greater than currentDate repeat with theEvent in calendarEvents set eventTitle to summary of theEvent set eventStartDate to start date of theEvent set eventNotes to description of theEvent if eventNotes is missing value then set eventNotes to (no notes) -- Create a new reminder with the event details te

After scouring the internet to see whether I could discover a solution with better key words, such as [Binding and NSView], I noticed a quote posted more than five years ago, stating the following: Since KVC and KVO are built on the Objective-C runtime, and since Cocoa Bindings is built on top of KVC and KVO, any properties you want to use Cocoa Bindings with need to be exposed to Objective-C. At the bare minimum, that means adding @objc to the declaration. So, my original [Date] property was set to: var currentTime: Date? I changed the [Date] property to: @objc var currentTime: Date? The application did not crash, but did not show the [Clock and the Calendar] updating. Further reading stated: However, if the property can be changed at runtime, there's an additional hurdle you need to jump through; you need to make sure that the KVO notifications will fire whenever the property's setter is called. Apple's implementation of KVO will use Objective-C magic to automatically add the needed notifications t

There is no supported way to open that specific Settings page [1]. However, if you go to your app’s own Settings page then the Calendar switch shows up there as well. Your app can open its own settings using UIApplicationOpenURLOptionsKey. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Or any other Settings page for that matter. See this post.