SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Developer Shares How a Day-3 Crash Was Triaged During a Google Play Closed Test

0
·2 views

A developer running a Google Play closed test received a tester report that the app crashed when opening settings, with no stack trace or device details. The developer explains using Play Console's Android vitals and mapping files to get a readable stack trace, then identifying that the crash only affected Android 10 devices. The bug was a null value returned by older Android versions, which was fixed and verified on a borrowed device. The fix was shipped as a new release on the same closed track to avoid resetting the 14-day testing requirement. The article is written as a practical guide for handling crashes during closed testing.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Python 3.14 subinterpreters cut a CPU-bound job from 3.6 to 0.9 seconds, but reject concurrent calls

A developer benchmarked a CPU-bound prime-counting task in a Python 3.14 container with four cores. Four subinterpreters from the new concurrent.interpreters module finished in about 0.9 seconds, close to a single-thread baseline and far faster than four classic GIL-bound threads at 3.6 seconds. Subinterpreters performed comparably to multiprocessing in the same tests. However, a single interpreter rejects a second concurrent call with an InterpreterError rather than queuing it. The author concludes that running N tasks in parallel requires N separate interpreters, so thread-pool patterns do not carry over directly.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

SlothSort: Local AI Tool Organizes Downloads Without Deleting Files

A developer built SlothSort, an open-source Python tool that uses the locally run Gemma model via Ollama to sort cluttered Downloads folders. The agent scans text files and PDFs, suggests clearer filenames, and moves items into sensible folders, while image classification currently relies only on filenames and extensions since OCR is not yet implemented. A dry-run preview lets users check proposed changes before anything moves, and every operation is logged in SQLite so it can be undone. Because processing happens on the user's own machine, private documents never need to be uploaded to a cloud AI service. The project was submitted to a Hacktoberfest open-source AI challenge, and its next planned steps include adding OCR and a review step for uncertain classifications.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Common SaaS Development Mistakes and How Teams Can Avoid Them

Building a successful SaaS product requires more than useful features, since it must also perform consistently, protect customer data, scale with demand, and stay maintainable. Many products struggle as user numbers grow, often because of early decisions made under time pressure, such as weak planning, limited testing, poor architecture, or vague requirements. Such issues tend to become costlier to fix over time. The article outlines ten frequent pitfalls, beginning with heavy investment before confirming real customer demand, and suggests practical remedies like customer interviews and launching a minimum viable product. It also cautions that architecture choices should match the product's actual complexity and growth expectations rather than follow trends.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Shiftary Android shift planner adopts offline-first pricing with trial, lifetime and subscription options

Shiftary, a Flutter-built shift planner for Android that works offline without accounts, has been monetized without relying on a backend server in the purchase flow. Its model includes a 14-day free trial of all features requiring no card, a one-time $19.99 Lifetime purchase, and a $9.99 yearly Cloud subscription adding backup and sync. A discounted $9.99 Lifetime upgrade is offered only to Cloud subscribers. The developer describes storing the trial start date locally and within user data, always keeping the earliest date, and using Google Play as the source of truth for ownership via the in_app_purchase plugin. The article also highlights Play's three-day acknowledgment requirement for purchases and how renewal order IDs can be used to estimate subscription periods.

0 comments Read more at DEV Community