Last Played Books widgets don’t show artwork or text

[city3oy]

Environment

• OS Version: [e.g. 13.5.1]
• App Version: [e.g. 3.9.0-1]

Description

A clear and concise description of what the bug is. Last Played Books widgets, both sizes, initially stopped updating widget information, continued to show the previous book shown even though no longer being listened to, when a new book was being played. After removing and re-adding the widget(s) they now contains no artwork or text at all.

This bug does not appear to affect the Time Listened widgets.

This bug was previously seen in Last Played Books widgets and also did not affect Time Listened widgets and was fixed.

Steps to reproduce the behavior

1. Adding either or both Last Played Book widgets.
2. Removed and re-added widgets resulted in no information shown instead of it being stuck on a previously listened book.
3. Only affects Last Book Played widgets
   
   
   
   

[rakheshster]

I too am experiencing this issue. App version 5.5.1-91. iOS 18.2.

Not sure when it started. I finally completed the book I had been listening to these past few weeks and noticed that the (last played) widget didn't update to the new book I was listening to. So I removed and re-added and since then it's showing nothing.

Update: Saw a new version of the app (5.5.2-93) and updated to that. Same issue. Removed and re-added the widget just in case.

[rakheshster]

I will add this as a new comment rather than edit the previous one so it doesn't get missed.

Today the widgets are working. It even updates when I listen to a different audiobook. I am on the same version as my last comment yesterday. No changes to the iOS version nor did I reboot the phone.

[szymon-romanko]

+1, same issue
iOS: 18.2
app version: 5.5.2
let me know if you need anymore details

[GianniCarlo]

I'll post here a link when the next open beta is available, I tried to debug this with someone over a support ticket, but once they installed the beta build, it started working. For context, we changed how widgets load the data (back in v5.4.0) so it's done via the shared UserDefaults, instead of loading the entire CoreData stack which was crashing for some users (not sure if that's just memory constraints on the widget app extension), and what I've found is that the extension sometimes caches things, and I think it's messing up things when going from the old way to the new way of loading the data

If anyone is experiencing this and the first version they installed is v5.5.0+ please let me know

[jesse2367]

I'll post here a link when the next open beta is available, I tried to debug this with someone over a support ticket, but once they installed the beta build, it started working. For context, we changed how widgets load the data (back in v5.4.0) so it's done via the shared UserDefaults, instead of loading the entire CoreData stack which was crashing for some users (not sure if that's just memory constraints on the widget app extension), and what I've found is that the extension sometimes caches things, and I think it's messing up things when going from the old way to the new way of loading the data

If anyone is experiencing this and the first version they installed is v5.5.0+ please let me know

Hi! I keep having this issue. I have version 5.5.4 and iOS 18.3.1

[GianniCarlo]

Hi @jesse2367 @szymon-romanko @city3oy this is the link to join the beta (link: https://testflight.apple.com/join/tUPqnaRS ), there's still one more update I want to do to that version, so probably it's not completely fixed (my only clue right now, is that CoreData continues causing crashes on the widget extension due to a lock on the database file that iOS does not allow for app extensions)