I have a Chromium based browser published on Play Store few years ago. It has its users base and not a bad rating but recently I've faced a very strange issue. My app update was rejected by Play Store claiming it crashes continuously on its native side during Pre-launch testing.
I've investigated crash logs from Pre-launch test reports, spent a lot of time trying to reproduce the issue and finally found that it's reproducible if I convert an .aab file (required by Play Store to be uploaded) to .apk via bundletool and then install it on the device and run or download a Singned universal APK from Play Console's App bunle explorer section. At the same time both .aab and .apk work fine on my devices and in Firebase test lab, even with the same devices list reported by Pre-launch testing as crashable ones if I upload them directly.
I suggest that the problem is in bundletool itself. It seems like it's not able to extract Chromium native libs properly while converting .aab to .apk
I've reached to Play Store support but got no help from them, only general answers and links. Has anyone faced such an issue? I'm not sure if there anything I could do to continue publishing my app updates.
enable_arm_cfi_table variable in
build/config/compiler/compiler.gni I disabled it and everything went back to normal state. hi,have you figured out a solution to this problem ? we are facing the same issue.