whiskeywalrus Does it crash? If it doesn't, I don't see why you'd disable hardening features. But you can simply enable exploit protection compatibility mode.
whiskeywalrus Also why is there no such database to check what others have reported to have caused issues?
Can you imagine the amount of work this would entail? Also:
- Which apps would be in the proposed list?
- How many apps will be on the list? The most commonly used 100?
- How often will apps' info be updated on the list? Monthly? Or every time the app is updated?
- Will the person or people maintaining the list and testing apps test on both profiles with Sandboxed Google Play installed and profiles without Google Play?
- Will a testing device have an account for each profile?
- How much testing will be done? Like will the tester send messages for each one? Look at videos, try to send emojis, stickers, etc. on WhatsApp?
- Will they enable the Play Integrity API or block it?
- Secure app spawning on or off?
- Which hardening things will be documented? Hardened memory allocator? Native code debugging? DCL via memory and/or storage?
- If the database or site relies on external testers, how will an admin of the site verify reports are genuine?
I kind of tried something like you proposed by the way and gave up really fast. It's too much work, honestly, and you have to account for so many different variables. It's far easier to tell people how to troubleshoot issues if they encounter them, and if people have questions about a specific app, they can ask within our community and chances are someone will know whether an app works or not.