In this article:

    Applicable to:

    • Twingate Component: Client–App Store, standalone
    • Platform: macOS

    Overview

    After starting the Twingate client, it appears to login instantly without prompting authentication and there are no resources listed within the dropdown menu. You are also unable to access protected resources.

    Cause

    The described behavior is a symptom of using the App Store version of the client while also having the stand alone client present on the system.

    The stand alone client requires the installation of a system extension which conflicts with the App Store version. In some rare cases the system extension becomes orphaned after an uninstall of the stand alone client.

    If you have uninstalled the stand alone client but are still experiencing this issue, confirm if the system extension is still active and/or enabled by running the following command in terminal.  systemextensionsctl list

    example output with system extension present:

    --- com.apple.system_extension.network_extension
    enabled	active	teamID	bundleID (version)	name	[state]
    *	*	6GX8KVTR9H	com.twingate.macos.tunnelprovider (2023.250/1)	TunnelProvider.macos	[activated enabled]

    Resolution

    Remove the App Store version and only use the stand alone version of the client.

    If you only want to use the App Store version and have an orphaned system extension then the easiest way to remove it is the following :

    1. Install the stand alone client again. This will terminate the orphaned system extension when it installs a new one. Afterwards you can remove stand alone client again which should remove the new system extension along with it. We recommend using the drag/drop to trashcan method versus using rm -f in terminal.  You can use the systemextensionsctl list command throughout the process to verify that both system extensions were terminated/removed. 

    If you have never had the stand alone client installed and confirmed that the system extension is not present then you are most likely facing a different issue and the solution here is not applicable.