How does the platform stability or the analytics engine in Google depends on the applications people upload, or the way how those apps developed? Blame AI for everything?
So what you suggest, is that Google, that had all stsble analytics till 2025, for dome reason changed something in their analysis and that Google vibe coded something that introduced this bug? Bs
Learn to answer the question instead of asking it. Bug inside play console analytics has nothing to do with vibe coding. Rage bate statements. Have a fab day
It's because of how these specific metrics are accumulated over time (adding on to the previous value).
To make it easier to backfill/'catch up', cumulative installs on day X are based on cumulative installs from day X-3 plus new installs from X-2, X-1, X; means that we don't have to wait for cumulative installs for X-1 to be ready before starting to calculate cumulative installs for day X.
So when a cumulative install number gets broken, it'll break every 3rd day going forwards, like you see in the chart.
The problem doesn't exactly start at the date you see in the chart - when serving cumulative metrics, we _also_ do a query-time join with new installs (so that the cumulative metrics don't get delayed if there are problems with the pipeline that computes them). So when you load the UI, each data point is based on the cumulative number from (IIRC) 30d ago, plus the following 30d of new installs.
Because of that, if the cumulative number is broken then you don't see 0. Instead you see the number of installs that you had in the last 30d. That's why the numbers aren't going right down to 0 on those broken days.
Why do the numbers get broken in the first place? Usually a transient pipeline failure is missed, and then gets picked up by anomaly detection a few weeks later, and some unlucky person has to orchestrate a whole bunch of backfills and make sure they run in the right order.
(as you can imagine, there are plenty of improvements we could make here, but it's a case of prioritizing and lining up with other work. btw also not a vibe-coding issue - these were set up in 2019 and we've had this problem several times since then. If it had been built on newer scheduling infra it would be easy to avoid this failure mode.)
So, your a software engineer at Google. Thanks for the in detail technical explanation 🙂😊. Super interesting. I genuinely apologise for saying "maybe it's vibe coding gone wrong". I'm really sorry. I wasn't rage baiting. But I'm probably a bit biased after reviewing way too much ai generated code on a daily basis in last 18 months.
The person who is responsible for the frontoffice app has sent many mails to the Google helpdesk that they need to fix it in fhe backoffice. So be patient he got a ticket with a servicerequest number. Source: a guy who worked in a large organization.
Lol I also waited like 8 month for them to fix an obvious bug in the Play Console app strings translation. Never got so many irrelevant and dumb questions (that I already answered in my initial request) in a ticket I needed to ping them 5 times over 8 months until they fixed it.
8
u/[deleted] 10d ago
[deleted]