Change Details

It's currently possible to get the app into a misbehaving state in which it believes zim compilations are present that no longer exist. 1. Download a comp (e.g., WP Uganda) 2. Let the app search for it and cache the info 3. Remove the comp outside the context of the app (e.g., in a file explorer app or with ADB) 4. Search compilations in-app and select the same comp from the list Expected: The app detects the file is absent, and the 'Download' button appears Actual: The app still believes (based on cached compilation info) that the comp is still present, and the 'Remove' and 'My compilations' buttons appear

It's currently possible to get the app into a misbehaving state in which it believes zim compilations are present that no longer exist. 1. Download a comp (e.g., WP Uganda) 2. Let the app search for it and cache the info 3. Remove the comp outside the context of the app (e.g., in a file explorer app or with ADB) 4. Search compilations in-app and select the same comp from the list Expected: The app detects the file is absent, and the 'Download' button appears Actual: The app still believes (based on cached compilation info) that the comp is still present, and the 'Remove' and 'My compilations' buttons appear This condition persists even after clearing the app data in Android settings. (!)

It's currently possible to get the app into a misbehaving state in which it believes zim compilations are present that no longer exist. 1. Download a comp (e.g., WP Uganda) 2. Let the app search for it and cache the info 3. Remove the comp outside the context of the app (e.g., in a file explorer app or with ADB) 4. Search compilations in-app and select the same comp from the list Expected: The app detects the file is absent, and the 'Download' button appears Actual: The app still believes (based on cached compilation info) that the comp is still present, and the 'Remove' and 'My compilations' buttons appear This condition persists even after clearing the app data in Android settings. (!)