Error while launching packaged app on Windows 10 (Surface)

[RilRil]

Hello, i've got some trouble with Windows 10 ...
I'm packaging for platform windows x64 using electron 1.2.7; electron-builder 5.12.1 on a windows 10 x64.

when I execute the app file in the win-unpacked directory on the machine I packaged on everything is working correctly.
But If I try to execute the same file on a Windows Surface I get this error :

the module file (4753.tmp.node) exists ...

any idea ?

[develar]

Set build.asar to false.

Please see electron/packager#425

[develar]

Do you use native extensions or do you execute external exe?

[RilRil]

what do you mean ?

[develar]

Please try to set build.asar to false as temporary workaround.

And

Do you use native extensions or do you execute external exe?

[RilRil]

oh ok sorry.
I'am using some native extensions

[RilRil]

When I'm packaging I have this message : "Skip app dependencies rebuild because dev and app dependencies are not separated", I dont know if it can be related though ...

[develar]

I dont know if it can be related though

It means that you can build only on the same platform — i.e. you cannot build on Linux on Windows. It is not the reason of the issue (since you build in WIndows).

Asar is the issue, see http://electron.atom.io/docs/latest/tutorial/application-packaging/#limitations-on-node-api/

So, disable asar, and report — does it help you. If helps, please provide sample project (or name of native extensions) and I will try to fix it (such files should be not packed into asar archive). Or you can try to use asar.unpackDir.

[RilRil]

With the build.asar option to false I now get the following error :

[develar]

Maybe for MS Surface you have to recompile native ext. I cannot help. BTW, is Surface is ARM or x86?

[RilRil]

it's x86. ok that's too bad .. I'll try to remove that extension or maybe to recompile on the surface..
thx anyway

[develar]

Is your packaged app works on other Windows machine? You can send me your app and I will try to investigate what is wrong. [email protected]

[RilRil]

It works if I execute the packaged app on the machine I packaged it...
Unfortunately I cant send you the app since it belongs to my company.

[develar]

I doubt that Surface is the issue. So, I ask you sample/real project to investigate.

[RilRil]

EDIT : I found the problem, a .dll was missing for the native extension to work (libeay32.dll from SSL). So I just added the missing .dll next to the .exe and it worked !

[bordunez]

Hi RilRil,
I'm getting a similar problem with a native extension (windows.devices.geolocation), can you give some suggestion in order to find what is the missing .dll dependency in this native extension?

Thanks

[RilRil]

Hi @bordunez ,
in my case, the missing library (.lib) was referenced in a file (binding.gyp) of one of my dependancies.

Maybe this could help you : http://stackoverflow.com/questions/33205339/what-dll-is-needed-for-windows-devices-geolocation,