32bit - Githubissues

Custardcs commented 7 years ago

hi, so i have been reading up on some of the things that were being used and i see you said to a previous message about using

build --ia32 but it doesn't work :|

also you are using target = squirrel.windows they say its depreciated..

so if i use nsis can i still use your auto updating?

megahertz commented 7 years ago

Hi. Last time I used win32-ia32 it works correctly. And electron-builder always displays warning when you build squirrel ia32 build. As for nsis, electron-simple-updater doesn't support it.

Custardcs commented 7 years ago

i had to use "dist": "build --arch=all", in order for it to work. noone explain this :| lol but anyhow thanks bud ill keep the squirrell and all is building and stuff and if i publish

do i just do npm run publish? and it will push both 32 and 64 to github?

megahertz commented 7 years ago

By default, publisher uploads only the current build (made for the current platform). So you need to specify buildId (see docs) to publisher another build.

Custardcs commented 7 years ago

but what happens with the update.json then it gets over written each time? it doesnt combine the scripts?

does this mean i have to manually change it?

megahertz commented 7 years ago

update.json will be merged

Custardcs commented 7 years ago

alright well something is not working, because i published and it overwrote it. and i am now getting another error i dont understand what i am doing wrong. i uploaded version 0.0.1 and 0.0.2

i ran version 0.0.1 and it says (Update for win32-x64-prod-v0.0.1 is not available) is there something i'm missing?

Custardcs commented 7 years ago

when it finished publishing it got this

Could not get updates.json. You can ignore this warning if you run this command for the first time. A hosting response is: 404 {"error":"Not Found"} All releases have been successfully published

is this why it is overwriting the json?

because it is updating the json but its not merging if i publish from a mac or if i publish the 32bit

sorry about all the questions >.<

megahertz commented 7 years ago

Yes, that's why it's not merged. Publisher can't determine the json path. You can set it through updatesJsonUrl option.

Custardcs commented 7 years ago

alright ill place it it both,

could you just explain to me about the updating? with version 0.0.1 and 0.0.2

megahertz commented 7 years ago

First of all, make sure that your app can retrieve updates.json correctly. Because you've received 404 when publishing I can assume that something wrong with update.url option.

Custardcs commented 7 years ago

well its because its a private repo? im assuming? and if i make it public i see its releasing the source code with the release and i cant do that. soo is there a way i can get it to work between the two?

megahertz commented 7 years ago

You can create a public repo for releases only.

Custardcs commented 7 years ago

Thats fine i dont mind creating a public one but then when i publish it has the source code with the release and i dont want the source available? so how i i stop it from releasing the source when i run

npm run publish

megahertz commented 7 years ago

What do you mean? Publisher can only upload binaries, not source.

Custardcs commented 7 years ago

i created a public repo and tried to npm run publish and when it was done this is what it has

capture

i can not have the source available

megahertz commented 7 years ago

Sure, github creates it for each release, even if the repo is empty.

Custardcs commented 7 years ago

but then anyone can download the source? or is it the source of the empty repo?

megahertz commented 7 years ago

Just open the archive

Custardcs commented 7 years ago

alright ill try it now bud.. thank you for all your help.

Custardcs commented 7 years ago

Hi bro tried the 32 bit publish doesnt work

C:\scratch\Filmplicity>npm run publish32

filmplicity@0.0.7 publish32 C:\scratch\Filmplicity publish win-ia32

Unknown build type win-ia32

npm ERR! Windows_NT 10.0.14393 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "publish32" npm ERR! node v6.11.0 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! filmplicity@0.0.7 publish32: publish win-ia32 npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the filmplicity@0.0.7 publish32 script 'publish win-ia32'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the filmplicity package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! publish win-ia32 npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs filmplicity npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls filmplicity npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! C:\scratch\Filmplicity\npm-debug.log

C:\scratch\Filmplicity>

megahertz commented 7 years ago

win32-ia32

14 авг 2017 г. 7:46 пользователь "JarHeaD" notifications@github.com написал:

Hi bro tried the 32 bit publish doesnt work

C:\scratch\Filmplicity>npm run publish32

filmplicity@0.0.7 publish32 C:\scratch\Filmplicity publish win-ia32

Unknown build type win-ia32

npm ERR! Windows_NT 10.0.14393 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "publish32" npm ERR! node v6.11.0 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! filmplicity@0.0.7 publish32: publish win-ia32 npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the filmplicity@0.0.7 publish32 script 'publish win-ia32'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the filmplicity package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! publish win-ia32 npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs filmplicity npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls filmplicity npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! C:\scratch\Filmplicity\npm-debug.log

C:\scratch\Filmplicity>

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/megahertz/electron-simple-publisher/issues/26#issuecomment-322088451, or mute the thread https://github.com/notifications/unsubscribe-auth/ABrlcOH_V7OtNMxxcDXPOXQbDzSK6xgEks5sX7T8gaJpZM4OlAKS .

Custardcs commented 7 years ago

i have done that too

C:\Scratch\Filmplicity>npm run publish32

filmplicity@0.0.7 publish32 C:\Scratch\Filmplicity publish win32-ia32

File C:\Scratch\Filmplicity\dist\win-ia32\Filmplicity Setup 0.0.7-ia32.exe doesn't exists. You can try to check if:

electron-builder successfully made a build
electron-builder and electron-simple-publisher are up to date
if nothing helps please create a new github issue. Don't forget to include electron-builder version to the bug report.

npm ERR! Windows_NT 10.0.15063 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "publish32" npm ERR! node v6.11.1 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! filmplicity@0.0.7 publish32: publish win32-ia32 npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the filmplicity@0.0.7 publish32 script 'publish win32-ia32'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the filmplicity package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! publish win32-ia32 npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs filmplicity npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls filmplicity npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! C:\Scratch\Filmplicity\npm-debug.log

C:\Scratch\Filmplicity>

Custardcs commented 7 years ago

capture i see it is looking for

Filmplicity Setup 0.0.7-ia32.exe doesn't exists

but when i use the dist32 which builds it in the correct folder win-ia32

but with the name of Filmplicity Setup 0.0.7.exe

megahertz commented 7 years ago

What's electron-builder version?

Custardcs commented 7 years ago

"electron-builder": "latest", in js

electron-builder 19.16.3

megahertz commented 7 years ago

Try the latest version of publisher

Custardcs commented 7 years ago

0.4.7? its still doing the same thing :|

megahertz commented 7 years ago

Please provide console output when using this version

Custardcs commented 7 years ago

its still building the file with Setup 0.0.7.exe isnt it supposed to build it with the Setup 0.0.7.exe-ia32?

megahertz commented 7 years ago

In my environment it can use both forms, with -ia32 and without. Try remove node-modules and than npm i

Custardcs commented 7 years ago

alright yes its working ... its publishing if there is any other issue ill let you know 💃

megahertz / electron-simple-publisher

32bit #26