I tracked this one down too -- and filed a FB for it. After filing a TSI. The issue seems to be that, for whatever reason, if they are both trying to access the preferences (the VPN manager and the filter manager), it fails. I changed my code to in addition, listen for notifications about changes to the VPN and filter, and when one completed, try the other one if it hadn't been enabled yet.

I eventually tracked this down: one of my @Models had a (Codable) enum in it. I removed that, and it didn't crash. (I may have had to also reset everything programmatically? I forget.)

I wasn't, but I changed it to match what was in the entitlements file, and it still segfaults the same way at the same place.

My current implementation seems to deal with this -- if I get an error during the save preferences, I use dispatch_after for 1 second, and try again.

In practice, I was using completion to do the context.save() so I can deal with workarounds. But it... seems to totally defeat the purpose of @Bindable and requiring a context.save() if you can't get back to an earlier state.

I can do relationships -- but only one level. In my example above, $0.room?.id works, but $0.room?.home?.id does not.

So, if I'm understanding this, #Predicate can not use @Model objects, but only members? (And if a member is itself a @Model object, this recurses infinitely?) (And, on top of that, cannot use any method parameters or struct/class members, but can capture local variables?)

Hm, no, I tried that, and it fails with openssl -- looks like it's trying to compile x86 assembly for arm64 architecture. 😩

Weirdly, although it's still giving me that error, it seems to have activated the packet filter. I still have no idea what's going on there!

It was easy enough to do in CMake, since it has support for processing an input file, and that was so easily done I forgot about it until just now. 😄 (Is there a similar way to do that with the entitlements file in Xcode? I'm thinking not, based on everything.)

For one, I duplicated it in Finder; for the other, I saw that Xcode's File menu had that as well, so did it that way. Then I opened them up in vi and changed them. Then I changed the build settings for the two targets, so that Debug and Release use different entitlement files.

It doesn't appear to be. But! We have two network extensions, and they both show up with the same name, so could that be the problem? If so, how would I ensure that the content filter gets a different configuration name than the transparent proxy provider one?

Ok! Figured it out. This is, however, fairly annoying, but I suspect filing an enhancement request won't go too far. (It didn't help that I've had a bad headache much of today.)

I have never tried to have a different file used in building based on configuration, but I assume that's what I have to do, yeah? Although it turns out I have no idea how to do that for the entitlements file.

And.... after a reboot, it was still not working. Then I went out to go to the immigration office, and when I came back... there were the two Developer IDs I created, and both had private keys now. And now Xcode builds my test app for me. Debug & Release. I am completely flabbergasted Quinn.