Brave-browser: [Desktop] Import data and settings from another Brave channel

Created on 30 Sep 2018  路  12Comments  路  Source: brave/brave-browser

Description


Dev/Beta are not listed in import bookmark settings

Steps to Reproduce

  1. Install dev build
  2. Install beta build as well
  3. Open bookmark importer, only lists legacy browser-laptop as Brave, no option to import from Dev->Beta or Beta ->Dev (unlikely being done)

Actual result:


Dev/Beta are not listed in import bookmark settings

Expected result:

Should be able to import bookmarks and stats from other channel install. Needed for 1.0 when users want to migrate from Beta to Release builds

Reproduces how often:


Easy

Brave version (chrome://version info)


All

Reproducible on current release:


N/A

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields?
  • Is the issue reproducible on the latest version of Chrome?

Additional Information


cc: @bbondy @bsclifton

ODesktop featurimporter prioritP5

Most helpful comment

We don't want to discourage people from trying out Beta/Dev and if this isn't fixed, people who switch will essentially be committing themselves to always using the beta/dev browser.

All 12 comments

Manual work-around until the issue is fixed:
Copy your profile directory over the other one. For example, if you wanted to use your Dev profile for the Beta version, you'd do the following on macOS:

cp -rp ~/Library/Application\ Support/BraveSoftware/Brave-Browser-Dev ~/Library/Application\ Support/BraveSoftware/Brave-Browser-Beta/

Windows and Linux would be similar- but the paths would be different. I believe Windows is at %APPDATA%\BraveSoftware\Brave-Browser-Dev and Linux is at ~/.config/BraveSoftware/Brave-Browser-Dev

Just a heads up if using the workaround mentioned by @bsclifton. It's entirely possible that moving around profiles to different channels might cause some issues. I've moved my personal profile between dev, beta and release several times and eventually bricked the entire Rewards feature. It's entirely possible that sometimes one version of Brave might receive an update and change the structure of several files while other versions are still not aware of this change. So moving a profile with these changes to a channel that doesn't understand those changes could lead to issues.

So be warned! It's possible to manually move profiles around the different channels but it could lead to some really bad issues.

+1 from @TontyTon via #2938

We don't want to discourage people from trying out Beta/Dev and if this isn't fixed, people who switch will essentially be committing themselves to always using the beta/dev browser.

@bsclifton could I have this issue?

@CalebRotello absolutely 馃槃 I've done quite a bit of work on related items in the past. Let me know if you have questions

@bsclifton I am having a difficult time tracking down where brave sends the browser profiles (browser and its bookmark/user data) to the chromium engine. Could you point me in the right direction?

@CalebRotello you might start by checking out our Chrome import, which the Brave import would be similar to:
https://github.com/brave/brave-core/blob/master/utility/importer/chrome_importer.cc

Since you'd need to add a new type of import in the drop down, you might use this PR as a reference. We allow users to import from the old Electron/Muon based version of Brave. The PR shows how to alter the dialog to have a new import type and then create the basic classes
https://github.com/brave/brave-core/pull/185

Just ran into the need for this, to move back to Brave stable/official from Brave dev.. is this still in progress?

cc: @rebron should we bump up priority on this (P4?)

i saw a promo to switch to the beta channel on brave community

Was this page helpful?
0 / 5 - 0 ratings