-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Source being null prevents library sync #659
Comments
What sources do you have in your Playnite library? You can check the extension.log file to see if any errors were logged by the plugin. The extenions.log file can be found in Playnite's application directory. |
I think there is a legitimate error in the plugin that was recently introduced. I thought it was introduced and then resolved, but this does not appear to be the case. For more context: a game's source may not always be set within Playnite. This is often the case with emulators or manually added games. In the case a source is not set, it defaults to Emulator as the source and creates this new source on the fly to be used (as it is not in Playnite proper). This is why I thought it was resolved by using a default "Emulator" source when the underlying value is null. I'll have to investigate this further to see where this is breaking down. I certainly think it is a bug in the plugin. |
When I have the error, I do not see any error in the extension.log file. However, in the playnite.log file I have this: sorry for the format but there are some " ` " in the error that make this weird formating I don't know if this helps |
This is very helpful! Thank you! |
@Shayviri , @Nightchanger , can you wipe your database and try the latest dev build of both the app and the Plugin, then report back if this resolves the issue?
Thanks! |
I updated my docker with the :dev tag and installed the plugin you gave (v4.0.2). And I still have the same error: |ERROR|MainMenu:Main menu extension action failed. I am sorry, I think the last line was missing in the previous error I gave you |
This is very helpful. The second error is at a different location in the code and gives me a new lead. I apologize for having you be the tester. I can't reproduce it locally and don't what data in Playnite is required to reproduce it. I'll follow up soon with a new builds to try. Thanks again! |
@Shayviri , @Nightchanger , try the latest dev app and this Plugin version: https://github.com/andrew-codes/playnite-web/actions/runs/12243037521/artifacts/2295901727. Drop the database, retry, and report back. You may see more logs if there are any games that cannot be processed. Before it may have errored out, now it will produce a warning in the extension.log file. Thanks! |
Hi, I tried with the new plugin and the latest dev app, and it worked! When I launch one of those game, the playnite web doesn't throw an error anymore, but instead says: |
That's great news! 😁 I'll close this issue and cut a release. |
## [10.0.2](v10.0.1...v10.0.2) (2024-12-10) ### Bug Fixes * library sync errors for games w/o a source ([#663](#663)) ([ecc60e2](ecc60e2)), closes [#659](#659) * remember me auth sessions expires in 1 year ([#666](#666)) ([e100330](e100330)), closes [#546](#546) * signout works as expected ([#665](#665)) ([b4e0197](b4e0197)), closes [#662](#662)
🎉 This issue has been resolved in version 10.0.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
The text was updated successfully, but these errors were encountered: