-
Notifications
You must be signed in to change notification settings - Fork 14
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
1Password importer doesn't work with 1Password for Windows 4 #40
Comments
Interesting issue. Why would 1password encode their files differently for different operating systems? That doesn’t make sense.. I suspect there must be something else going on, such as a different vault version or export format update. Nevertheless we need to first figure out why there’s a difference and how we can handle as many potentialities as possible, as you said.. |
@neojp can you possibly create a new 1password vault, with a few sample items and folders, and export it here so we can look further at it? |
Certainly, I will do so later today. Could someone also provide one that works with the current version of the importer? I have started working on a importer for the Windows version. |
This is a quick example that includes multiple URLs, password history, a section of additional fields, and tags.
|
Thanks @neojp! We'll get to it as soon as we can. |
I'm trying to import a 1PIF file from 1Password for Windows 4.6.2.626. There aren't any error messages and the import finishes with a new group named "Imported 1 password archive".
I'm going with the assumption that this is because of the 1PIF exported version of macOS is different and contains additional data that doesn't exist in the Windows version.
Line 22 in the 1password.js looks for
item.typeName
wheretypeName
doesn't exist in my list of items. The code follows to line 23 which looks for a reference to the macOS system.folder which obviously fails again.It all goes downhill from here and the rest of the script fails at importing any of the items in my 1PIF file.
Not sure what the next steps for this issue would be:
Regardless, there probably should be a note in the README saying it only supports macOS.
The text was updated successfully, but these errors were encountered: