-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to restore extensions from a clone to a rebuilt macOS machine? #6791
Comments
Did you figure this out @jtheletter ? |
I didn't find a solution, and now, eleven days later, I have my primary machine back from hardware repairs, with its data thankfully fully intact. I would still consider the need to export/import or sync of browser extensions to be a critical issue for any web browser. Apple's Migration Assistant and Time Machine are too limited in my experience, so I always end up rebuilding my machines from clones. |
Good question, @jtheletter - the extensions themselves can be seen at But if your profile gets corrupted, they may not be shown there. Glad you got your situation sorted, but you bring about a good point with the extension sync. Let me see if we have an issue tracking that |
@jtheletter we have an issue here, if you want to give it a +1 - this is for enabling extension sync for Brave: #4094 |
OK I believe I found where you can see the extensions... this would be in the Profile directory for your platform (ex: In there, you can see the You can then do a search for that ID on the Chrome Web Store and re-add the extension: |
Thanks for your reply. Nothing showed in The I've upvoted the linked ticket. Cheers. |
@bsclifton I just wanted to thank you, your solution helped me get my extensions back after a Time Machine restore did not recover them automatically. Found the JSON file in the stated location in the backup and looked up each id in the Chrome extensions store. Thanks! |
Super glad to hear, @nhuesmann 😄 Thanks for confirming this worked great. Hope the rest of the Time Machine restore went OK 😄 |
I had this issue recently too. I was migrating from one mac to another using the Migration Assistant. All of my other apps migrated properly, but Brave migrated without its extensions and I don't know why. I had to migrate to another machine about a week later and had the same issue. It was really annoying. |
A one liner for opening previously installed extensions in Chrome Web Store, so that one can easily add them to Brave. cat "$HOME/Library/Application Support/BraveSoftware/Brave-Browser/Default/Preferences" \
| jq -r '.extensions.toolbar[]' \
| xargs -L1 -I{} open -a Brave\ Browser 'https://chrome.google.com/webstore/detail/{}' Needs |
The above returns this for me:
This no longer works with newer versions of Brave it seems...I got the command to run using the following (below) but it's still broken and I haven't the time to mess with this because of some totally avoidable overreaching stupid default behavior by Brave. Brave is TOO HELPFUL in a very annoying and time wasting fashion, when someone migrates from one Mac to another using Migration Assistant Brave thinks it's doing someone a favor by "detecting changes" and unilaterally removing/resetting all or some of the Brave settings and removing all of your extensions from functioning. This is ridiculous default behavior and should NOT be happening without at least asking the user if they wish to proceed with resetting anything and killing previously installed extensions.
|
yes it works |
I have a clone on an external drive of my primary machine, presently in for repairs. I copied all user library files from the clone to my rebuild. Upon launching Brave, I get a prompt reading…
…And all items disappear from
~/Library/Application Support/BraveSoftware/Brave-Browser/Default/Extensions
.I see my name and icon under menubar "Profiles". I see my old/primary device under
brave://sync/
(and it's described as "this device").How do I restore my extensions? How even do I find at least a text or GUI list of my extensions to reinstall manually?
The text was updated successfully, but these errors were encountered: