And our devices are Global (LE2125)...
I brought that first one I MSM'd back all the way back to 1/10/23 LOS 20 using the upgrade path I'd outlined previously (MSM -> 126.96.36.199 -> LOS 18.1 -> 19.1 -> 20.0 ) with a full data wipe from recovery immediately prior to each LineageOS install (18.1) or upgrade (19.1, 20), and manual config of cert store and app install/config of preferred email client. I ran into one problem while setting up user certs in the cert store, cleared all credentials and rebooted, then got them (our CA cert, my mail client cert, and adaway self-signed cert) added back.
Within a few hours of that yesterday I had my first SSL "cert required" error message in FairEmail where it was not able to read the configured client cert from the store to present it to the server.
So I am at a loss here, no idea what else to do or try. "I guess the f***in' thing is broken" (My Cousin Vinny) comes to mind.
If someone who has seen these kinds of problems with the "fragility" of the user certs/cert store in Android 13/LOS20, as I and others have described in this topic, has a specific path from MSM to LOS20 that they followed which got them there with stable user cert behavior, please share the exact path you followed (which firmware upgrades applied etc. too) and I will follow that and see if I can reproduce as well.
EDIT: I see that what looks to be the latest full A12 OTA for LE15AA / LE2125 available on the XDA OP9Pro OTA repository topic is LE2125_11_C.65. (C66 seems to be there for EU)
So would another possible valid upgrade path be:
MSM -> 188.8.131.52 OTA manual .zip in updater -> 11_C.65 OTA manual .zip in updater -> Lineage OS 20 *install* ?
or maybe even just:
MSM -> 11_C.65 -> Lineage OS 20 install?
And if so, what are chances that my phones are any different with wiped data along the way when I land in LOS20 if I did that instead of 184.108.40.206 -> 220.127.116.11 -> LOS18.1 install -> 19.1 upgrade -> 20 upgrade?
If there IS a difference somehow based on how we got to 20 it would be good to figure out what/why.
In case it matters I am magisk rooted as well, using the method most recommend/follow - boot from adb bootloader with patched boot image , install magisk 25206 apk, direct install method in magisk to patch the stock LOS boot image (and get a restorable unrooted image), reboot, reboot into adb sideload and sideload the magisk apk again as .zip (symlink with .zip extension to the apk comes in handy...) to get the addon.d mod. (Rooting not done until after all updates/upgrades completed...)