{
  "version": "2",
  "id": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf",
  "title": "Android workout tracker's Play Store release log details R8 crash and a blocked upload",
  "summary": "A developer's account of shipping DotShredzilla 1.5.1 to Google Play describes a release-only crash caused by R8 stripping a Room class pulled in by AdMob, a pre-review block over a broad photo permission, and a Data safety form that understated what the app collects.",
  "body": "An open-source Android workout tracker called DotShredzilla has documented the work between a build that runs on a developer's own phone and a build that passes Google Play's checks, in the fifth part of a build series published on dev.to. The author, writing under the FreeRave/DotSuite name, says version 1.5.1 was going through Play review at the time of writing. The post is a first-person account of one release, not an independent audit, so every technical claim below is the author's own description of what happened.\n\nThe most concrete finding concerns a crash that appeared only in the release build. The author says every build tested up to that point had been a debug build, and that installing the minified release APK produced a launch failure with the message \"Failed to create an instance of androidx.work.impl.WorkDatabase\". The author states that none of their own code uses WorkManager; the dependency arrived through AdMob, which pulled in WorkManager 2.7.0 alongside Room 2.2.5.\n\nA reflection problem is what the stated mechanism amounts to. The post says R8 stripped the class during minification because the Room version in question builds its database class via reflection and does not ship the keep rules R8 requires. Depending directly on a current WorkManager is the described fix, since that pulls in a newer Room along with its consumer keep rules. The author's takeaway is procedural, not clever: every time, before uploading, install the minified release build on a real device.\n\nRather than from human review, a second surprise came from Play Console's pre-review checks. VersionCode 8, the author reports, was blocked under the photo and video permissions policy, the reason being that the app requested READ_MEDIA_IMAGES only so users could pick a profile picture. Through ActivityResultContracts.PickVisualMedia, version 1.5.1 is said to move to the system photo picker, which needs no storage permission and grants the app access solely to the image chosen. Older testing tracks that still shipped the broad permission were paused, the author adds, since the policy covers every track.\n\nA mismatch was also exposed by the release, sitting between the code and the store listing. Workouts, weight and body measurements are in fact collected and analytics is used, the author writes, while the Data safety form claimed only device IDs were gathered. The listing now declares health and fitness information plus app interactions as collected, for app functionality and analytics; device IDs are shared solely for ads. For the account, an app-level confirmation, a trader status declaration and a link to app-specific terms were additionally required — something the author frames as a publishing decision, not a checkbox.\n\nVersion history turned out to be another gap. The author says the version live on Google Play was 1.2.0, and that 1.3.0 and 1.4.0 had never been uploaded, making this a larger jump than the version number implied. The lesson offered is to check what is actually live on the store before assuming you know the release history.\n\nDescribed on the update path is a move, from 1.5.0 onward, to Google Play In-App Updates away from a small library that read an update-info.json file from Firebase Hosting and showed a dialog with an always-available dismiss button. Under the new flow, at most once a day the app offers a newer version when Play has one, downloads it in the background and then asks for a restart. The lowest version allowed to run is set by a Firebase Remote Config parameter, min_supported_version_code; anything below it gets a full-screen update-required screen using Play's immediate update flow. Without shipping a release, the minimum can be raised from the Firebase console, the author notes, and the old JSON remains for installs predating the change.\n\nA reliability rewrite was given to the rest timer. According to the author, the previous implementation used the colored launcher icon as a status-bar icon, repositioned its notification every 100 ms and restarted the app when tapped, and with the screen off the phone could sleep, so the end-of-rest alert sometimes arrived late. The new version posts the notification once and lets the system count down, including on the lock screen, via setWhen, setUsesChronometer and setChronometerCountDown. Only for the length of the rest does it hold a partial wake lock, it vibrates with alarm usage when rest ends, and on tap it brings the running app forward instead of restarting it.\n\nOn platform targets, API 37 (Android 17) is what the author states the release targets, above Play's Android 16 requirement, with minimum API 29 unchanged, and edge-to-edge and predictive back were handled during an earlier redesign. Before uploading, the author says, 16 KB page alignment for native libraries was checked; the only native code found was a small AndroidX library whose LOAD segments were aligned at 0x4000, and the merged manifest's versionCode and targetSdkVersion were verified along with the upload key certificate.\n\nLegal and hosting housekeeping is covered too. The privacy policy, account deletion page and terms of use are now hosted on dotsuite.dev, and the author lists five language versions: English, Arabic, German, French and Russian. Source documents are kept in the repository under docs/legal, and a script bundles them to the site so that published text and repository cannot drift apart. Rather than being copied, shared components were extracted from an earlier app's pages, the author says. The Firebase project, which previously showed a default hosting page, now serves the update JSON uncached and redirects /privacy, /terms and /delete-account to dotsuite.dev; an older privacy policy on GitHub Pages forwards to the new one; the public-facing project name was changed from a numeric identifier to DotShredzilla; Firestore delete protection is on; and a legacy shared collection was removed, with rules now allowing nothing outside each user's own documents.\n\nFor freelancers and developers shipping Android apps, the transferable points are narrow but practical. The release-only crash is a reminder that debug builds do not exercise R8, and that transitive dependencies can carry their own minification requirements. The permission block shows that Play's automated pre-review checks can catch policy problems before a human reviewer does, and that the policy applies across every track, not just production. The Data safety mismatch is the kind of discrepancy that is easy to leave stale after features are added.\n\nThere are real limits to what this account establishes. It is a single developer's narrative about one app, with no linked Play Console output, crash logs or policy correspondence in the supplied material, and the claims about R8, Room and WorkManager versions are the author's diagnosis rather than a reproduced test. The post does not state a release date for 1.5.1 beyond saying it was in review at the time of writing, and it gives no user numbers, revenue or review outcome. The author also notes that scheduled Firestore backups need billing and will come only once real users are storing real training history, so that protection is not yet in place.\n\nThe post closes by pointing to a sixth part covering removal of forced ads, selling a Pro tier through Play Billing, and granting ad rewards only after server verification. For now, the useful signal is the checklist the author derived from this release: install the minified build on a device, read every pre-review check, keep the Data safety form, privacy policy and code consistent, and confirm what is actually live on the store before planning a version bump.",
  "category": "dev",
  "language": "en",
  "datePublished": "2026-11-20T21:18:03.081Z",
  "dateModified": "2026-11-20T21:18:03.081Z",
  "eventDate": null,
  "sourcePublicationDate": "2026-11-20T18:01:01.000Z",
  "source": {
    "name": "dev.to",
    "url": "https://dev.to/freerave/building-dotshredzilla-part-5-shipping-to-google-play-the-parts-nobody-sees-15k1",
    "kind": "community"
  },
  "practicalImpact": "Editorial interpretation: the account is a useful pre-release checklist for anyone shipping Android apps — test the minified build on a physical device, treat Play's automated pre-review checks as a real gate, and re-audit the Data safety form whenever data collection changes. The permission and version-history findings are the kind of issues that surface late and cost a review cycle.",
  "limitations": "Single first-person developer account with no linked Play Console output, crash logs or policy correspondence in the supplied evidence; the R8/Room/WorkManager diagnosis is the author's own and was not independently reproduced. No release date for 1.5.1 beyond 'in review as I write this', no user or revenue figures, and no stated review outcome. Scheduled Firestore backups are described as not yet enabled because they require billing.",
  "keyPoints": [
    "The author reports a release-only launch crash caused by R8 stripping a Room database class that arrived transitively through AdMob's WorkManager dependency, fixed by depending on a current WorkManager directly.",
    "Play's pre-review checks blocked versionCode 8 under the photo and video permissions policy because the app requested READ_MEDIA_IMAGES only for profile pictures; 1.5.1 switches to the system photo picker.",
    "The Data safety form had claimed only device IDs were collected, while the app collects workouts, weight and body measurements and uses analytics; the listing was corrected.",
    "The version live on Play was 1.2.0, with 1.3.0 and 1.4.0 never uploaded, so the release was a larger jump than the version number suggested.",
    "Updates moved to Play In-App Updates from 1.5.0, with a Firebase Remote Config minimum-version parameter that can force an update without a new release."
  ],
  "review": {
    "status": "source-reviewed",
    "checkedAt": "2026-11-20T21:18:03.081Z",
    "method": "Automated comparison against retrieved source text; not independent fact-checking.",
    "correctionNote": null
  },
  "sources": [
    {
      "id": 1,
      "url": "https://dev.to/freerave/building-dotshredzilla-part-5-shipping-to-google-play-the-parts-nobody-sees-15k1",
      "publisher": "dev.to",
      "title": "Building DotShredzilla (Part 5): Shipping to Google Play, the Parts Nobody Sees",
      "publishedAt": 1795197661000,
      "fetchedAt": 1795209454541,
      "hash": "7c99db749a17d2d2047885cfe7b56b63dd78cac8ada28f527e14e2620166e975",
      "kind": "community"
    }
  ],
  "claims": [
    {
      "claim": "The author says the minified release build crashed on launch with a WorkDatabase instantiation failure, while debug builds had not.",
      "source": 1,
      "id": "claim-1",
      "url": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf#claim-1"
    },
    {
      "claim": "The author attributes the crash to AdMob pulling in WorkManager 2.7.0 with Room 2.2.5, whose database class is created by reflection and stripped by R8.",
      "source": 1,
      "id": "claim-2",
      "url": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf#claim-2"
    },
    {
      "claim": "Play's pre-review checks blocked versionCode 8 under the photo and video permissions policy over READ_MEDIA_IMAGES used for profile pictures.",
      "source": 1,
      "id": "claim-3",
      "url": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf#claim-3"
    },
    {
      "claim": "Version 1.5.1 switches to the system photo picker, which needs no storage permission and grants access only to the chosen image.",
      "source": 1,
      "id": "claim-4",
      "url": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf#claim-4"
    },
    {
      "claim": "The Data safety form had claimed only device IDs were collected, while the app collects workouts, weight and body measurements and uses analytics.",
      "source": 1,
      "id": "claim-5",
      "url": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf#claim-5"
    },
    {
      "claim": "The version live on Google Play was 1.2.0, and 1.3.0 and 1.4.0 had never been uploaded.",
      "source": 1,
      "id": "claim-6",
      "url": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf#claim-6"
    },
    {
      "claim": "From 1.5.0, updates use Play In-App Updates, with a Firebase Remote Config min_supported_version_code parameter forcing a full-screen update.",
      "source": 1,
      "id": "claim-7",
      "url": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf#claim-7"
    }
  ],
  "formats": {
    "html": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf",
    "markdown": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf.md",
    "json": "https://freelancenews.online/news/android-workout-tracker-s-play-store-release-log-details-r8-crash-and-f61366cf.json"
  }
}