Here's the scenario:
This behavior is only exhibited in macOS 10.15.5. We have verified this in builds 19F101 and 19F2200. This does not occur in 10.15.4 or 10.15.6 or 11.0.
This does not occur when developer mode is off, presumably due to the system extension not being replaced.
Was this a known issue/regression that was fixed in 10.15.6?
Thank you
Enable developer mode: sudo systemextensionsctl developer on
Activate a system extension
Check the pid of the running system extension
Activate the same system extension (same version/build) again.
The first instance of the system extension should be set to [terminated waiting to uninstall on reboot]
The second, newer instance of the system extension should be set to [activated enabled]
The pid of the system extension process should have changed
systemextensionsctl list does show both instances of the system extension correctly
However, there is no running process of the system extension. The first instance gets a SIGTERM as expected but the second instance is never started
This behavior is only exhibited in macOS 10.15.5. We have verified this in builds 19F101 and 19F2200. This does not occur in 10.15.4 or 10.15.6 or 11.0.
This does not occur when developer mode is off, presumably due to the system extension not being replaced.
Was this a known issue/regression that was fixed in 10.15.6?
Thank you