Description of the issue:
Unable to check the status of the sandbox after the latest update.
How can this issue be reproduced?
- Type either brave://sandbox or chrome://sandbox
Expected result:
Being able to assess the sandbox status and know if the version I’m using is secure.
Brave Version( check About Brave
):
Brave 1.75.175, Chromium 133.0.6943.54
Mobile Device details
Samsung a35, android 14, original os.
Brave Browser, stable branch, originally downloaded from Google Play.
Additional Information:
I’ve tried downloading the nightly and beta from Google Play with the same result.
Then tried uninstalling and reinstalling, but the error remains. Tried uninstalling and downloading the APK from the github repository, no change.
Reverting to a previous version shows the sandbox, but browsing the web without security fixes is extremely undesireable.
Tried other Chromium browsers with 133, the sandbox is shown.
Am I just supposed to blindly trust that every component in the browser going forward just simply works without being able to confirm/assess?
While I do know using a piece of software or hardware does require trust, and Brave is open source, and my experience so far has been nothing but pleaseant, fridge cases and botched installations can happen.
I see no reason for internal pages to be inaccessible after an update, expecially one as important as the status of a critical security component.
I assume this is not intentional, and forward this issue.
(English is not my first language)