An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

Hello Apple Developer Community and App Review Team, I received a Pending Termination Notice regarding Section 4.3 (Spam) for my games (Scream Bird and Hopscotch). I submitted a formal appeal 7 days ago detailing the technical context, but I have not yet received an automated confirmation email or a case tracking number. Full Context of My Situation: I had previously published a game called "Scream Bird" on this account, and that was the first time I received a 4.3 Spam error. It was the first time I'd encountered this error, as all my games and applications are designed by me, from the buttons to the characters and gameplay. When I received that error, I tried to understand and modify my game a bit, thinking it might have overlapped with an existing game. But that build continued to receive the 4.3 Spam error. This time, I really didn't know what to do. I intended to keep the gameplay but redesign everything. Strangely, while I was trying to redesign and change my game, I received an email saying that Apple was reviewing my app (the one that had just been rejected), and just minutes later, my game was approved and ready for distribution. This was the first time I'd encountered something like this. I thought the review team had re-evaluated my game and changed their minds. And since the game was approved, I didn't know what else to do and just continued working on other projects. Shortly after, Google AdMob approved it (because the game was already live on the store), so ads started appearing on the game (I think this was the issue, causing the system to automatically think my game had been flagged for content changes, but the content was already there; it was just that I had set a production ID for the ads at the time, so they weren't showing – that was partly my fault). But the problems didn't end there. Recently, I published a new game called "Hopscotch" and encountered the 4.3 Spam issue again. It was then that I really looked back at the binary files I built for my games and was shocked to realize that this might be the reason the automated system incorrectly flagged my games as spam. Technical Explanation (Godot Framework & Shared Native Libraries): I build all my games myself using Godot (3.x and 4.x). Regardless of the version, I write supporting libraries (mainly to call simple native features). Therefore, all my games will have files like: notch.a, share.a, haptics.a, local-notification.a, inappstore.a... You can check it out on my GitHub page; most of it is public. https://github.com/kyoz/godot-notch https://github.com/kyoz/godot-share https://github.com/kyoz/godot-local-notification https://github.com/kyoz/godot-haptics https://github.com/kyoz/godot-leaderboard https://github.com/kyoz/godot-native-rating https://github.com/kyoz/godot-flashlight etc... However, the entire game, from images, models, scenes... almost everything I designed myself, was packed into a single [game].pck file by Godot. This makes my Godot-built games look very similar in terms of binary, but in terms of content and gameplay, they are completely unrelated. My Commitment: I've been on my Apple journey for over five years now, and I've published 20 apps/games. The journey so far hasn't been easy. But I promise I've always complied with Apple's policies. I have never engaged in subscription scams, fake reviews, bait-and-switch tactics, or any of the fraudulent conduct described in the termination notice. I am respectfully requesting: Confirmation if my appeal submitted 7 days ago is actively under review by the App Review Board. A status update or Case Reference Number for tracking. I am fully cooperative and ready to provide full source code, Godot project files, or any documentation needed. Thank you so much for your time and assistance! Best regards, Phan Minh Cuong

Hi everyone, My app E-Forward (v4.4.10) has been in Waiting for Review for a week now, which is longer than the usual turnaround I've seen. I haven't received any messages requesting more information, and everything in App Store Connect looks complete on my end. Has anyone experienced a similar delay recently? And if any Apple staff happen to see this — I'd greatly appreciate any guidance on the status or on what I can do to help move things along. Thank you!

Hello, I'm experiencing a very unusual issue with App Store Connect and would appreciate any advice. Timeline: I submitted version 1.1.2 of my macOS app "Wallpets" for review. I received the notification that the app status changed to "In Review". Shortly after that, App Store Connect became completely inaccessible. A few minutes later, I received another notification that the app was "Rejected". However, App Store Connect is still unusable. Submission ID: 956a336e-1862-4abe-9bbd-c700a654f3df Current symptoms: • On the App Store Connect website, the Apps page displays: "Sorry, something went wrong. Try your request again." and it incorrectly shows "No Apps", even though my app has existed for some time. • The App Store Connect iOS app displays: "App Store Connect is currently unavailable." • TestFlight on macOS also reports: "TestFlight is currently unavailable." • The "View in App Store Connect" link from the rejection email also fails because App Store Connect cannot load. I can still log into my Apple Developer account and the Apple Developer website works normally. The issue only affects App Store Connect and TestFlight. Has anyone experienced this before? Is this likely to be: a temporary App Store Connect backend issue, an account-specific problem, or something that can happen after an app review rejection? I've attached screenshots showing: The review status notifications. The App Store Connect website error ("No Apps"). The App Store Connect iOS error. The TestFlight unavailable error. Any suggestions would be greatly appreciated. Thank you. Update: This issue started immediately after my app entered review, before I received the rejection notification. Additional information: I can successfully sign in to developer.apple.com. Certificates, Identifiers & Profiles are all accessible. The issue only affects App Store Connect and TestFlight.

I’m seeing an App Store Connect / StoreKit product-availability issue for a universal iOS + macOS app. Product ID: com.vincentchu.VideoAtlas.pro.lifetime The product is a one-time, non-consumable lifetime purchase. Current state: Both iOS and macOS apps are approved. The IAP status is Approved. I waited more than 24 hours after IAP approval before retesting. The IAP is configured for the universal app, is available in 175 storefronts, and has an effective price. Paid Applications agreement, tax, and banking are active; this account already has other paid apps. In-App Purchase capability is enabled for both targets. The product ID exactly matches the App Store Connect product ID. Production schemes have StoreKit Configuration: None. iOS is tested from TestFlight, so it uses StoreKit sandbox. macOS is tested from a development-signed build against sandbox, also with no local StoreKit configuration. The app uses StoreKit 2: let products = try await Product.products( for: ["com.vincentchu.VideoAtlas.pro.lifetime"] ) The call does not throw an error, but returns an empty array on both platforms: StoreKit product request completed productIDs=com.vincentchu.VideoAtlas.pro.lifetime returnedCount=0 returnedProducts= StoreKit returned no products for requested productIDs= com.vincentchu.VideoAtlas.pro.lifetime As a result, the app cannot retrieve Product.displayPrice or offer the purchase. I have already followed "TN3186: Troubleshooting In-App Purchases availability in the sandbox", including checks for product identifier, bundle identifier, IAP capability, provisioning/signing, StoreKit configuration, sandbox testing, paid-app agreements, IAP approval, pricing, and storefront availability. Since this is an empty result rather than an error, and it persists more than 24 hours after approval on both TestFlight and macOS sandbox, is there an additional App Store Connect-side configuration or Apple-side issue that could cause an approved non-consumable IAP not to be returned by Product.products(for:)? Thanks.

Hello Applet, I’m experiencing an issue with StoreKit on a TestFlight build. My app uses auto-renewable subscriptions through StoreKit and RevenueCat. Configuration already verified: App installed through TestFlight (not debug). Bundle Identifier: com.ciborgu.vytalai Paid Applications agreement is active. In-App Purchase capability is enabled. Three auto-renewable subscriptions exist in App Store Connect. Product IDs match exactly between App Store Connect, RevenueCat and the application. RevenueCat initializes successfully. A Sandbox test account has been created. Tested on a physical iPhone. Device restarted and app reinstalled from TestFlight. VPN and iCloud Private Relay disabled. When attempting to purchase a subscription, the Apple payment sheet never appears. Our diagnostics indicate that StoreKit does not return any available products for the configured Product IDs, preventing the purchase sheet from opening. Expected Product IDs: vytalai_premium_monthly vytalai_premium_yearly vytalai_premium_yearly_intro Could you please verify if there is any issue with the App Store Connect configuration, StoreKit availability, or the processing state of these subscriptions on Apple’s side? If additional logs or diagnostics are required, I can provide them. Thank you. I have already contacted Apple Developer Support regarding this same issue. Previously, I was advised to schedule a technical support meeting. However, when I requested the meeting, my request was declined because of the subject of my issue, so I was unable to speak with an Apple engineer. Since I have now completed all the recommended troubleshooting and the issue still persists, I would greatly appreciate it if this case could be reviewed by the appropriate technical team or a StoreKit engineer. Thank you for your assistance.

I'm submitting a new version of my app, and after click "submit for Review", it show that: A few more items are needed in order to submit for review The items listed below are required for submission:There are still screenshot uploads in progress. I didn't met this problem before. Is that mean I haven't upload all the screenshot required or it's still uploading the screenshots to App Store Connect's server? Cause before there is a "save" button after you drag images to the screenshots area, now you don't. And I think I have uploaded all the screenshots needed and I waited a day to try submit again, still the same. What should I do?

Hello, I’m posting a new thread in case anyone has seen this before. My Apple Developer Program membership is paid and should remain active until March 10, 2027, but my account suddenly lost access to membership-related resources. Current symptoms: developer.apple.com/account shows “Join the Apple Developer Program” In Certificates, Identifiers & Profiles, I get: “Team ID is not associated with an active membership.” A few weeks ago, I received a “We need more information” email asking for ID and proof of address. I did upload the requested documents, and after contacting Developer Support in China, I uploaded them again as a second submission. Developer Support in China has confirmed that the issue is related to an additional identity verification review, and that my second submission was forwarded to the relevant internal team. My Team ID is: 84FV5VNGS2 My China Developer Support case number is: 102922928162 But after about 3 weeks, the account is still not restored. Has anyone had a similar case? If so: how long did it take? did Apple manually restore the membership / team linkage? was there anything else you needed to do besides waiting? Any similar experience would be appreciated. Thank you.

Hello everyone, I am experiencing a similar issue to the one reported by aarshps: "I hope someone has encountered this specific pattern and resolved it, or can point me in the right direction to escalate the issue." In my case, my iOS Apple Developer account (Case ID: 102929769930) has been pending for 40 days. I have met all of Apple's requirements, but support staff stated they could not verify my subscription or enrollment. The only potential detail on my end is that the payment was made using my son's credit card (Felipe Silva Ferraz), while the developer account was registered under my own name (Ademir Gomes Ferraz). I have sent multiple emails through the support portal, and my account still hasn't been approved. If anyone has faced this pattern or knows how to properly escalate it, please let me know.

Hi everyone, I'm hoping someone from Apple or another developer has seen this before because I'm completely blocked from submitting my first auto-renewable subscription. Setup First app submission App version: 1.0 (Build 34) One auto-renewable subscription Five consumable IAPs Everything configured in App Store Connect StoreKit works correctly in TestFlight Subscription purchases complete successfully in TestFlight RevenueCat configuration has been verified Subscription review screenshot is uploaded and processed successfully Problem App Store Connect shows: "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." The draft contains: App Version 5 Consumable IAPs 1 Subscription When I submit through the App Store Connect API I receive: STATE_ERROR.SUBSCRIPTION_SUBMISSION_REQUIRES_GROUP_VERSION A subscription must be submitted with its subscription group version when the group has no prior approved version. That makes sense because this is my first subscription. However, when I attempt to create a subscription group version I receive: STATE_ERROR.ALREADY_EXISTS Version already exists. There is already an inflight version with id: bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a So I then attempted to add that existing SubscriptionGroupVersion to the review submission. Apple responds with: STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_NOT_SUPPORTED Subscription group version bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a is using an older format that is not supported for review submission. Please update before submitting. and also: STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_INVALID_STATE Subscription group version bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a cannot be submitted. Only versions in Prepare for Submission or Developer Rejected can be submitted. The issue I'm now stuck because: Apple says I must submit a SubscriptionGroupVersion. Apple says one already exists. Apple will not allow me to create a replacement. Apple will not allow me to submit the existing one. Apple says the existing one is using an older format. I cannot find any way in App Store Connect to update, replace or delete this SubscriptionGroupVersion. Things I've already verified Build 34 is attached correctly. Subscription Product ID is correct. RevenueCat configuration is correct. StoreKit loads the subscription successfully. Purchases work in TestFlight. Subscription review screenshot exists and is COMPLETE. Localizations, pricing and availability are all configured. The issue occurs both in App Store Connect and when submitting via the App Store Connect API. Question Has anyone encountered this before? Is there a way to regenerate or migrate a SubscriptionGroupVersion into the new format from App Store Connect, or is this something Apple Developer Support has to reset on the backend? Any advice would be greatly appreciated. Thanks!

I'm building my first mobile app with a developer, and I'm trying to understand the full App Store publishing process before making a decision on how to move forward. Another developer I'm considering working with instead of my current developer told me the following: "If you do it yourselves, your developer will have to learn everything for the first time. Registering a business and getting the corporate key takes about a week, getting a D-U-N-S number can take up to a month, rebuilding a web app into a mobile UI is a skill in itself, Capacitor is a skill, push notifications can be very challenging, then there's App Store compliance, submission, possible rejection and resubmission. You'll also realistically need a Mac to publish to the App Store. Overall, expect 2–3 months and well over $2,000 before you might be on the App Store." My situation is: I'm a solo founder. The app already exists as a web app. We plan to wrap/build it into a native mobile app (likely using Capacitor or a similar approach). I'm happy to publish under an individual Apple Developer account for now if that simplifies things. I don't necessarily need an organization account at this stage. My biggest priority is speed. I'm not trying to build the perfect long-term company structure right now. I want to get my app into people's hands as quickly as possible so I can validate the product, learn from real users, and iterate. If there are trade-offs that let me launch faster without creating major technical debt or problems later, I'm very open to that. I'm hoping to understand from developers who have actually been through this process: Which parts of the statement above are accurate? Which parts only apply if you're publishing as an organization rather than an individual? Is 2–3 months a realistic estimate for someone who already has a working web app and an experienced developer? If your goal was simply to get an MVP into users' hands as quickly as possible, how would you approach it? Are there any hidden hurdles or costs that first-time founders commonly underestimate? Also for better context: this developer who made this comment to me said they're charging $1100 AUD to ONLY convert our web app into a mobile app. They also proposed a $450/month retainer after the migration for maintenance, tweaks, etc. I'd really appreciate hearing from anyone who's published apps to the App Store recently. Thanks!

102940998310 im dealing with a fraud problem with one studio and several games my support case is above and it has been over 8 days waiting and thats just this year. I started in 2020 and even designed an iPhone model

Hello, My app was reviewed and rejected on June 26, 2026 (3:48 PM). I fixed every issue mentioned by the App Review team and submitted a new build. After about one week, the app was still stuck in "Waiting for Review" and had never moved to "In Review." Thinking there might have been an issue with the submission itself, I canceled it and submitted it again. Submission ID: 0e03f336-27f3-42d0-9d15-a0df4e8ac77a Unfortunately, even after re-submitting, the app is still in "Waiting for Review", and I haven't received any communication explaining the delay. Has anyone experienced a similar situation? If so, how did you get the review process moving again? Any guidance would be greatly appreciated. Thank you.

I paid the $99 annual Apple Developer Program fee and submitted my first iOS app with the understanding that App Review would normally take approximately one or two days. It has now been six days, and the submission is still sitting in “Waiting for Review.” There has been no review, no request for additional information, no explanation, and no indication that anyone has looked at it. I understand that review times can vary, especially for a first submission, but six days without even entering review seems excessive. Developers are required to pay Apple before they can distribute an app, yet there appears to be no meaningful service-time commitment or communication when a submission remains untouched. Is this currently normal for first-time app submissions? At what point is a developer supposed to conclude that the submission is stuck rather than merely delayed? At this point, I am also wondering whether I should request a refund of the $99 membership fee, since the primary service I paid to access has not been provided within anything resembling the expected timeframe.

I’m having an issue with the Apple Developer Program. I received a notification that the Apple Developer Program License Agreement has been updated and must be accepted in order to continue submitting and updating apps. The problem is that after signing in to my Apple Developer account, I don’t see any option to accept the new agreement. Instead, I’m shown a “Join the Apple Developer Program” screen, as if I’m not enrolled in the program, even though I have active apps on the App Store. In App Store Connect, I can see the agreement status as “Active (New Agreement Available)”, but there is no visible way to actually review or accept the updated version. Has anyone experienced a similar issue and knows how to fix it?

Hello, I am facing a critical issue with my Apple Developer Account verification process where an automated timer suspended my account despite submitting all requested documents on day one. Timeline & Details: I received a request from Apple to upload address verification documents with a 14-day deadline. I uploaded all requested documents on the very first day. While waiting for the review process to be completed on Apple's end, the 14-day window expired. Consequently, the system automatically suspended my account, disabling certificate creation and blocking development/distribution. I have open support tickets, but have not received a response yet. Case ID: 102944887663 Since this is an automated timeout caused by review delay, could someone from the Apple team please help escalate this Case ID to the Enrollment / Account Verification team? Thank you very much for your help!

Hi everyone, I’m currently stuck with a blocking issue in App Store Connect and would really appreciate any guidance or insight. Issue: My app version (iOS App 1.0) is missing the “In-App Purchases and Subscriptions” section entirely. Because of this, I cannot attach my subscriptions to the version, which is preventing me from submitting the app for review. Additionally, I also do not have the option to create a new version, so I can’t work around the issue by moving to 1.0.1. What happened before this: I uploaded a build (Build 24) Submitted the app for review Then removed the submission After that, the IAP section disappeared completely Since then, I cannot attach subscriptions or create a new version Current state: Subscriptions are created and show “Waiting for Review” New Build is attached to Version 1.0 All metadata and screenshots are complete “In-App Purchases and Subscriptions” section is missing “Add Version” option is not available What I’ve tried: Removing and re-adding the build Waiting for UI refresh/processing Contacting Apple Developer Support (case has been escalated for 6 days with no response) Impact: This is currently blocking my app launch because I would be rejected since the subscriptions are not linked, as I cannot submit my first subscription with the app. Questions: Has anyone experienced a missing IAP section after removing a submission? Is there any way to force reset the app version state from the developer side? Is this a known App Store Connect issue? Any help or suggestions would be greatly appreciated. Thanks in advance.

We currently have version 1.2.0 live and in the middle of its 7-day phased release (automatic updates), currently around the 5% stage. We now want to submit version 1.3.0. I want to confirm the exact behavior before we submit, because I've heard conflicting claims internally. My understanding is: Submitting 1.3.0 for review does NOT affect 1.2.0's ongoing phased release. 1.2.0 continues ramping (10% -> 20% -> 50% -> 100%) undisturbed while 1.3.0 is in review. If 1.3.0 is set to "Manually release this version," it will sit in "Pending Developer Release" after approval and still not affect 1.2.0's rollout -- nothing changes until I actively release it. Only when I tap "Release" on 1.3.0 does 1.2.0's phased release stop, at which point 1.3.0 begins its own phased release from 1%. If 1.3.0 were instead set to "Automatically release this version," it would go live the moment Apple approves it and would interrupt 1.2.0's rollout at that point. Questions: Is the above correct? Specifically, does the act of submitting/approving a new version have any effect on the currently live version's phased rollout, or is the rollout only ever interrupted by the release action? When 1.3.0 is released and 1.2.0's phased release is interrupted, what happens to the users who had not yet received 1.2.0 via automatic update? Do they get queued for 1.3.0 instead? Thanks in advance for clarifying.

My iOS app's first submission (ThymeBlock, Apple ID 6779269775) was rejected under 2.3.2 solely over the OPTIONAL promotional images on my two auto-renewable subscriptions. The required fix, deleting the images, was impossible: both subscription records were locked in "Waiting for Review" and the image field disabled. My reply in the submission thread went unanswered for 48+ hours, so I cancelled the submission (standard advice). The cancel completed, no submission exists anymore, and both subscriptions REMAIN locked in "Waiting for Review", held by nothing. I cannot edit them and cannot delete the flagged images, so resubmitting the app version cannot satisfy the rejection: the change App Review required is impossible to make. Developer Program Support has so far responded with unrelated information, and on a call suggested the subscriptions are in review due to "pending charges from July 18", which seems impossible since the app has never been released and has zero customers. This matches threads 705460 and 717024 (same lock; resolved only by Apple server-side). Case number: 20000117635283. Could App Review or App Store Connect staff release my two subscription records to an editable state, or remove the two promotional image as the rejection requested?

Hello, I am experiencing a persistent TestFlight installation issue affecting multiple unrelated apps under the same Apple Developer account. For all affected apps: Builds upload successfully to App Store Connect Processing completes normally Builds appear in TestFlight Internal and external testing can be enabled Public links generate correctly However, when attempting to install the app via TestFlight, the installation fails with the error: “The requested app is not available or doesn’t exist.” This occurs: For internal testers For external testers Across different Apple IDs Across different devices With newly created apps After incrementing build numbers After re-uploading builds After signing out/in of TestFlight After regenerating provisioning profiles After creating entirely new app entries The issue currently affects: • TubeChat AI – Apple ID 6752591427 • Vibex – Apple ID 6756860663 • vigilAI – Apple ID 6757738356 Since multiple unrelated apps are impacted in the same way, this appears to be an account-level or App Store Connect backend issue rather than a code signing or project configuration problem. Has anyone encountered a similar situation where TestFlight distribution fails across all apps within a developer account? Any guidance would be greatly appreciated.

Hello, We are a registered software company and have been unable to publish our iOS game for approximately three months because of repeated rejections under Guideline 4.3(a). The first rejection stated that our app shared a similar binary, metadata, and/or concept with apps previously submitted by a terminated Apple Developer Program account. Later rejections repeated similar general wording but did not identify the application, account, source-code component, asset, SDK, metadata element, or design considered similar. Our game is an original Unity project developed by our own team for more than two years. It was not purchased as a template, cloned, reskinned, or repackaged from another application. We possess the complete Unity project, client and server source code, Git development history, design source files, custom assets, backend infrastructure, and all related project files. Our core code, game systems, UX/UI design, and custom visual work were created by our team. Any limited third-party assets or SDKs used by the project were obtained from legitimate sources, and the relevant licenses and purchase records are available. The game also includes substantial custom functionality: • A server-authoritative real-time multiplayer architecture developed by our team • A 51-point opening rule that forms the core of every match • Custom scoring and penalty rules for plays made on other players’ opened tile groups • Matchmaking, table management, reconnect, timeout, and authoritative game-state recovery systems • Multiple game modes and competitive tables • Tournaments and leaderboards • Friends, private messaging, in-game chat, and direct table invitations • Player progression, daily rewards, missions, collectible profile icons, and virtual gifts We use only one Bundle ID and one App Store Connect record. We have not submitted duplicate versions of this application through multiple Bundle IDs or unrelated developer accounts