jurgelenas

Pinging @CapnBry

It can be solved by catching an exception in your routes.rb file. But if you really want to use it - find exactly which exception you want to catch, because...

But please track the exact Exception which is thrown and post it here for others as I am unable to do it now.

+1

> especially for the 'no-console' rule it seems like console.error() should be allowed and not throw a warning. Console.log() and console.warn() could still throw a warning. Agree on this one....

@Index303, @fanbinjim can you post application logs or at least a full screenshot of the configurator app?

> Thanks,but I've turn back to 1.2.1 Still, can you post application logs over here? This issue might affect other people too

> > ``` > > { > > context: d [FetchError]: request to https://raw.githubusercontent.com/ExpressLRS/ExpressLRS/1.2.0/src/platformio.ini failed, reason: getaddrinfo ENOENT raw.githubusercontent.com > > at ClientRequest. (C:\Program Files\ExpressLRS Configurator\resources\app.asar\main.prod.js:14:2318932) > > at ClientRequest.emit...

> Same problem on Linux machine also. If you are behind great firewall there is not much we can do about that at the moment.

@Index303, @MercadoNegro, @fanbinjim, @YI-BOYANG can you please try this nightly release? https://github.com/ExpressLRS/ExpressLRS-Configurator-Nightlies/releases/tag/v20220204.67723.0 I have made some changes that might help you.