4.3(a) on an update to a live app with 30 approved versions — App ID 6776105247

Question

Created 2w

Replies 1

Boosts 0

Participants 2

Hi, NewTake — AI Video Editor (App ID 6776105247) has been on the App Store since June 2026 with 30 approved versions and paying subscribers; version 1.8.9 was approved on August 27, 2026. Version 1.8.10 (submission 5ac4e580-9634-431d-be60-c4580e775295), which differs from 1.8.9 only by an optional feedback text field, was rejected under Guideline 4.3(a) on August 28 and again on August 29 after a Resolution Center reply. Both responses were the guideline template and did not reference anything specific in the submission.

The app is a single bundle ID with an original on-device pipeline (transcription, scene detection, false-start trimming, captions — video never leaves the phone). No other app on our account shares code, assets, or concept with it. We have filed an App Review Board appeal and requested a call.

We'd be grateful for guidance on what specifically triggers 4.3(a) on an update to an already-approved app, so we can address it.

Answer 1

GetResubmit OP

2w

Since your App Review Board appeal is already pending, I would not submit another build yet.

Guideline 4.3(a) specifically concerns multiple Bundle IDs for the same app. Because this is an update to the same live Bundle ID, ask the Board to clarify whether the match involves another app record, an embedded component, your developer-account history, or an unrelated binary.

Provide a compact comparison between the approved 1.8.9 archive and rejected 1.8.10:

the Git diff and release notes,
every Bundle ID in the app and its extensions,
embedded frameworks and SDK versions,
signing team, entitlements and dependency lockfiles,
confirmation that no other app under the account shares the product, assets or code.

Then ask Apple to compare 1.8.10 directly with the approved 1.8.9 build and identify the additional Bundle ID or associated app that triggered 4.3(a).

Previous approvals do not guarantee approval of an update, but if the only product change is the feedback field and the bundle/dependency inventory is unchanged, that is much stronger evidence than another general explanation or speculative code change.