Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Filename can either be an absolute HTTP[s] URL, *or* a file name #690

Closed
virror opened this issue Aug 22, 2016 · 14 comments
Closed

Comments

@virror
Copy link

virror commented Aug 22, 2016

  • Version: 5.30.0
  • Target: Win32

Im trying to use electron together with the electron release server (https://github.com/ArekSredzki/electron-release-server) but im getting a system error when using dots in the path for the auto-update server and thats required with the electron release server.
Im getting the same issue as here;
Squirrel/Squirrel.Windows#436

@virror virror changed the title Filename can either be an absolute HTTP[s] URL, *or* a file name Error: Filename can either be an absolute HTTP[s] URL, *or* a file name Aug 22, 2016
@gdurastanti
Copy link

Getting this as well while using the autoUpdater in electron with electron-release-server backend. Any workarounds?

@virror
Copy link
Author

virror commented Aug 23, 2016

Have not found any workaround sadly : /
I put the updated files on dropbox at the moment so i can continue, hope this can be fixed or worked around.

@virror
Copy link
Author

virror commented Aug 29, 2016

ANyone??

@develar
Copy link
Member

develar commented Aug 29, 2016

It is not electron-builder issue. Currently we are working on #529 and NSIS will be default target instead of Squirrel.Windows.

@virror
Copy link
Author

virror commented Aug 29, 2016

Ok, thanx for the answer.
How does this package work with Squirrel.Windows? The only package i have added is this one and the electron one and i saw this was reported before and marked fixed in the squirrel.windows git, but how do i know what version is being used?

@develar
Copy link
Member

develar commented Aug 30, 2016

but how do i know what version is being used?

Latest version of Squirrel.Windows is bundled into your app.

@virror
Copy link
Author

virror commented Aug 30, 2016

This one is marked as fixed almost a year ago so i guess this must me a new error then, thanx for the clarification : ) I will contact them about it, do you plan on abandoning squirrel after implementing NSIS or will you continue to use and update squirrel.windows? The electron release server only supports that atm : /

@develar
Copy link
Member

develar commented Aug 30, 2016

do you plan on abandoning squirrel after implementing NSIS or will you continue to use and update squirrel.windows

Although it is an open source project, personally I am not going to abandon Squirrel.Windows support. Personally I am not going to improve Squirrel.Windows, only maintain. As in this case – I don't want to waste my free time and investigate what's wrong with Squirrel.Windows if I am sure that is not an electron-builder bug. Instead, we will provide robust and maintainable NSIS/JS-based solution.

@virror
Copy link
Author

virror commented Aug 30, 2016

I understand and have already posted an issue on their forum about it. I was just wondering tf you planned on updating squirrel.windows when there are official fixes even going forward?

@develar
Copy link
Member

develar commented Aug 30, 2016

I was just wondering tf you planned on updating squirrel.windows when there are official fixes even going forward?

Yes. electron-builder goal is to simplify your life, not to teach what ditributable format is better for your product.

@virror
Copy link
Author

virror commented Aug 30, 2016

Thank you, sorry for taking up your time : )

@AlexeyVoroschak
Copy link

One solution is to specify appUrl: 'http: // localhost: 1337', in the file config/local.js of electron-release-server.

@phoenix2692
Copy link

One solution is to specify appUrl: 'http: // localhost: 1337', in the file config/local.js of electron-release-server.

Specifying appUrl fixed my issue. Thank you :)

@gdmec07150725
Copy link

I specify port 1337, but also has this issue. @phoenix2692

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants