Import into 1Password from 1PW3 broken in build 4.1b18
Yes
[b]Which devices did this bug appear on and is it reproducible on any devices?[/b]
iPhone 5, iOS 6.0.1, 1PW3.7.2, 1PW4.1b18
[b]A quick summary of the bug:[/b]
The new build 1PW4.1b18 broke the import from 1PW3 version into 1PW4. [u]Earlier builds 4.1b15 and 4.1b17 have no issue with import[/u] from 1PW3 although the process is not consistent (I'll post in a separate topic later). From the recent change log, this may be due to the CFBundleURLSchemes or CFBundleURLName updates made in 4.1b18 regarding the onepassword related URL schemes. A consistent behavior is when 1PW3 opens, it should display the familiar dialog where it detects a 1PW4 version is installed and prompts user to import. 4.1b18 no longer produce this behavior.
[b]Detailed Step-by-step instruction on how to reproduce it:[/b][list=1]
[*]Backup 1PW3 data using 1ptbackup or other methods.
[*]Uninstall/Delete both 1PW3 and 1PW4 apps on iPhone
[*]Install 1PW3.7.2
[*]Open 1PW3, setup Master password and add one or more entries OR simply restore from any 1ptbackup files or from other methods.
[*]Close 1PW3 and force quit this app from background
[*][b]Install 1PW4.1b17[/b]
[*]Open 1PW4, you may see a dialog to upgrade (to 4.1b18 or any higher version) - simply ignore any upgrade for now.
[*]Select 'I've used 1Password before' and Import from old version.
[*]Enter new Master Password for 1PW4 and re-enter the Master Password, skip the Hint view.
[*]You should see a view with 'Get started!' button. Select Get started! button. This should setup a new DB in 1PW4.
[*]1PW3 app is opened automatically - you will be prompted to enter the quick unlock code or master password for 1PW3 - [u]DO NOT unlock yet[/u]
[*][b]Click on iPhone HOME button[/b]
[*][b]Force quit both 1PW3 and 1PW4[/b]
[*]Open 1PW3, enter any Quick unlock code or master password for 1PW3.
[*]Dialog is displayed prompting for Import into 1Password app. Select the button 'Import into new 1Password'.
[*]You will be prompted with 3 options - Open in 1Password, Mail, Copy
[*]Select 'Open in 1Password'
[*]1PW4 app opens at the enter Master Password view - ignore any upgrade option if prompted.
[*]Enter the Master Password of 1PW4.
[*]You should now see a view the Import view. Select the Begin Import button.
[*]All entries from 1PW3 will be imported into 1PW4 (except for trashed items).
[*]Preview the new entries in 1PW4 to verify.
[/list]
Repeat the same steps as above but install [b]1PW4.1b18[/b] instead of 1PW4.1b17 - [b]no dialog is displayed after step 14 and you are stuck without any option to import into 1PW4.[/b]
[b]Workaround[/b][list=1]
[*]Stick with 4.1b17 <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/emoticon-0118-yawn.gif' class='bbc_emoticon' alt='(yawn)' />
[*]Install 4.1b17, import old entries from 1PW3, then upgrade app to 4.1b18.
[/list]
Hope this helps.
Comments
-
Hi @wailam,
I just tested this with the latest 4.2b2 and it seem to be working fine. Can you confirm that it's still broken for you? Also, can you install the official build of 1Password at the App Store and see if it makes any differences?
Here's what it looks like to me when I killed all apps and open 1Password 3 first,
I did both and it imported fine in both the beta and official versions.
Please let me know.
Flag 0 -
Hi @wailam,
Sorry, I meant to post the iPhone screenshot, I tested both to make sure it's not just iPhone.
Here's a video of me doing it, please let me know what I'm doing wrong, I did the first step 14 and this video starts with me killing both apps:
Flag 0 -
Hi Mike
Pls try without having the 1Password app (official) installed. Only install the beta. I suspect since 4.1b17 (last known working beta to support this feature), some location mrtadata was changed causing all future betas to break. I just tried this without any official 1password. 4.1b17 still works and 4.2b4 that breaks.
Hope this helps.
Flag 0 -
Hi,
Looks like the import process won't start if it can't recognize the regular URL scheme but it does recognize both the regular and beta URL schemes if the official build was installed first.
I've filed it as a bug. Unfortunately, this may require an update to 3.7.x series to fix this, which is lower on the priority list. As soon as we finish with the rest of issues in 4.x, we'll take a look in the 3.7.x series to release an update to fix this.
Thanks for your patience on this matter.
Flag 0