Network Extensions regressions introduced in Big Sur dev beta 8

Our app onboarding installs a network extension, and there a two issues:

1) The latest Big Sur Dev beta 8 throws a modal with a new red error sign saying that a system extension has been blocked, while we followed all the steps to install network extensions by the book. It looks like we tried to install malware. Why is this necessary? Didn't the move to user space networking and the sunset of KEXTs also aimed to prevent such error modals?

2) The link in the modal to Open Security Preferences doesn't work: it opens the System preferences but throws a "Preferences Error: There was an error in the Security & Privacy preferences". The user can't even go manually go to that screen to Allow the network extension. The same error is thrown. In our app tech preview phase, about 10-20% of our users faced this issue.

We were days away of releasing our app, and our plans are thrown into uncertainty, again. What are the odds of Apple fixing these P1 issues (for us!) in the late beta stage? It is a very poor first time user experience and we don't have control on that part. We filed feedback for other critical issues but many never received any form acknowledgement. Is it worth posting feedback reports for these ones ?

1) The latest Big Sur Dev beta 8 throws a modal with a new red error
sign saying that a system extension has been blocked …

If you have feedback about the new UI the best way to get the attention of the folks responsible is to file a bug. Please post your bug number, just for the record.

2) The link in the modal to Open Security Preferences doesn't work: it
opens the System preferences but throws a "Preferences Error: There
was an error in the Security & Privacy preferences".

This is a known bug. See this thread.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"
Network Extensions regressions introduced in Big Sur dev beta 8
 
 
Q