-
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
Rest of Muon import fails after denying keychain access #2513
Labels
Milestone
Comments
Manual testing with a debug build shows the utility process crashes with the following stack trace:
|
18 tasks
garrettr
changed the title
Rest of import fails after denying keychain access
Rest of "Brave (old)" import fails after denying keychain access
Dec 13, 2018
garrettr
changed the title
Rest of "Brave (old)" import fails after denying keychain access
Rest of Muon import fails after denying keychain access
Dec 13, 2018
Verified passed with
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
Separate issue for "Scenario M - Upgrade from muon but then deny keychain access in b-c" from #2438.
Steps to Reproduce
--upgrade-from-muon
command line flag.Actual result:
The following data types ARE imported: History, Bookmarks.
The following ARE NOT imported: Passwords, Cookies, Stats, Rewards, Open windows and tabs.
Expected result:
The following data types SHOULD be imported: History, Bookmarks, Stats, Rewards, Open windows and tabs.
The following data types SHOULD NOT be imported: Passwords, Cookies.
Passwords and Cookies are encrypted with a keychain password on some platforms (macOS, Linux) so if you see a keychain prompt and deny access, you should expect that these data types are not imported because there is no way to decrypt them. However, all other data types should be imported in this scenario.
Reproduces how often:
Easily reproduced.
Brave version (brave://version info)
Reproducible on current release:
Yes
Additional Information
The subset of data types that fail to import when keychain access is denied corresponds to the order of import functions as they are called in
BraveImporter::StartImport
, which suggests that an error in one of the functions that requires keychain access is crashing the importer utility process and thus preventing the rest of the import functions from executing.The text was updated successfully, but these errors were encountered: