Buen Día is live on Google Play. It took two trips through review, and the first one failed for a reason I should have caught myself: the app froze on the kind of low-end device Google's reviewers use.
Try 1: rejected for "keeps crashing"
On November 19, Google rejected Buen Día 1.1 (build 4) under the Broken Functionality policy: "The app opens, but it keeps crashing." The rejection email included one screenshot. It showed the Se Regalan Dudas show page, a spinner saying "Loading episodes…", and Android's "Buen Día isn't responding" dialog.
It wasn't a crash. It was an ANR (Application Not Responding). That podcast's RSS feed is 4.1 MB, and build 4 parsed it with regular expressions on the main thread. On my phone that's a short stutter. On the low-memory virtual devices Play reviews with, which have no on-device AI hardware, it took long enough for Android to declare the app dead.
None of my testing caught it, because I tested on fast hardware with plenty of memory.
What changed in 1.2
The main-thread fixes were already in progress on my other laptop the same day. Release 1.2 pulled them together:
- RSS parsing moved off the main thread and was rewritten as a linear scanner, capped at the 250 most recent episodes.
- Artwork is decoded at the size it's shown (96–512 px), not at the full 3000×3000 cover.
- Disk writes go to a background queue. HTTP requests got timeouts.
- A fallback for phones without on-device Spanish speech recognition. The reviewer's device has none. Instead of an error, the episode plays in 15-second audio stretches, with Repeat, Slow and Driving Mode still working.
- No permission prompt at launch. Android's speech service needs the audio permission even though Buen Día only reads the downloaded episode file. The app now asks, with a one-line explanation, the first time an episode is transcribed.
- No accidental device filter. Locking the screen to portrait had made Play hide the app from Chromebooks, desktops and XR headsets. The portrait screen is now marked optional.
Then I did what I should have done the first time: I created an emulator with the same constraints as Play's review device (2 GB RAM, 256 MB heap, Play Store system image, no AICore) and ran the minified release build on it. I opened Se Regalan Dudas and tapped around while it loaded. There was no ANR, and the Java heap peaked at 42 MB.
Try 2: approved in about three hours
Build 7 went to Google Play review on November 20 at about 10 pm Central. It was approved and live on Google Play by 1 am.
The timeline
| When (Central) | What happened |
|---|---|
| Nov 17, 10:14 pm | First 1.2 feature lands: Driving Mode prepares the English translation in the background |
| Nov 19 | Google rejects 1.1 (4): ANR on the Se Regalan Dudas show page |
| Nov 19, 10:07 pm | 1.2 (6) on Play internal testing after a full release review |
| Nov 20, ~9:00 pm | iOS 1.2 (6) uploaded; Apple rejects the binary (ITMS-90208, see below) |
| Nov 20, 9:50 pm | 1.2 (7) on Play internal testing (portrait fix and permission change added) |
| Nov 20, ~10:00 pm | 1.2 (7) sent to Google Play production review |
| Nov 20, 10:05 pm | iOS 1.2 (7) uploaded to TestFlight |
| Nov 21, 12:58 am | 1.2 (7) live on Google Play |
From the first 1.2 commit to live on Google Play took just over 3 days. From cutting 1.2 to live took 27 hours. Review itself took about 3 hours.
How long the builds took
| Build | Step | Time |
|---|---|---|
| 1.2 (6) | Android: 103 unit tests + R8-minified release build | 3 min 6 s |
| 1.2 (6) | Android: tests + APK + iOS Kotlin compile check | 9 min 28 s |
| 1.2 (6) | Android: signed AAB build + upload to internal | ~2 min |
| 1.2 (6) | iOS: archive | failed twice: a Swift protocol mismatch, then an expired Xcode sign-in |
| 1.2 (7) | Android: 103 unit tests + R8-minified release build | 3 min 9 s |
| 1.2 (7) | Android: signed AAB build + upload to internal | ~1.5 min |
| 1.2 (7) | iOS: clean Release archive (4 min 53 s of it compiling the Kotlin framework) | 5 min 12 s |
| 1.2 (7) | iOS: archive + upload to TestFlight (warm) | ~2 min |
Builds are minutes. Everything else is hours or days: noticing a rejection, figuring out what the reviewer saw, and waiting on review.
The iOS side had its own retry
Apple bounced iOS 1.2 (6) with ITMS-90208: a bundled framework "does not support the minimum OS version." The cause was ONNX Runtime, which runs Buen Día's on-device neural English voice. It ships as a static library, so its code lives inside the app binary. Xcode 26.5 still adds an empty placeholder framework to the app. That placeholder declares iOS 15.1 but is built for iOS 26. A build step now removes the unused placeholder, and 1.2 (7) is in TestFlight.
What I'm doing differently
- Test on the reviewer's device, not mine. Every Play release now runs on a 2 GB / 256 MB-heap emulator with no on-device AI, using the minified release build, before it goes to review.
- Every on-device model needs a fallback. If speech recognition, translation or the neural voice isn't available, the app still has to do something useful.
- Measure releases, not builds. Build 6 never reached production review; it was superseded by 7. The number that matters is how long it took the 1.2 functionality to reach users. That led me to a stricter way of naming releases.






