Trezor connect issue about connect

[andreashuber69]

I've got the same issue, the page https://connect.trezor.io/1/popup/popup.html will just display "Loading..." forever. Tested with Edge, Firefox and Chrome.

[prusnak]

Should be fixed now.

[pbarry]

Same here.

I opened the JS console, and it appears MEW is still using Trezor Connect v1, which Trezor says is no longer maintained. Unless Trezor Connect backports a fix, MEW will probably need to upgrade (I sent them a support request).

Details in case it helps - the specific error message I see in the JS console is:
"Config too old; 1500835774 >= 1500829387" coming from popup/popup-dist.js

The first number keeps incrementing as I retry, and appears to be the current UTC time. The 2nd number stays fixed, and if it's a UTC timestamp, it's currently about 2 hours ago.

[pbarry]

Sorry I posted after your message - it is indeed fixed!

[prusnak]

still using Trezor Connect v1, which Trezor says is no longer maintained.

@pbarry where exactly do we claim that?

[pbarry]

On the README of https://github.com/trezor/connect:

Currently, we are at version 2, which has an url https://connect.trezor.io/2/connect.js. The older version at https://trezor.github.io/connect/connect.js is still working, but not updated.

[pbarry]

I suppose the distinction between "not updated" and "unmaintained" could be open to interpretation.

[prusnak]

Thanks, I changed the wording in readme so it is more clear.

[pbarry]

Thanks so much!

[defcon23]

solved! Thanks

[chrisrico]

@prusnak This seems to be occurring again. Is this something you can fix on your side or does Copay need to be updated to use a newer Connect version?

[karelbilek]

Does it make the same error? Can you copy-paste the error stack in the console. if it occurs?

[prusnak]

@chrisrico could you please try again?

[chrisrico]

Yes, it was the same error Config too old; 1508715774 >= 1508601310. It is fixed now.

When it wasn't working, it could be reproduced on a v1 example.