Tested on Windows 10/11 Pre-Blueprint Attune setup To workaround this, we create a scheduled task to run the installer, it then behaves as the normal user, and installs the browser to the correct place. But we found that running the intaller directly with Attune(WinRM protocol), the actual privilege of the running session is Administrators rather than the normal user we're using, thus the browser is installed in the System Profile directory, which can't be accessed later by the user.
We use the StandaloneSilentSetup installer, to prevent user interaction during the installation. In this blueprint, we download and run the installer, delete the installer package, then remove Brave update services(disable automatic update). Brave is a privacy-focused browser, which automatically blocks online advertisements and website trackers in its default settings. based on the Chromium web browser, which Chrome is based on as well. For example:* exact device/version of Android* which version of Brave are you on that's causing the issue (take a look within GPS)* was there anything enabled via `brave://flags` manually* was Rewards or any other features enabled?Īpologies for anyone that's experiencing an issue and we'll try our best to get this fixed ASAP and push out a hotfix.Using Attune to install Brave Browser on Win10/Win11īrave is a free and open-source web browser developed by Brave Software, Inc. This also fixed a start up crash for users on `Android 12` and a start up crash via the initial onboarding experience if the network was completely disabled.įor the time being, reporting as much information as possible is always helpful. 69) - a minor chromium that upgrades `C95` to `.69`. Usually major chromium bumps carry a lot of risk of introducing issues/crashes/regressions.ġ.31.x - Release #2 (1.31.88 Chromium. My guess is that our issue was released within this release. 54) - major release that updated chromium from `C94` -> `C95`. 81) - this release included a minor chromium 94 bump and a few ad notification fixes.ġ.31.x - Release (1.31.87 Chromium.
Quick summary of the releases/updates:ġ.30.x - Release #3 (1.30.89 Chromium. Unfortunately due to some lag time in the Android review process, we ended up in a situation were we released three updates within ~2 days so we're looking into which of these releases introduced the problem. We've halted upgrades for the time being until we know more and can get a fix out ASAP. I just wanted to let everyone know that we're aware of all the issues that are being reported and are currently investigating and trying to narrow down the problem/cause.
0 kommentar(er)
