Audible Cloud Player broken since v1.44.105

Issue: Cloud Player starts then tries to buffer. Buffering fails and I am presented with a generic error message saying ‘Try again later.’

Browser Console reports:
A1afwnb0YCL.js?AUIClients/AudibleWebPlayerAssets:2910 It is recommended that a robustness level be specified. Not specifying the robustness level could result in unexpected behavior.
(anonymous) @ A1afwnb0YCL.js?AUIClients/AudibleWebPlayerAssets:2910
61gcbKtCLjL.RC%7C11PYwsl+A1L.js,71aM+FDr9BL.js.js?AUIClients/AudibleCloudPlayerAssets&S7m1SUlT:3317 Failed to getProductStream
EX24dc9c746b924a5295f766ce8f169a18-libraryCode_source.min.js:3 visitor.publishDestinations() result: Attempted to attach and load the destination publishing iframe through this API call. Result: The destination publishing iframe was attached and loaded successfully.
DevTools failed to load source map: Could not load content for https://images-na.ssl-images-amazon.com/images/I/shaka-player.compiled.map: HTTP error: status code 400, net::ERR_HTTP_RESPONSE_CODE_FAILURE
61gcbKtCLjL.RC%7C11PYwsl+A1L.js,71aM+FDr9BL.js.js?AUIClients/AudibleCloudPlayerAssets&S7m1SUlT:3332 showing
generic error dialog because of timeout

What I have tried so far:
0.) Cleared absolutely all browser data I could clear.
1.) Disabled Brave Shields, allowed all scripts, and allowed all tracking and ads on the site. The plan was to turn them on one-by-one until I found the offender.

The issue still occurs with all Brave Shields and protections turned off. So I just gave up and turned everything back on.

It should be mentioned that the player works fine in… (cringe) Edge. So it’s not a firewall rule on Windows.

Timeout seems to happen here:
https://www.audible.com/webplayer?asin=B09XY39B53&contentDeliveryType=MultiPartBook&ref_=a_libraryItem_cloudplayer_B09XY39B53&fetchNewPlayQueue=true&overrideLph=false&initialCPLaunch=true

1 Like

Hello @Aijima, thank you for bringing it up. Apologies for the long delay. Is this still an issue for you? If so, please try downloading the latest version released a couple of days ago. and let us know if the issue persists. Regards.