Input String Failure

[abraham09]

When trying to import an OPVault File, it fails with the following message:

Input string '26.575424759098905' is not a valid integer. Path 'ps', line 1, position 117.

Using standard settings, etc. The only option is to click ok in the dialogue, afterwhich keepass just hangs and needs to be forced closed through task manager on win 10.

Wondering it it's failing due to a login type, like credit card, account, identity, etc. IPF plugin is also failing with a different message.

[juanii]

Hi! Thank you for using the plugin and taking your time to report the error. From the error message I guessed it's failing because it found a real number where only integers were expected. Luckily it seems it's in a piece of data not used at all, so I could quickly create a new test version which accepts real numbers.

I'd be very grateful if you could please download and try this version and confirm if it works for you. If you want to be check the authenticity of the file the SHA-256 fingerprint is b55e10565e5a12b4c67e887eb8e7164d83d06d96ec9ddb0ccf386eda5ef74f44.

Thanks again

[juanii]

Wondering it it's failing due to a login type, like credit card, account, identity, etc. IPF plugin is also failing with a different message.

If you mean the OnePIF plugin is also failing, feel free to report the bug over there and I'll take a look at it.

Just curious, is it a "new" vault (created in 1Password 6 or 7) or is it an old one that passed through several different versions of 1Password?

Regards

[abraham09]

Thanks for the quick reply, installed the version you posted above and no longer got that error message, instead I am now getting the following:

Year, Month, and Day parameters describe an un-representable DateTime

Regarding the vault, I use 1Password 6 on mac and think it was created with that program rather than being an older one.

I ended up installing KeepassXC on windows and used their native OPVault import feature without any problems to create my kdbx file

[juanii]

Thanks for the quick reply, installed the version you posted above and no longer got that error message, instead I am now getting the following:

Year, Month, and Day parameters describe an un-representable DateTime

Oh I've seen that before and I remember where: the sample OPVault file from AgileBits. I thought it was just a poorly crafted vault so I didn't pay too much attention to fix the bug, but now it seems like there are real vaults out there that have the same problem! I'll certainly take a look at it now. IIRC the problem is with Month/Year fields (not regular date fields) which should be stored as 202005 (for may 2020) but instead the sample vault contained something weird. I used 1Password for a few years and I think I remember something went wrong with those fields in a major update (from 4.x to 5.x?) which broke the data. Maybe it's all related.

Regarding the vault, I use 1Password 6 on mac and think it was created with that program rather than being an older one.

OK, thanks for the tip!

I ended up installing KeepassXC on windows and used their native OPVault import feature without any problems to create my kdbx file

Oh KeePassXC is great, in fact I'm a KeepPassXC user, not KeePass. Just did this plugin to contribute back to the general project. The KeePassXC OPVault importer works like a charm, personally I didn't like the resulting field names/entry arrangement though.

Edit: yeah, here it is, it seems they have longer 15-month years in Canada. I'd advise you to go through your items to check if there's a malformed date, just in case.

Regards