Audible Android app 26.19.13 bug

- Good e-Reader reported on May 22 that Audible’s Android app version 26.19.13 is causing abnormal downloads, playback disruption and app instability for some users. - The key figure is 26GB: Good e-Reader said some users reported that much extra storage use, while PiunikaWeb tied complaints to broken Wi-Fi-only controls. - Audible help pages still list generic crash troubleshooting, while user reports and third-party coverage say a fix is in development.

Audible’s Android app version 26.19.13 is drawing complaints from users who say the app is re-downloading books, burning through mobile data and interrupting listening even when titles were already saved offline. Good e-Reader reported on May 22 that the issue affects version 26.19.13 specifically and described it as a cloud syncing and license verification glitch. PiunikaWeb reported a day earlier that Audible support had acknowledged the problem to users and said a fix was being worked on. ### Which Audible version is at the center of the reports? Version 26.19.13 is the build named in both Good e-Reader’s report and PiunikaWeb’s follow-up on user complaints. APK listing sites also show that version 26.19.13 is a current Android release, which matches the build number cited in those reports. Good e-Reader said the bug is limited to the Android app, not Audible broadly across all platforms. (goodereader.com) PiunikaWeb separately reported a different iPad crash issue, but treated the Android problem as a distinct bug tied to excessive data use and repeated downloading. ### What are users saying the bug is doing? Good e-Reader reported that the app is failing to recognize audiobooks already downloaded to a device, causing repeated downloads over mobile networks. (goodereader.com) The outlet said some users reported more than 26GB of additional storage consumed and said downloads were occurring over cellular even when Wi‑Fi-only settings were enabled. PiunikaWeb described the same pattern in user complaints, saying reports ranged from about 2GB to nearly 30GB of mobile data use in a matter of days. According to that report, users said the app was consuming mobile data while they listened to titles that were supposed to be available offline. Android Authority also reported on May 22 that some Audible users were seeing unusually high mobile data consumption on Android. (goodereader.com) That outlet’s report aligns with the narrower version-specific claims made by Good e-Reader and PiunikaWeb. ### Why would a download bug affect playback? Good e-Reader said the reported failure involves cloud syncing and license verification, which would explain why downloaded titles may not be treated as fully local files. (piunikaweb.com) PiunikaWeb, citing screenshots of user conversations with support, reported that the app may be repeatedly streaming or re-downloading chapters instead of recognizing the copy already stored on the device. That connection is an inference from the reported behavior, not a formal technical incident report from Audible. (androidauthority.com) Audible’s own public help pages currently show generic troubleshooting for crashing apps, including clearing cache, updating the app and rebooting the device, but they do not appear to include a public bulletin naming version 26.19.13 or describing the Android data-drain issue. ### What can affected users do right now? PiunikaWeb reported that because in-app controls appear unreliable in affected cases, the most dependable workaround is blocking Audible’s mobile data access at the Android operating-system level. (goodereader.com) That is the most specific mitigation described in the current reporting. Good e-Reader urged users to avoid updating to version 26.19.13. (help.audible.com) For people already on that build, the practical steps supported by current reporting are to check Android data usage, confirm whether Audible is using cellular data despite Wi‑Fi-only settings, and watch for a patched release. ### Has Audible said anything publicly? Audible’s public-facing help pages remain limited to standard troubleshooting guidance as of May 22. (piunikaweb.com) PiunikaWeb reported, however, that Audible support told users the company was aware of the glitch and that a fix was in the works. The next concrete marker will be a new Android app release beyond 26.19.13 or a support notice from Audible naming the bug. (goodereader.com) Until then, the build number 26.19.13 is the main detail users can check in the Play Store or in the app’s settings. (help.audible.com)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.