Import of Keepass xml is not working

[NickLittleNZ]

Hi Denis,

I've found the cause of KeePass XML import failure, at least in my case.

After redacting a file to PM to you, I found that it unexpectedly imported! 

As I'd only redacted usernames, passwords, and note fields it was a matter of working through those in isolation to find the issue.

With a bit of trial/error, I've found that the import failure occurs when a username value is strictly numeric, with no letters or symbols in it.

So, for example, the username value of "12345678" doesn't work, but "A12345678" or "#12345678" does.

This should be a quick and simple development fix? Someone is reading the username value as an integer or similar instead of a string in their import code?

Edit: Also found that any custom text fields in KeePass that might contain numeric only values (same as username field) cause problems as well...

Cheers,

Nick

[packetguy]

Hey NickLittleNZ,

I tested it with a test database and youre right.

I am bedazzled that Lastpass Support does not know this, keep me waiting for weeks and ask me for my Keepass XML with potential sensitive data.

If they do not fix this in a timely manner they lost a (Business) customer.

I will update my support case with this information and see what the response is gonna be from Tech Support.

[denis_]

Hi,

Thank you for the valuable feedback. It's much appreciated. I passed it on to the team. They were able to reproduce the issue and are working to solve it.

I'll let you know as soon as I have any update regarding a release date. 

[denis_]

Hi @NickLittleNZ ,

The team is making progress, we identified an issue related to usernames starting with a number that the team is currently working on (link). 

I'll let you know as soon as I have any update regarding a release date. 

[packetguy]

Like NickLittleNZ mentioned the issue is not only with usernames starting with a number but also with custom text fields starting with a number. (See below)

[packetguy]

Also when importing a Keepass XML with only numbers in username or custom field in my Lastpass for normal consumers it works without any problems.

How is this possible? It seems the import feature is different for Lastpass Consumers vs Business/Enterprise customers. (See Below)

Please explain this.

Lastpass Normal Consumers import screen: (Working as it should)

Lastpass Business/Enterprise import screen: (Not working due to bug in Lastpass)

[denis_]

Hi @packetguy 

Thank you for the feedback. The team is working to fix for all the fields.

The new import experience is currently rolled out to English users. As your consumer user language is not set to English, you are getting the old experience, as opposed to the Business user that uses English and hence gets the new experience that unfortunately has an issue currently. 

[packetguy]

Thank you denis_  for the update on the issue and the clarification of the different import experiences.

I will be waiting for a new update from you when there is one.

[sunike98]

Hi @denis_ 

Is this issue still ongoing?
I'm trying to import all my passwords to a fresh LastPass account from a KeePass xml and I'm waiting hours for review and import phase to show me something.

The three dots just keep loading.

[denis_]

Hi @sunike98,

The fix is still under way. Unfortunately I don't have an ETA for you at this moment. I'll follow-up here as soon as I have an update. 

Thank you for your patience.