Jason Kraft

Results 10 comments of Jason Kraft

#### I can replicate this issue via two paths by doing the following: 1. Add Profile option 2. Shimmer option in "Choose Protocol" view 3. Testnet option in "Choose Network"...

Also happens when restoring a stronghold backup and getting to the "You have successfully recovered your backup message", then going back to the "Setup a Shimmer Profile view". It will...

I've also just tested with Simplified Chinese and Russian, recovering a profile and logging into an already created profile, and I cannot reproduce this issue.

Looks related to #4113, but the operating system and error message are somewhat different. I'm guessing they are affected by the same issue.

@corbo I know that the error text says version 1.6.5, but did you receive this error while using the Firefly Stardust - Beta version and it just reported the version...

Joining all the related issues from the discord: ![image](https://user-images.githubusercontent.com/72045705/182525748-dd143b5f-e359-4e57-b5ca-85801217fb8d.png) ![image](https://user-images.githubusercontent.com/72045705/182526066-338021ff-b873-4e65-9d8a-9f6cfca12f79.png) ![image](https://user-images.githubusercontent.com/72045705/182526394-4696aeb1-ca81-481f-95b7-10138f9254c3.png) ![image](https://user-images.githubusercontent.com/72045705/182525979-d10bfbe5-1a81-4285-af5c-e24f36614dd0.png) ![image](https://user-images.githubusercontent.com/72045705/182525898-1b9941f0-e3e1-41b4-9079-545a511b13c3.png)

Also the error from Linux has the same `Error: node-loader`, but this one is from 1.6.5 FF. ![image](https://user-images.githubusercontent.com/72045705/182526698-07a9da34-69ef-4137-b19e-99167d19718a.png) Worth checking what has changed there too

From what I've seen in other related issues, I thought it might be related to missing local dependencies so I created a fresh Windows profile and installed the Firefly Beta....

Extra info. When moving to the %TEMP% directory and running `node [hash].tmp.node` on the specified file that could not be found from the error message. t00k is affected by this...

Changed to blocked, awaiting next beta release to see if pull #4091 fixes this issue