Fixes #10494. (maybe) To quote @mzorz from the previous PR:

This is a tricky issue.

@mzorz did a great job explaining the issue in both the original issue and its PR and for quite a while I couldn't even come up with a theory for how we were still having this crash. Now, I have a theory, but it might be a stupid one and a little far fetched. What if the issue is related to Sentry setup?

When we enable the crash logging Sentry might be accessing methods from android.webkit which means we won't have the WebView data directory suffix setup before it. I am not sure how best we can check if that's the case, but I think it's reasonable for Sentry to setup network stuff since they need to send the crash reports.

Now the tricky bit is that, if we make the suggested change in this PR and the app crashes in setWebViewDataDirectorySuffixOnAndroidP we won't be aware of it and related crash reports might disappear. I feel it's very unlikely for that to be the cause of this crash or to result in a crash itself, but it's a risk we'd have to take.

It'd be great to get opinions of a few people for this. What do you think @mzorz @maxme @jkmassel ?

To test:

• Make sure the app builds and runs OK since we don't know how to reproduce the issue.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.