I did have a few unexpected quits with AE the first few times I edited a dynamic link but it seems to have settled down and is stable now.
To date all my CC apps work fine under 10.10 (Pr, AE, Au, AME, Lr, Sg, Ps, Ai, Id, Mu). I hope the development team takes that to heart, because I want Brave to thrive.I had some mission non-critical time to give it a try on my work machine. And for many who won’t realize/discover that they can easily download an older version to restore their access, the feeling will remain. Even a temporary feeling of dread at thinking they’ve lost all their data really undermines a user’s trust in whole Brave brand. If it finds no such version, yet does find later versions incompatible with the system, then it should apologetically notify the user that they won’t be receiving any further updates, warn them of the security risk of continuing to use their current version, and let them take it from there.Īs it is, the software renders itself inoperable in the middle of the night, yanking itself (and their data) out from under users. It should install (or prompt to install) the latest version found that’s compatible with the system. The update mechanism needs to check for compatibility. That is what should not have happened and should not be allowed to happen again. The core problem is that, unlike Chrome and Firefox, Brave blindly installs updates beyond compatibility with the system it’s installed on. That is NOT all that you’ve encountered here. Please do not write off the flack Brave is getting here as a bunch of people with outdated computers whining that they can’t keep using Brave. I’m not one of those users, but reading this thread has shaken my trust in Brave a bit all the same. Thank you for pointing out to the users affected by this blindsiding how they can recover from it. This would make the full command for launching Brave on from the terminal: open -a "Brave browser.app" -args -disable-brave-updateĪgain, please understand that in doing this, you are opening yourself up to potential security risks while browsing and we never recommend using a downgraded version of the browser.
The easiest way to do this would be to launch the browser from the macOS Terminal, adding the -disable-brave-update flag at the end of the command. However, you will also need to disable auto-updates from initiating, or you will run into this problem again. Once installed, the browser should launch as it normally would. Note that doing this will not overwrite any data. Find the file and re-install Brave – you should be installing Brave v1.18.78.Visit our Github and download the previous version of the browser (you’ll want the appropriate.NOTE: Do not delete any other Brave data other than this or you risk losing any browsing data stored on your device. On your OS, go to ~/Library/Applications and move Brave to the Trash.We recommend that users currently on these versions update their OS and Brave version to ensure that they have the latest fixes/securities offered and are fully protected while browsing.įor users who would like to stick with the OS they currently have (10.10.5 or earlier) and still run Brave, you can downgrade to the previous version of the browser by following the steps below: These older versions of macOS are at risk, given that they have not received security updates from Apple for years. This matches the behavior in both Firefox and Chrome, which also no longer support 10.10.5 or earlier. After updating to version 1.19.x, Brave will no longer be compatible with OS X 10.10.5 Yosemite or earlier. I’d like to officially clarify and confirm that we will keep these changes.