Hello Apple Developer Community, I am an independent developer and I am looking for some guidance regarding the App Review process for my app, Zivoo. The review process has been ongoing for about four months, but I still have not been able to get a clear explanation of what Apple expects me to change. The main problem now is that App Review is no longer responding to our clarification messages in App Store Connect. We have already sent detailed questions, additional explanations, information about our previous Bundle IDs, and technical supporting materials, but we have not received a response. Zivoo has never been released on the App Store. During the review process, we submitted the app under the following Bundle IDs: confident.zivoo ru.zivoo.social ru.zivoo.talk All of them belong to the same Apple Developer Team. After previous rejections and major changes to the app, we deleted the earlier App Store records because we mistakenly believed that a substantially redesigned product should be submitted under a new App Store record and Bundle ID. Previously, Zivoo was rejected under Guideline 4.3(b). After that, we significantly redesigned the product. We removed profile browsing, swipes, likes, and mutual-like mechanics. The current version focuses on language practice through active conversation rooms and AI-assisted room discovery. The latest submission was rejected under Guideline 4.3(a). The rejection says that the app shares a similar binary, metadata, and/or concept with other submissions. We asked App Review to clarify what exactly this refers to: our own previous Zivoo submissions, shared third-party SDK components, or specific code, assets, metadata, or product concepts that Apple considers similar to another app. Unfortunately, we have not received a specific explanation, and currently we are not receiving any response at all in App Store Connect. We have already provided our full Bundle ID history and a technical report showing the size and contribution of third-party SDKs. I am also ready to provide the client and backend source code, Git history, original design files, dependency information, or a live technical demonstration if that would help clarify the situation. I would really appreciate any advice from developers who have dealt with a similar 4.3(a) or 4.3(b) situation, especially when previous Bundle IDs of the same app were involved. Apple App Review has completely stopped responding to us in App Store Connect. We have sent several clarification messages with detailed technical information and questions, but have not received any response. Thank you.

Hello Apple Developer Community, I am an independent developer and I have reached a point where I genuinely do not understand what the correct path forward is. I have invested a very significant amount of personal time and money into Zivoo. The app has never been released on the App Store. Every time App Review provided feedback, I tried to address it seriously and substantially redesign the product instead of simply resubmitting the same application. The first versions of Zivoo focused on real-time social communication. Later, the app was rejected under Guideline 4.3(b) because Apple considered the experience too similar to existing dating apps. In response, we substantially redesigned the product again. Profile browsing, swipes, likes, skips and mutual-like mechanics were removed. The current Zivoo is focused on language learning and real-time language practice through active conversation rooms, AI-assisted room discovery, entry requests, live conversations, voice/video messages, reactions, shared mini-games and invitations for future practice. The application-specific code, backend, UI system, custom assets, product logic and more than 35 custom animations were developed specifically for Zivoo. We have never purchased a white-label app, cloned another application, purchased an app template or repackaged another developer's product. We do use standard third-party SDKs such as Yandex Mobile Ads, mediation SDKs, Firebase, AppMetrica, Lottie and others. During this process, we may also have made an important mistake. Previous Zivoo submissions used: confident.zivoo, ru.zivoo.social The current submission uses: ru.zivoo.talk All of these Bundle IDs belong to the same Apple Developer Team. Zivoo has never been published on the App Store, and multiple versions of Zivoo have never been publicly distributed at the same time. After previous rejections and major redesigns, we removed previous App Store records. Because the concept had changed significantly, we mistakenly believed that the redesigned product should be submitted under a new App Store record and Bundle ID. This was never intended to bypass App Review or distribute multiple copies of the same app. The current submission has now been rejected under Guideline 4.3(a), stating that it shares a similar binary, metadata and/or concept with apps submitted by us or other developers. The most difficult part of this process is that we are never clearly told what exactly is considered wrong. With each rejection, we receive a broad guideline reference, but not a specific explanation of which code, asset, metadata element, feature or concept triggered the decision. We currently see two possible explanations: Apple's systems may be matching the current submission against our own previous Zivoo submissions under different Bundle IDs. Shared third-party SDK components may be contributing to the binary similarity signal. Our technical analysis shows that standard third-party libraries represent a substantial portion of the measured build. We fully understand that this does not prove that the SDKs caused the rejection. At this point, however, I am afraid to simply make random changes and resubmit again, especially because the latest rejection also includes an Extended Review warning. I am not asking for automatic approval or special treatment. I simply want to understand what Apple actually expects us to fix. Can 4.3(a) be triggered by a developer's own previous submissions under different Bundle IDs, even if none of them were ever released? Can common third-party SDKs contribute to the similarity determination? And if Apple believes our application-specific code, assets or concept are similar to another developer's app, how can we verify or address that? I am prepared to provide client and backend source code, Git history, original design files, dependency information, build details and a live demonstration. If anyone has experienced a similar case, especially after removing previous app records and submitting a substantially redesigned version under a new Bundle ID, I would greatly appreciate hearing how it was resolved. If Apple Staff sees this post, I would be extremely grateful for concrete guidance on what exactly we should do next. Thank you.

Hello Apple Developer Community, I’m looking for guidance regarding an unusually long App Review process for my first iOS app, Zivoo. The overall review and resubmission process has now been ongoing for more than a month. During the previous reviews, we received feedback from App Review. In response, the application was completely redesigned and the latest version contains a substantially revised core experience. The latest build is: App: Zivoo Platform: iOS Version: 2.1.4 (34) Submitted: August 10, 2026 Current status: Waiting for Review The App Store description, screenshots, metadata, and Review Notes have also been fully updated to reflect the redesigned application. Detailed testing instructions have been provided for App Review. After more than a month of working through the review process, responding to feedback, redesigning the application, and preparing a new submission, the latest build is still waiting for review without any visible progress. I have also contacted App Review Status support to confirm whether any additional action is required from our side. Could someone from Apple please check whether this submission is progressing normally or whether it may require additional attention? I would also appreciate hearing from other developers who have experienced a similar delay after substantially redesigning an application following App Review feedback. Thank you for any guidance or assistance.