My account is invited to a team as admin I already accept the invitation but I can't find the team on developer.apple.com, appstoreconnect.apple.com even on XCode. My colleagues also cant find my account on the user and access tab on apple store connect but when he tried to invite me again it throw an error (A user with this email address already exists on this team.) What should I do to fix this?

Hello everyone, I’m hoping the community (and maybe someone from App Review) can point me in the right direction. I submitted my new game on 22 April 2025. The build was rejected, so I filed an appeal the same day and re‑submitted it twice after that. The appeal has shown “Waiting for Review” ever since, and I’ve never received the usual “We got your appeal” email, just the generic “We’re seeing higher volume” message. Although this is a fresh developer account, I’ve shipped 50+ apps for other organizations over the years and never ran into a delay like this, so I’m pretty sure the hold‑up isn’t about the actual build. Why it’s urgent:
Influencer promos, community streams, and some paid ads were all timed around the original launch window. After four weeks of silence people assume the game’s been cancelled, and traffic/comments are sliding fast. What I’ve tried so far: Emailed App Review → same volume auto‑reply Used the Contact Us form twice Added a short note in Resolution Center every few days If anyone from App Review sees this or if another dev has broken out of a similar appeal limbo any tip or nudge would be hugely appreciated. Thank you in advance for your time.

Hi, Since Friday 18 April 2025, around 9am, my team and I have been unable to manage one particular app in App Store Connect. Whenever we open the app’s page and try to view “General → App Information,” or when we press “Add for review” on the current iOS version, App Store Connect immediately displays “Something went wrong. Try again later.” and the content never loads. The error occurs every single time, in both Safari and Chrome on multiple Macs, while all our other apps in the same developer account behave normally. Our build and submission tooling (Fastlane) hasn’t changed for more than a year and continues to work for the rest of our apps. Every attempt to open App Information or submit the version fails. I have already opened a ticket ~1 month ago and shared all the screenshots, screen recordings and .har files but seems like really take their time to fix things. It feels like a server-side issue isolated to this single app, so any guidance or a manual unblock would be greatly appreciated.

Hello guys, I currently have a problem with Xcode cloud. When I setup a simple workflow in my Xcode project that just archives it and builds the project for TestFlight Internal testing, it will fail and give the following error: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “DropIn.app/DropIn” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. I've already been searching for solutions and double checked the documentation. My Xcode project is a simple iOS app with the app target and two other targets for tests and UI tests. I made sure the checkbox "Automatically manage signing" is ticked in all targets. The workflow has only one action "Archive - iOS" with TestFlight (Internal Testing Only) and a post-action "TestFlight Internal Testing - iOS" with an internal testing group assigned. I've seen people having similar problems where it turned out they had a non roman character in their name? This would also affect me if that's the case, since my name includes "ö". I also checked on app store connect and already deleted xcode cloud data, removed all certificates recreated the workflow, but it still gives this error. Any ideas on how to fix this?

Hello, We’re seeking urgent help or guidance regarding a serious issue with our app review process. We submitted our iOS app last month. It was rejected three times for various reasons, and each time we promptly resolved the issues and resubmitted. After the most recent resubmission (over a week ago), the app has been stuck in the “Waiting for Review” status. The last communication we received from Apple was: We’ve tried to follow up multiple times via email, as phone support is not available in our country. However, we’ve only received automated responses saying that the review requires additional time. No actual progress or update has been communicated since then. Our launch date is now critically close, and we're concerned that we may miss it due to the continued delay and lack of visibility into the review timeline. If anyone from the App Review team is reading this, or if any developers have been through a similar situation and can share advice, we would deeply appreciate your input. Thank you for your time and support.

Hello, I am attempting to enroll in the Apple Developer Program and have already added $100 to my Apple account. However, every time I try to proceed with the enrollment, I encounter an error. I have reached out to Apple Support multiple times, but the issue remains unresolved. Each time, the case is escalated to a senior representative, yet no clear solution has been provided. It feels as though the issue is being passed back and forth without accountability. Furthermore, I’m receiving conflicting guidance—Apple.com refers me to developer.apple.com, and vice versa—leaving me stuck without a resolution. I would appreciate your urgent assistance in identifying and resolving this issue so I can complete my enrollment. Best regards, Gulf Now

Hello, I represent a registered business operating under a developer account that has always followed Apple’s guidelines, complied fully with review requests, and submitted documentation whenever asked. We have never knowingly violated any policy, and we categorically deny any dishonest or fraudulent behavior. Last week, our developer account was suddenly terminated without any prior warning or opportunity to address concerns. The message provided no specific reason, no actionable details, and no path to resolution. This has left us completely locked out — unable to appeal through standard channels, and unable to contact anyone directly. It’s shocking, disorienting, and devastating to a legitimate business with employees, users, and operations depending on this platform. To make matters worse, this is not the first time. A previous termination notice was sent weeks ago and then — after we submitted a respectful and professional appeal — Apple quietly reversed the decision overnight, without any explanation or follow-up. We were left to assume it was a mistake. We had hoped that incident was rare and behind us. Now it’s happening again, without explanation, and without a human conversation. We are losing money and users every day, and we’re still in the dark about what Apple believes we did wrong — because no one has told us. We submitted a support ticket (ID: 102590329012), but have received no reply. We are committed to transparency, and we’re ready to provide any information needed. But we need someone to acknowledge this issue and help us find a path forward. If anyone has experienced something similar or knows of escalation methods that worked, please share. We’re doing everything we can to resolve this respectfully — but we are shocked and deeply concerned. Thank you.

In my understanding, with the latest court ruling in the US, iOS apps may decide to support web-based payments for subscriptions and in-app purchases. However, are we allowed to exclusively support web-based payments and not implement StoreKit at all?

My app uses iCloud to let users sync their files via their private iCloud Drive, which does not use CloudKit. FileManager.default.url(forUbiquityContainerIdentifier: nil)?.appending(component: "Documents") I plan to transfer my app to another developer account, but I'm afraid it will affect the access of the app to the existing files in that folder. Apple documentation doesn't mention this case. Has anyone done this before and can confirm if the app will continue to work normally after transferring? Thanks

I hope this message finds you well. I’m reaching out to ask whether specific App Store Connect metrics available in the App Analytics dashboard can also be accessed via the App Store Connect REST API. I have reviewed the official API documentation, but I couldn’t find confirmation regarding the metrics listed below. Could you kindly clarify if the following metrics are available through the REST API? And if so, could you point me to the relevant endpoints or documentation? From the "Usage" group: Installations (Opt-in only) Active Devices Deletions (Uninstalls) From the "App Store" group: Impressions (Unique Devices) Product Page Views (Unique Devices) If these metrics are not available via the REST API, is there an alternative method to programmatically access or export them? Thank you very much in advance for your help and guidance.

I would like to copy the text of the field 'What's New in This Version' from the previous Release into the new release. Is that possible or when will it be possible? Google Play Console did a fantastic job implementing this. Stack Overflow Questions: https://stackoverflow.com/q/52474402/11322034

Our app's App Clip version has been published to app store, but still we can not open "Edit Advanced Experiences" page, when we click on it, we will be redirected to the homepage of connect. Did I miss some settings, or is this a bug? We can not open the single detail page of "Advanced App Clip Experiences" Diagnostic information Associated Domain

Hi All, We are trying to integrate Promotional Offer in our app, We have a React Native app and are using react-native-iap for handling our in app purchases, as per the documentation we are generating signature in our BE and passing the proper details to the function as well, but for subscription request which have offer applied we are getting the apple pop up properly as well with offer details but when trying to subscribe it gives us SKErrroDomain: 12, for subscription without applying offer the subscription goes through but when we apply the offer we get the above error. Our app is currently in Development Stages and has not been sent for review sam for our subscription plans as well. Please let me know what could be the probable cause for this and help us resolve the issue. This is the code snippet of ours for the front end : export const buySubscription = async (subscriptionData: any) => { try { if (subscriptionData.offer_id) { const response = await getSubscriptionSignature( subscriptionData.productId, subscriptionData.offer_id, ); const offerData = response?.data; const offer = { identifier: offerData?.offer_id, keyIdentifier: offerData?.key_id, nonce: offerData?.nonce, signature: offerData?.signature, timestamp: Number(offerData?.timestamp), }; await requestSubscription({ sku: subscriptionData.productId, withOffer: offer, }); } else { await requestSubscription({ sku: subscriptionData.productId }); } } catch (err) { logger.error('Subscription error: ' + JSON.stringify(err)); throw err; } }; and 
from my python Backend which generates the signature:

def generate_signature(self, product_id: str, offer_id: str) -> dict: """ Generate signature for Apple StoreKit promotional offers. Args: product_id: The product identifier from App Store Connect offer_id: The promotional offer identifier Returns: dict: Contains signature and required metadata Reference: https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/subscriptions_and_offers/implementing_promotional_offers_in_your_app """ try: # Generate UUID without dashes and use as nonce nonce = str(uuid.uuid4()) timestamp = get_current_time_ms() # milliseconds # Create the payload string in exact order required by Apple payload_components = [ self.bundle_id, # App Bundle ID self.key_id, # Key ID from App Store Connect product_id, # Product identifier offer_id, # Promotional offer identifier nonce, # UUID without dashes str(timestamp) # Current timestamp in milliseconds ] payload_str = "\u2063".join(payload_components) # Use Unicode separator logger.debug(f"Signing payload: {payload_str}") # Create SHA256 hash of the payload digest = hashes.Hash(hashes.SHA256()) digest.update(payload_str.encode('utf-8')) payload_hash = digest.finalize() # Sign the hash using ES256 (ECDSA with SHA-256) signature = self.private_key.sign( data=payload_hash, signature_algorithm=ec.ECDSA(hashes.SHA256()) ) # Encode signature in base64 signature_b64 = base64.b64encode(signature).decode('utf-8') logger.info(f"Generated signature for product {product_id} and offer {offer_id}") return { "key_id": self.key_id, # Changed to match Apple's naming "nonce": nonce, # UUID without dashes "timestamp": timestamp, # As integer "signature": signature_b64, # Base64 encoded signature "product_id": product_id, # Changed to match Apple's naming "offer_id": offer_id # Changed to match Apple's naming } except Exception as e: logger.error(f"Failed to generate signature: {str(e)}") raise HTTPException( status_code=500, detail=f"Failed to generate signature: {str(e)}" )

Hi - I was recently added to Apple Developer Team, and I am trying to upload an App to our Team's App Store Connect account for TestFlight distribution. I am trying to use XCode Cloud to this all automatically, but it is currently giving me this error: "Invalid Bundle ID. Bundle ID "com.XXX.YYY" could not be automatically registered because it is not available. Update the bundle ID of your project and try again." I am not sure if this is related to the fact that when I try to associate my XCode Account (XCode -> Settings -> Accounts), I only see my (Personal Team) account even after removing that account and re-adding it. Additionally, when I go my App -> Targets -> Signing & Capabilities and I check / uncheck automatically manage signing. I only see my Personal Team account. When I try to download a Provisioning Profile, I see "No Valid Teams, Unable to Find Any Valid Teams." I need to keep the bundle ID of the project as is because it is associated with a Firebase backend. What should I try next? Thanks!

Hello, I currently have a live application in the iOS App Store that needs an update to start functioning again, but I've lost the source code in a hard drive failure. Is there a way to reverse engineer the currently deployed package that is live (and also a way to download it from App Store Connect)⁉️ The development change itself is just a very small change for an API route in the code itself. I could even direct an engineer at Apple to make the change in 5 minutes! Let me know if this is possible. Thanks❗️

Hello, I am writing to seek assistance regarding a prolonged delay in updating my personal information within the Apple Developer Program. I submitted a request to update my developer account information on December 9, 2024. Since then, nearly six months have passed. Despite multiple follow-ups with Apple Support, I have only been informed that my case would be “escalated to the operations team” without receiving any concrete update or explanation about the processing status. I am not sure if there is a time limit for such a request. A delay of almost half a year is far beyond the normal timeframe and has caused significant disruption to my account maintenance, app distribution, and personal tax matters. Can anyone give me a suggestion for this? Great thanks. 🥺

Hey everyone, I’m submitting my first version of an iOS app to the App Store and ran into an issue I can’t seem to resolve. The app was rejected because during review, Apple couldn’t see the In-App Purchase product on the purchase screen. That’s their only complaint — everything else works fine. Here’s what’s going on: • In debug mode via Xcode, the product shows up correctly, and everything works as expected. • In TestFlight builds, the product doesn’t show up at all — neither for me nor for Apple. • The IAP is currently marked as “Waiting for Review”, not “Ready to Submit”, and it is linked to the current app version in App Store Connect. I’m not sure if the IAP being in “Waiting for Review” is the reason it doesn’t show up in the TestFlight version — but I assumed Apple would still be able to access it for testing. Has anyone experienced this? Do I need to wait for the IAP itself to be approved before it works in TestFlight and can be reviewed? Any insights would be super helpful. Thanks!

Hi everyone, I’m facing a frustrating issue with the App Store review process and wanted to know if anyone else has gone through something similar. I first submitted my app on April 15, 2025. After waiting for nearly 8–10 days with no progress, I ended up rejecting the binary myself out of frustration. I then resubmitted the app on April 24, 2025, but as of today, it’s still showing "Waiting for Review" with no updates or movement. This delay is really affecting my release schedule, and I’m not sure if there’s something wrong on my end or if this is just an unusual queue time. Has anyone else experienced this recently? Is there anything I can do to speed things up or get insight from Apple? Appreciate any help or shared experiences. Thanks

Hello, after sending my application for review, my application is rejected by specifying the general reasons without adding any screenshot. After correcting the specified deficiencies and errors, I send it to review again, but there is no response for weeks. I am creating an accelerated examination request, but it has no effect. 2 months have passed since the first time I sent my application to review ... I received a rejection response 3 times in 2 months. The investigation does not start, it is only 'waiting for the review'.

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.