E01 — EasyTallys: прежний ответ разработчика и запись об отправке Дата русского перевода: 13 сентября 2026 г. Время сохранения оригинала (UTC): 2026-09-12T15:40:59.124Z Тип материала: Документ разработчика Это сохранённые локальные заявления разработчика. Утверждения этого документа об отправленном Release-бинарном файле или метаданных App Store не сопоставлены независимо с загруженным архивом или квитанцией Apple. Переведены пояснения и сведения о происхождении материалов. Код и снимки экрана оставлены на языке оригинала; русские тексты не заменяют исходные свидетельства и не означают нового одобрения Apple. Проект: AppleLedger Файл: AppStoreAssets/submission/GUIDELINE_5_6_RESPONSE_EN.md Выбранные строки: 1–17 Выдержка с исходными номерами строк; выбранные строки сохранены без изменений. SHA-256 полного исходного файла: 04dfa389f217c2659f02d6cf1af820d647e7fb1c4a7a0ef228bb83cfd1126120 SHA-256 выдержки с номерами строк: b16507111ff0949a1c6012b2071b718c574ecc1bab03f7d6c62fab5dada50c57 1 | # Guideline 5.6 Resolution Center Response 2 | 3 | Thank you for identifying this issue. We reviewed the rejected build and found that the production app target incorrectly retained an internal screenshot workflow. That workflow included launch arguments and environment variables that could inject sample records, force a local data store, bypass the privacy lock, and simulate iCloud or App Group availability. We understand that retaining this behavior in a production build was inappropriate and could appear intentionally hidden. 4 | 5 | The new build removes that workflow completely: 6 | 7 | - All screenshot-only data creation, deletion, and injection code has been removed. 8 | - All forced-local-store launch arguments and environment variables have been removed. 9 | - All privacy-lock and automatic-lock bypasses have been removed. 10 | - All simulated iCloud and App Group status results have been removed. 11 | - All language- or region-based app-icon switching, the English alternate icon, and the related system-switch prompt have been removed. Every user now receives the same primary "好记" icon. 12 | - Ledger, account, transaction, collaborator, and cold-wallet screens now display only data actually created and stored by the user. 13 | - The submitted Release binary contains no screenshot route, language override, demo-data, forced-local-store parameter, or alternate app icon. 14 | 15 | The app does not hide or reveal features based on reviewer identity, date, region, device, build source, or server configuration. App Review and all users now execute the same Release code path. All features are accessible through the normal user interface, and the App Store description and screenshots explicitly disclose shared ledgers and the on-device cold wallet vault. 16 | 17 | No backend account is required. iCloud and shared-ledger features can be tested on a device signed in to an Apple ID. Проект: AppleLedger Файл: README.md Выбранные строки: 143–164 Выдержка с исходными номерами строк; выбранные строки сохранены без изменений. SHA-256 полного исходного файла: b6e872e127759a760d75f34c142123d3215189c9f8418d289fffb924189c9318 SHA-256 выдержки с номерами строк: d5e772387b59a78bad0f0fe71ccc3123f1e631c7495cd5666b731b6e6cfb4f6b 143 | Hello App Review Team, 144 | Thank you for reviewing our app. 145 | As explained in our response dated August 11, we investigated the previous rejection and identified an internal screenshot-production workflow that had been mistakenly retained in the production target. We understand why the presence of that workflow could have appeared to be hidden behavior. 146 | We have now submitted a corrected iOS binary: 147 | Version 1.0.2 (Build 1.0.1) 148 | This build supersedes the previously rejected binary and includes the following remediation: 149 | - All screenshot-only sample-data creation, deletion, and injection code has been removed. 150 | - The Release binary contains no screenshot route, demo-data parameter, forced-local-store parameter, language override, privacy-lock bypass, or automatic-lock bypass. 151 | - All simulated iCloud and App Group results have been removed. The app now displays only the actual status reported by Apple system services. 152 | - No alternate app-icon switching is available in the Release build. Every user receives the same primary “好记” icon. 153 | - Ledger, account, transaction, collaborator, and cold-wallet screens display only information created and stored by the user. 154 | - The app does not change, hide, or reveal functionality based on reviewer identity, date, region, device, build source, network response, or server configuration. 155 | - App Review and all users execute the same Release code path. 156 | EasyTallys (“好记”) is a local-first personal and family bookkeeping app. It has no developer-hosted account or backend, no advertising, no third-party analytics, no remote feature configuration, no in-app purchases or paywall, and does not download executable code or configuration that changes its functionality. 157 | Ledger data is stored on the user’s device. If the user enables iCloud, ledger data is synchronized only through Apple CloudKit under the user’s own Apple ID. No developer-provided login credentials are required. 158 | All features are accessible through the normal user interface: 159 | - Bookkeeping features are available from Overview, Transactions, Accounts, Budgets, Reports, and Library. 160 | - CloudKit shared-ledger features are available under Library > Sharing. Testing requires a device signed in to an Apple ID. 161 | - The on-device Keychain vault is available under Library > Cold Wallets. It only stores information manually entered by the user in the current device’s ThisDeviceOnly Keychain. It does not create cryptocurrency wallets, connect to blockchain services, perform transfers or trading, or upload vault information to any server. 162 | These features are also disclosed in the App Store description, screenshots, and Notes for Review. 163 | We respectfully request that App Review evaluate Version 1.0.2 (Build 1.0.1). 164 | If App Review still observes behavior associated with Guideline 5.6 in this corrected build, could you please identify the specific feature, navigation path, review steps, device conditions, or provide a screenshot of the observed behavior? This information would allow us to reproduce and address the concern immediately.