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
{{ message }}
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
I have an electron app, arbitrator. It uses electron-boilerplate as a base. Within that electron application, I have an icon specified in resources/icons/512x512.png. When I run the application using npm start, the icon shows up on the Gnome Unity bar.
If, however, I run npm run release, and then run cd dist/linux && ./Arbitrator, the application runs, but the icon doesn't show up in the Unity bar (just the default icon). Further, if I run the ./Arbitrator command from the source repository working directory, then it finds the resources/icons/512x512.png file and shows it in the unity bar.
Is there a way I can make sure that the icon is shown for the app, regardless of how it's run (it seems to be referencing the path for the icon locally, rather than using the asar file for resources).
The text was updated successfully, but these errors were encountered:
(This is also a question on stackoverflow).
I have an electron app, arbitrator. It uses electron-boilerplate as a base. Within that electron application, I have an icon specified in
resources/icons/512x512.png
. When I run the application usingnpm start
, the icon shows up on the Gnome Unity bar.If, however, I run
npm run release
, and then runcd dist/linux && ./Arbitrator
, the application runs, but the icon doesn't show up in the Unity bar (just the default icon). Further, if I run the./Arbitrator
command from the source repository working directory, then it finds theresources/icons/512x512.png
file and shows it in the unity bar.Is there a way I can make sure that the icon is shown for the app, regardless of how it's run (it seems to be referencing the path for the icon locally, rather than using the
asar
file for resources).The text was updated successfully, but these errors were encountered: