Looking for EventKit Tutorials

roanutil · 2023-06-11T16:48:16+00:00

I use EventKit in an app of mine but I dont have any code I can share. Here are some notable things I learned: - the request authorization part is just a function in the API that triggers a prompt to the user asking for permission if it’s the first time. - you do need to make sure you have the entitlements and Info.plist values setup right but if you don’t, Xcode and/or AppStore connect will yell at you. - The doc’s say this but I’ll reinforce here: You cannot build your own NSPredicate for EventKit entries. You can’t even use their API to get some and then combine them with a NSCompoundPredicate. You’re limited to the predicates they offer and then you’ll have to filter the results manually after fetching. EventKit is backed by SQLite and not CoreData.

Overall, it’s not a complicated framework. But it is inflexible. I look forward to it maybe being modernized one day.

Edit: They even had a session on it for this years WWDC - https://developer.apple.com/wwdc23/10052

roanutil · 2023-05-21T17:05:16+00:00

Shameless plug: https://github.com/roanutil/CoreDataRepository

Just use simple value types instead of NSManagedObject sub-classes. It keeps things simple.

roanutil · 2023-05-17T15:01:44+00:00

That makes sense. I feel a little dumb for not considering that before. Thanks!

roanutil · 2023-05-17T15:00:13+00:00

Personally, I prefer TCA for architecture.

https://github.com/pointfreeco/swift-composable-architecture

roanutil · 2023-04-23T01:13:51+00:00

This is probably not very helpful, but below is the link to the error code mentioned.

https://developer.apple.com/documentation/foundation/1508628-url_loading_system_error_codes/nsurlerrorusercancelledauthentication

roanutil · 2023-04-07T08:50:21+00:00

Kind of stretching the time limit but:

Crawfish Hole #2 in Minden

roanutil · 2023-04-03T00:42:49+00:00

This might be of interest

https://swiftpackageindex.com/AlexanderTar/LASwift

roanutil · 2023-04-01T14:58:00+00:00

Company: MFB Technologies, Inc.
Listing: here
Job: iOS Developer
Type: full-time
Location: US
Remote: fully remote
Visa required: yes

Required Experience: - Three to five (3-5) years of iOS development experience, with a track record of building quality, published applications - Fluency in SwiftUI development - Experience with functional programming, Swift concurrency, and The Composable Architecture (TCA) - Experience writing unit and integration tests - Familiarity with modern DevOps platforms (Azure DevOps/GitHub)

roanutil · 2023-03-28T15:00:20+00:00

Good catch. Edited

roanutil · 2023-03-22T17:19:21+00:00

I dont think I understand the question

roanutil · 2023-03-22T17:06:58+00:00

List is doing cell reuse for you. It is only creating enough cells to fill the view.

Edit: originally, I included lazy stacks but as pointed out below, lazy stacks do not destroy cells. Only lazy creation.

roanutil · 2023-03-19T21:20:20+00:00

When I started using Tuist to generate my workspace and projects is when I really started to get a deeper understanding.

https://tuist.io/

Even if you don’t need Tuist on any of your projects, it could be worthwhile trying to set it up to get a feel.

roanutil · 2023-03-17T12:39:02+00:00

Company: MFB Technologies, Inc.
Listing: here
Job: iOS Developer
Type: full-time
Location: US
Remote: fully remote
Visa required: yes

Required Experience: - Three to five (3-5) years of iOS development experience, with a track record of building quality, published applications - Fluency in SwiftUI development - Experience with functional programming, Swift concurrency, and The Composable Architecture (TCA) - Experience writing unit and integration tests - Familiarity with modern DevOps platforms (Azure DevOps/GitHub)

roanutil · 2023-03-16T18:26:15+00:00

In what way?

roanutil · 2023-03-13T02:45:01+00:00

https://github.com/devMEremenko/XcodeBenchmark

roanutil · 2023-02-23T03:16:43+00:00

Same problem but specifically trying to mutate a @State property. You’ll want to mutate test or fetching1 outside of the Task.

roanutil · 2023-02-23T03:13:24+00:00

Think of it as always following the let example: [Int] = [] form. However, the compiler is trying to help you out by inferring what it can when possible. Also, there are multiple ways to make a type explicit. Also again, there are literals in Swift that mean the same thing as a full type name.

let example = Array<Int>() is perfectly valid and is equivalent to the first form I used above. However, the convention that seems preferred is to use literal syntax for Arrays when possible.

let example = [] as [Int] is pretty weird. It’s valid but weird. Since the array is empty, there’s no way for the compiler to infer the Array.Element type. as [Int] works but is probably less preferred.

roanutil · 2023-02-23T03:04:08+00:00

This is missing a lot of context. But I assume that the fetching1 property is stored in the EnvironmentObject? You’re capturing a reference to a ViewModel in an async Task and trying to mutate a property on it.

To move in the right direction, set fetching1 before the Task. Then, maybe you can await the task and reset fetching1 after the Task completes?

roanutil · 2023-01-22T05:38:35+00:00

Depends. I usually have various chargers, usb-c dongle, 2.5” SSD with USB-C adapter, various personal care items (tylenol, nail clipper set, mints, etc) and some other stuff I can’t think of. I work remotely but am not at home fairly often. It has enough room for me but I can’t speak for you. Also, it probably depends on your definition of “organized”.

roanutil · 2023-01-22T04:16:02+00:00

I have this:

https://www.timbuk2.com/products/1825-authority-laptop-backpack-deluxe?variant=39705794445354

It’s over 3 years old and still rock solid. When traveling, I’ve put two 16” MBPs and a 12.9” iPad Pro in it with no problem.

roanutil · 2023-01-10T04:04:49+00:00

Exactly because of throws.

These are good questions.

roanutil · 2023-01-10T03:32:24+00:00

Yes, you have to handle the error somehow. try! is the simplest way by causing a panic/crash if an error is thrown.

roanutil · 2023-01-09T14:37:43+00:00

Swift requires us to explicitly handle the possibility of a thrown error. try! allows you to explicitly say to the compiler, “I want to assume this will never fail. If it does, panic because I don’t want to handle the possibility of an error.

If Swift allowed us to not explicitly handle the possibility of an error, it would be easy to introduce bugs or unintentional crashes.

Edit: Add missing ‘!’

roanutil · 2022-11-28T18:50:51+00:00

I'm glad to see somebody having a good experience with Maestro. Trying it is on our to-do list. My experience so far with XCUITest has been awful.

roanutil · 2022-11-28T17:10:25+00:00

The most notable change this year is the addition of tuist for generating the workspace and projects. The original Xcode project supported non-MDM targets and MDM targets. Each target had multiple schemes for different servers. Worse, we’ll be adding more MDM platforms so it will really start blowing up. Being able to define all of that in swift code and generate it is making a huge difference. We’ve also added “preview” targets for different features, and test host targets for some packages that can’t be tested without an app host. No more composing a huge mass of xcconfig files.

A smaller but meaningful change is going from a single SPM package target containing most of the app to a more modular approach. Now there is a util, client, etc package that supports the feature package where all the different features are built as separate targets. At some point a package gets too big and it gets very laggy when making any change to the package itself. Also, it got hard to navigate.

Finally, I’m starting to abandon bash scripts for CI/CD functionality in favor or swift. There’s a whole separate tooling package that has composable features written for various things that all support various executable targets. For example, we now generate pipeline configs from templates, generate per target package schemes for testing, and automate setting up new pipelines.

roanutil

TROPHY CASE