You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. Having trouble getting it to work after packaging electron app using electron-packager or electron-builder. Calling idevice_info crashes child process returning message "3221225477" on close. Doesn't seem to ever get past calling idevice_new inside info.c.
Also, everything works while running electron in debug. My setup is clean with no modifications to source. Using node v10.11.0. Electron v4.0.3.
@norman784@didix21 Were you guys able to get it to work on an electron production build for windows?
Not sure what I'm missing. Any help is greatly appreciated!
The text was updated successfully, but these errors were encountered:
Hello @iap2,
I've never tested on node v10.11.0 and Electron v4.0.3. In my case, I used it with node v8.15.1 and Electron v1.8.3 and I haven't had any trouble with it. How are you using idevice_info ?
Thanks for getting back. I just tried it on your setup with node v8.15.1 and electron v1.8.3 and still running into the same issue. I tried calling idevice_info from both the main and renderer process. Calling idevice_id has the same issue as well. All of this works when I'm just debugging electron. It's only an issue after packaging. I'm using electron-packager v13.1.1. What did you use for packaging?
Hi. Having trouble getting it to work after packaging electron app using electron-packager or electron-builder. Calling idevice_info crashes child process returning message "3221225477" on close. Doesn't seem to ever get past calling idevice_new inside info.c.
Also, everything works while running electron in debug. My setup is clean with no modifications to source. Using node v10.11.0. Electron v4.0.3.
@norman784 @didix21 Were you guys able to get it to work on an electron production build for windows?
Not sure what I'm missing. Any help is greatly appreciated!
The text was updated successfully, but these errors were encountered: