App blocked at starting screen

Support
1

Hello everyone,

I have see many subject on this matter but I can’t find one which fix my issue.

I have an issue with my app which doesn’t start and stay blocked on the starting screen.
I’ve installed the last version of Virtual Box without any success.

Here my last lines of logs :

Jan 11, 2018, 12:41 PM GMT+1 - info: [main/index] Existing Pressmatic data does not exist.
Jan 11, 2018, 12:41 PM GMT+1 - warn: [main/index] Unhandled Rejection at: Promise  Promise {
  <rejected> TypeError: Cannot use 'in' operator to search for 'version' in null
    at C:\Users\issey\AppData\Local\Programs\local-by-flywheel\resources\app.asar\main\updater.js:1:17896
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:135:7) }  reason:  TypeError: Cannot use 'in' operator to search for 'version' in null
    at C:\Users\issey\AppData\Local\Programs\local-by-flywheel\resources\app.asar\main\updater.js:1:17896
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:135:7)
Jan 11, 2018, 12:41 PM GMT+1 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Jan 11, 2018, 12:41 PM GMT+1 - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, 'machine-halted' ] machine-halted
Jan 11, 2018, 12:41 PM GMT+1 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jan 11, 2018, 12:41 PM GMT+1 - info: [main/docker-machine] Boot2Docker.iso hash does not match!
Jan 11, 2018, 12:41 PM GMT+1 - info: [main/docker-machine] Copying C:\Users\issey\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\boot2docker.iso to C:\Users\issey\.docker\machine\machines\local-by-flywheel\boot2docker.iso
Jan 11, 2018, 12:41 PM GMT+1 - info: [main/docker-machine] Running  C:\Users\issey\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Jan 11, 2018, 12:41 PM GMT+1 - info: [main/docker-machine] Starting "local-by-flywheel"...
Jan 11, 2018, 12:41 PM GMT+1 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Jan 11, 2018, 12:41 PM GMT+1 - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...

And you can see the logs file here if needed :
https://www.dropbox.com/s/mzdqso8chf72y9h/local-by-flywheel.log?dl=0

Could you help me to resolve this issue please ?

Regards,

Issey

2

Hi Issey,

Sorry for the trouble!

Can you please try the following?

  1. Quit Local if it’s running
  2. Open VirtualBox
  3. Right-click on local-by-flywheel and go to Close » Power Off
  4. Re-open Local by Flywheel
3

Hello Clay,

Thanks for your return and I tried it twice but it’s still freezing.

Do you have another solution ?

Regards

4

@Issey,

Can you please provide the local-by-flywheel.log file again now that you’ve done that?

Also, are you running a VPN, firewall, or any type of internet security software?

5

Hello Clay,

Here the new log : https://www.dropbox.com/s/mzdqso8chf72y9h/local-by-flywheel.log?dl=0

Yeah I have Nod32 and Zone Alarm, the fact is that I haven’t changed the settings since ages for those two.
I just shut them down, put the folder in the exclusion, watched the logs aswell and nothing special pop up.

6

Hello Clay,

Could you help me because I had started my first project with Local for a client and now I am stuck ?

I had to normally show my work today to this client but can’t do because of this issue…

7