recovery fails with cannot read property message

[mruddy]

Using the Chrome extension (downloaded from the chrome store today), I wipe the Trezor and then attempt to run the recovery.

Every time, without regard to the input values, I receive a "Cannot read property 'name' of undefined" message when I click continue (see screenshot). This is easiest to reproduce when the PIN protection is unchecked because then you don't have to enter a PIN to get the failure.

["log","Mon, 09 Jan 2017 02:08:23 GMT","[trezor] Sending","RecoveryDevice",{"pin_protection":false,"word_count":24,"enforce_wordlist":true}]
["log","Mon, 09 Jan 2017 02:08:23 GMT","[trezor.js event session] send : ","RecoveryDevice",{"pin_protection":false,"word_count":24,"enforce_wordlist":true}]
["error","Mon, 09 Jan 2017 02:08:24 GMT","[trezor] Error received",{"type":"error","message":"Cannot read property 'name' of undefined"}]
["log","Mon, 09 Jan 2017 02:08:24 GMT","[trezord] Received error",{}]
["log","Mon, 09 Jan 2017 02:08:24 GMT","[trezor.js event session] error : ",{}]

Google Chrome Version 55.0.2883.87 (64-bit)
Ubuntu 16.04.1 LTS
1.4.0 Trezor firmware

[karelbilek]

ACK

will look at it

[karelbilek]

It was a bug in the code handling protobuf=>JSON conversion. I have fixed this and will push to chrome store soon :)

[mruddy]

cool, thanks for figuring it out. i'll be sure to test it after it's available.

[karelbilek]

Pushed on chrome store.... It should be online in an hour or so

…

On Jan 11, 2017 1:01 PM, "mruddy" ***@***.***> wrote: cool, thanks for figuring it out. i'll be sure to test it after it's available. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGZ8XKiku7vfFud9l7D6RrxIYf8tYsZks5rRMSEgaJpZM4Ld4vV> .

[mruddy]

Excellent, thanks. I've just verified that version 1.2.4 of the extension from the chrome store fixes this issue.
I had to remove and re-install the extension since the chrome store did not seem to have an auto-update. That's probably typical, I've just never used the chrome store before.

[karelbilek]

I never figured out how exactly does Chrome update the extensions ; it usually takes a while to get to all users.

…

On Jan 11, 2017 3:55 PM, "mruddy" ***@***.***> wrote: Excellent, thanks. I've just verified that version 1.2.4 of the extension from the chrome store fixes this issue. I had to remove and re-install the extension since the chrome store did not seem to have an auto-update. That's probably typical, I've just never used the chrome store before. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGZ8Se6cPXI8drds7zQ8rwEeNjKjwvaks5rRO1OgaJpZM4Ld4vV> .