The task is to document in the Wiki how to test the app in release builds. Try running the tests yourself first, then document it. If you develop any kind of script or add any tips, it would be tremendous.

Mike's description in Discord should help:

1. you'll need to generate the build as release, which requires a keystore configured for signing - you'll need to set one up and remember 1) the location of it, 2) the key alias 3) the store password and 4) the key password

That's a little annoying to set up but it's simply the price of entry for doing app signing

2. release build for androidTest is all turned on / managed by environment variables - set them as we set them in the emulator workflow, but using your values from 1 above

What I do is I have a keystore setup, and I have a little script right next to it that exports all those vars
I should say it's not "easy", because there is some setup, but once you've got the keystore done and a little script that sets the env vars to match the keystore, then it's easy to iterate / do it whenever
That is is testable is kind of amazing, I don't even want to go into the details other than to say that it is kind of a crazy hack, and voczi deserves a lot of the credits, respect for that.

And that it is testable is the only way I was going to turn it on, fearing we'd have problems like what you're looking into in the future - there are always problems. But we can test them and fix them at least. Which unlocks like a 30MB app savings, so...on balance worth it