Audible’s Android app is apparently turning Wi-Fi-only audiobook downloads into a very expensive suggestion. Users are reporting sudden data spikes from a few megabytes to 15GB or more, with some saying the app has pushed them past carrier limits and into overage charges without any obvious change in how they listen.
The awkward part is that this does not look like a simple ”background sync went wild” story. Reports point to the app ignoring the Wi-Fi-only download setting, and one likely explanation is that a recent release is forcing repeated re-downloads of titles that should already be stored locally. That is the sort of bug that quietly punishes the most careful users first.
Version 26.19.13 is under suspicion
Multiple complaints on Reddit point to version 26.19.13 as the common factor. Audible support has asked users for title details and app version numbers, which is sensible enough, but not especially reassuring if your monthly data bucket is already on fire.
One proposed explanation is that cloud syncing and license verification are getting tangled up, triggering the app to fetch the same books again and again. That would fit the symptoms better than the more colorful theory that a splash-screen animation somehow caused a multi-gigabyte problem. Nice try, but not credible.
Why Audible on Android can burn through mobile data
Mobile data is cheaper than it used to be, but ”cheaper” is not the same as ”limitless.” A rogue app can still turn a decent plan into a surprise bill, and audiobook users are especially vulnerable because they often download large files in bulk and then assume the device will stay offline.
- Reported data use: from a few megabytes to 15GB or more
- Suspected app version: 26.19.13
- Reported behavior: Wi-Fi-only downloads appear to be overridden
A fix is the only real answer
Audible is aware of the complaints, and that is probably the only encouraging detail here. If the app really is re-downloading titles or misfiring during license checks, the fix needs to come from Amazon’s side, not from users digging through settings that the app may already be ignoring.
For now, the most likely outcome is a patch landing soon, followed by the usual round of people checking their carrier apps and wondering how an audiobook player managed to behave like a streaming video app with no brakes. If the reports keep piling up, Audible may also have to explain why a basic offline feature failed so loudly in the first place.