rasmuslos
Version 3.0.2 crashes every time I open it
Since the 3.0.2 update I can no longer use ShelfPlayer, ABS is running version 2.28.0.
I've tired deleting my server configuration and logging in with a new user but that doesn't work. I've uninstalled the app, and re-installed it, that didn't work.
It seems like it might have something to do with multiple libraries, as I deleted my instance and it seemed to work fine after I re-installed it. Then I tried to select a different library, and the app immediately crashed.
How do I debug what could be going on?
It looks like the app crashes while attempting to parse a series name. Probably on the Home Screen or an in progress audiobook if the app instantly crashes. Do any of your series names contain a #?
I've tried to edit series names and remove /#/ but that doesn't seem to resolve the issue. Also, having /#/ in the series name isn't new, I've had them there since I started using ShelfPlayer.
Actually, it appears that ABS automatically adds a /#/ when a Series sequence number is added.
https://share.cleanshot.com/Hp7tWsP1
Yes, that is why i ask. Sometimes the ABS api will tell you the series name and sequence number, but sometimes, like on the home tab, it just gives you the formatted series name (e.g. “Test #1, Test #2”), which i have to parse. I dint like this approach, but that is how it is. The crash logs point to the code that does the parsing, I have some ideas on how to improve it, but i also don’t see immediate issues when looking at it. Can you check the series tab in the web interface (across all libraries) again if there is maybe a series name containing an , (or again #) because these are these the two characters that ABS uses to format a series name.
I have the same issue with ABS v2.29.0 and ShelfPlayer v3.0.4. Linked and logged into my ABS, then crash, when reading the library. How can I get the log of the sideloaded install?
I can exclude the library files, because a new clean ABS install is working.
@Tuphal then it’s probably unrelated to this issue, please open a new one. The process of acquiring the crash logs is the same
@afly007 please check if the issue persists in version 3.1.0, which will release in a few days. If it does, please share the crash logs again, I don't have the necessary dysms to symbolicate them anymore, they should be available in AppStore connect, but apparently sometimes they just are not...