Dats won't download on windows

[aadilayub]

I added one of my dats that I've peered on hashbase, and it won't download (stays stuck at 0%, 0 B/s even when the peers increase to 2).

Opening the console, I get these warnings:

Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: IntroScreen

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: FileDrop

and this error :

events.js:177 Uncaught Error: /C: could not be found
    at notFound (C:\Users\aadil.ayub\AppData\Local\Programs\dat-desktop\resources\app.asar\node_modules\append-tree\index.js:683)
    at onnodes (C:\Users\aadil.ayub\AppData\Local\Programs\dat-desktop\resources\app.asar\node_modules\append-tree\index.js:116)
    at onget (C:\Users\aadil.ayub\AppData\Local\Programs\dat-desktop\resources\app.asar\node_modules\append-tree\index.js:358)
    at processTicksAndRejections (internal/process/task_queues.js:84)

[okdistribute]

This might be a problem deeper in dat-node, that might need to be updated.

[okdistribute]

I'm getting a windows machine sometime in the next month and can do more digging, unless someone else wants to have a go :)

[okdistribute]

hey can you see if master works for you now? like i said I can't test on windows, but maybe it was an easy fix

[aadilayub]

I'll check it out in a few hours! Do I just clone and then run npm install + npm run start?

[aadilayub]

Tried it again. It looks like I'm getting the same error:

Uncaught Error: /D: could not be found
    at notFound (D:\dat-desktop\node_…d-tree\index.js:683)
    at onnodes (D:\dat-desktop\node_…d-tree\index.js:116)
    at onget (D:\dat-desktop\node_…d-tree\index.js:358)
    at processTicksAndRejections (internal/process/task_queues.js:84)

The download still won't progress like earlier:

Also saw this error in cmd:

[okdistribute]

Yeah that Object not found error doesn't have to do with it, unfortunately.

Bummer, well, do you see the same error with the dat commandline tool?

[aadilayub]

Happy to report no errors on the cli version :)

[okdistribute]

okay great news, that means something is wrong with the desktop app so let's figure out what the differences are!