-
Notifications
You must be signed in to change notification settings - Fork 53
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
Latest windows release not working (Windows 10) #83
Comments
Its working fine for me on latest, so whatever the issue is its with your environment |
@Masamune3210 ah I guessed that's the case, but I have no clue how to debug anything. |
not working for me neither
@dilirity, have you modified the settings.json file? |
@azumukupoe - no. Simply downloaded, extracted and started the exe. Spawns a bunch of electron processes, the exe itself sometimes shows up in the task manager, but nothing ever happens. |
@azumukupoe - thanks. I read it several times. Third step is an alternative as far as I understand, so it should work just by starting it like a normal program. Unfortunately, it doesn't. I want to use the GUI. EDIT: |
@dilirity - can you please set debug to "true" , re-run, and paste the log here ? |
@giwty - sure. slm.log
settings.json {
"versions_etag": "W/\"2ef50d1cb6bd61:0\"",
"titles_etag": "W/\"a5b02845cf6bd61:0\"",
"prod_keys": "",
"folder": "",
"scan_folders": [],
"gui": true,
"debug": true,
"check_for_missing_updates": true,
"check_for_missing_dlc": true,
"organize_options": {
"create_folder_per_game": false,
"rename_files": false,
"delete_empty_folders": false,
"delete_old_update_files": false,
"folder_name_template": "{TITLE_NAME}",
"switch_safe_file_names": true,
"file_name_template": "{TITLE_NAME} ({DLC_NAME})[{TITLE_ID}][v{VERSION}]"
},
"scan_recursively": true,
"gui_page_size": 100,
"ignore_dlc_title_ids": []
} |
@giwty - I was able to get it to work by running the build process for windows. I had to remove some of the environments from the bundler.json to get it to properly though, since I got some errors (removed mac and linux). {
"app_name": "Switch-Library-Manager",
"icon_path_darwin": "resources/icon.icns",
"icon_path_linux": "resources/icon.png",
"icon_path_windows": "resources/icon.ico",
"environments": [
{"arch": "amd64", "os": "windows"}
]
} Anyway - after bundling, the exe properly starts up. The size of my bundled exe is 89mb, the one in the releases is 77. |
Nice work, happy you got it working. |
I tried every version, combining folders but also for me the v1.40 version does not start (Windows 11). Is there somewhere to download the working build? The v1.35 version does start but when I put the v1.40 binary in the v135 folder it doesn't start (v1.40 ofcourse :)). Anyway thanks for this app! |
1.40 works fine for me on fully up to date 11, so once again, it will likely fall onto you figuring out what is abnormal about your environment. Check the event logs for any mention of it crashing and it might at least give a hint as to what is going on. |
The CLI does work, I will use this one. Thanks for answering. To me it seems (not a programmer) but somehow the v1.4.0 is about 15MB and the working ones are about 75MB. Also it seems the electron runtime is included (as the web page folder on earlier ones?). So for me starting at v1.4.0 and backwards working to v-older I noticed the folders created in %appdata% (ad said the runtime?). But the v1.4.0 doesn't spawn any runtime download or whatever on my system (fairly clean installed). https://gbatemp.net/threads/switch-library-manager-easily-manage-your-switch-game-backups.568639/page-11 |
also v1.4.0 GUI log file with debug=true
|
Well, considering I already said it works fine for me, It's not a issue of missing parts of the file. |
So I downloaded the latest available version from the releases section (1.4.0 - switch-library-manager.GUI.windows.zip).
I've added my prod.keys in the same directory as the exe.
Starting it creates several files and that's it - nothing else.
sim.log
Waited more than 10 minutes, restarted - nothing.
Any ideas?
The text was updated successfully, but these errors were encountered: