[META]? Crash - latest "Stable" release unstable!

[kaduvert]

So there is a bug in the latest stable release, which i will describe later.
I suspect it has already been fixed though, but i refuse to try to find out because i do not want to risk having my main phone fucked by some unstable microg release.

I also refuse to be called a pointless issue opener, so there is definitely a problem: There should either be a recent stable version containing a fix, or, probably easier to do, a patch to the current stable version with a fix.

I don't know how impactful it is if microg crashes in the background, but it just doesn't feel right.
I get notified via LogFox with root whenever anything on my phone crashes, and i see this crash about every few days when i pick up my phone from standby. it has occured 117 times from February 2024 to today

Now to the actual Bug Report (which may be redundant as outlined above):

FATAL EXCEPTION: main
Process: com.google.android.gms, PID: 30869
java.lang.NullPointerException: Attempt to read from field 'byte[] com.android.volley.NetworkResponse.data' on a null object reference in method 'void org.microg.gms.auth.appcert.AppCertManager$fetchDeviceKey$2$1.deliverError(com.android.volley.VolleyError)'
	at org.microg.gms.auth.appcert.AppCertManager$fetchDeviceKey$2$1.deliverError(AppCertManager.kt:113)
	at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:104)
	at android.os.Handler.handleCallback(Handler.java:959)
	at android.os.Handler.dispatchMessage(Handler.java:100)
	at android.os.Looper.loopOnce(Looper.java:232)
	at android.os.Looper.loop(Looper.java:317)
	at android.app.ActivityThread.main(ActivityThread.java:8592)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:878)

this occurs on my sargo phone running lineage-21.0-20240716-microG-sargo from https://lineage.microg.org/ with magisk running microG v0.2.27.223616 (the latest stable release, purposefully NOT unstable or nightly because of reasons outlined above)

it occurs without interaction (while phone is in standby mode) and i theorize it could have to do with internet connectivity, occuring when there is bad / no connection. just guessing though