Android client stopped to authenticate "subject_token is invalid"

I have been dealing with connectivity issues, and somewhat covered in this thread

I noticed that my android devices were unable to connect, but other tunnels, including new users (on android) connect perfectly.

I arrived here by noticing the subject_token is invalid error line in the controller logs.

I am running GrapheneOS, and I have Ziti Mobile Edge installed directly from GitHub via Obtainium.

Other users are running stock Android, and they exhibit no issues.

I have both the controller and router installed via helm.

I inspected the ConfigMap for the controller, and the OIDC section is blank:

  - binding: edge-oidc
    options: { }

I have been debugging this from every angle, and I am curious if there is something specific about the release directly from GitHub, or using GrapheneOS, or both.

This has been a recent failure, and it is quite maddening.

At this point, I think my upgrading the controller and router was not the issue, and feeling that the upgrade was the issue is a red herring. At the very least, it may have set all of this in motion.

My instinct tells me that it is something about a direct install and/or GrapheneOS.

Why it recently stopped functioning out of nowhere is something I have not been able to deduce.