Taking a long time to redeem.

[Spamboxx]

Having updated to Playnite 10.36 yesterday, the latest version of the Humble Keys add-on has been running for the past 24 hours with no changes. Even an uninstall and fresh reinstall does not fix the issue. Yet, when I uninstalled and ran all other library updates, they finished in record time. It shouldn't take this long to scan through all the keys in the library, correct? Running latest version 0.3.8.

[Dasmius007]

Correct. Thanks for reporting this. I'll look into it and get back to you.

[Dasmius007]

I just tested this with the latest Playnite released today (10.37), and it worked fine. Try updating to it, and see if it resolves the issue. If not, please attach your extensions.log file from your Playnite folder.

[Spamboxx]

extensions.log.txt

Still sitting like this even after update. Notice how the log always sits and ends at cache cleared each time... also, in the image is all the libraries I have set up. Is it possible one of them is causing the issue? Again, without your add on, they all run and complete, but this one hangs...

[Dasmius007]

Probably not, but it is possible. You do have 2 other Humble libraries installed too. The log is kind of cluttered because of all the other plugins. Is it possible for you to install a clean Playnite portable install, and just install Humble Keys library only, run it again and attach that extensions.log file? It would do 2 things: 1) ensure it's not another plugin causing a conflict, and 2) make the log much easier for me to read/parse and try and isolate the error.

[Spamboxx]

Set portable up on a SanDisk flash drive since I don't want to overwrite anything, only installed Humble Library, and it still runs the same with no additions, even with every setting checked. The log has but

extensions.log (1).txt

one line.

[Dasmius007]

Thanks. So I set mine up the same as your config, ran it and I also only get 1 line in my log - the same "Cache cleared". That is just a line that always gets logged regardless of success of the plugin running, as it happens at initialization if you have cache disabled (it is just confirming there is no cached data anymore).

For me, it works fine. I am assuming you are saying the progress bar at the top of Playnite is what is actually stuck, and it never finishes?

The plugin only really logs errors right now, and none of those are occurring. So I think I will need to add more debug log lines. I am about to release another update with some new features - I will include more logging in it. Once I do, I will let you know and you can try it again with the new version plugin and then attach that log file.

[livejamie]

Having the same issue, only after updating to the latest Playnite

extensions.log

[livejamie]

After reauthenticating, it seems to work eventually, but the process is prolonged.

It would be nice if there were some sort of indication of progress here:

Other library addons will show a progress bar/percentage/etc, indicating what it's doing and how much time is left. That would make it feel better.

[Dasmius007]

@livejamie: I checked with the Playnite devs, and they said that no other library plugins are providing incremental progress bar updates during their library update process. They said it isn't supported, and you must just be noticing the progress bar advancing between each library as they update instead. For instance, the Indiegala library takes a long time with no progress bar update either.

So I appreciate your suggestion, but I am unable to implement it.

[Dasmius007]

@Spamboxx @livejamie: I added more debug logging to try and diagnose this. Please update to the latest version of Humble Keys (version 0.3.9), as well as the latest version of Playnite (version 10.43) and try again. If the issue persists please install a test portable version of Playnite, and only add the Humble Keys library plugin.

Before you try to update the library, press F4 to open Playnite Settings, and click the "For developers" menu on the left. Check the "Log trace messages" checkbox to enable the more detailed logging, and click Save. Now update the library, and attach your extensions.log file here.