Ever since I have upgraded to iOS 26 (at least, I THINK this was when it started) I have been seeing an email account on Testflight purchase flows that is NOT mine. I have never seen this email in my life, and have not used it during the 10+ years I have been a developer. I do not know how to make this use my Apple ID I am signed into on my device. However, locally signed builds from Xcode still work ok. But I need Testflight builds to work as well. How do I force this account to change?

Environment OS: iOS 26.2 (Beta/Release) Framework: StoreKit 1 (or StoreKit 2) Environment: TestFlight / Sandbox Device: [Insert your device model, e.g., iPhone 15 Pro] Description I am encountering a persistent issue where SKPaymentQueue.default().finishTransaction(transaction) does not successfully remove the transaction from the queue. Every time a new purchase is initiated, the observer triggers an immediate update with the previous transaction's ID (Transaction ID). The system then displays a system alert stating: "You've already purchased this In-App Purchase. It will be restored for free." Even after explicitly calling finishTransaction, the same transaction reappears in the updatedTransactions array upon the next app launch or purchase attempt. Steps to Reproduce Add a transaction observer in didFinishLaunchingWithOptions. Initiate an In-App Purchase in TestFlight. Upon success (.purchased), call SKPaymentQueue.default().finishTransaction(transaction). Attempt to buy the same non-consumable item (or any item) again. Result: The previous transaction is pushed again, and the queue never clears. What I’ve Tried Ensured finishTransaction is called on the main thread. Verified that the observer is added at app launch. Manually iterating through SKPaymentQueue.default().transactions and finishing all entries. Signed out of the Sandbox account and used a completely new test account. Deleted and reinstalled the App via TestFlight.

I'm currently working on an OSX app that requires a user to have Spotify installed. (If the user doesn't have Spotify, the app will still run–it will just be useless) It seems like this sort of thing is allowed because I see plenty of apps in the Mac App Store that use Spotify, but do I need to make any special notes of this in my app submission to make sure it's approved?

I noticed that https://developer.apple.com/news/upcoming-requirements/ is no longer being updated with SDK requirements. You would think this would be a nice place to check for upcoming requirements for app submissions etc. Can we get the Xcode 26 requirements added?

Starting on 1/30/2026, we started getting an error when using Reporter to retrieve a Subscriber/Sales report from App Store Connect. Our script was working daily perfectly for a long time before this. It normally pulls the report from 1 day prior. We have been troubleshooting and cannot seem to find any issues on our end. Is this a universal issue for other users too?

Hello, My new app has remained in the "Waiting for Review" status for an extended period. I initially submitted it on January 23, 2026. After several days without any progress, I submitted an inquiry on January 27 but have not yet received a response. On February 1, I canceled and resubmitted the app, wondering if there might have been an issue with the review queue, but it still remains in the "Waiting for Review" state. I had scheduled my marketing activities based on the typical review timeframe, but since the review has not started and there is no indication of how much longer the wait will be, it has been difficult to adjust my plans accordingly. If anyone has experienced a similar issue and managed to resolve it, I would greatly appreciate any insights you could share. Thank you for your time, and I hope you have a great day.

Hi, Apple developer community We’re launching our first app and we’re really excited (and honestly a bit anxious) about the review process. From the start, we used the Notes section to proactively answer any questions we could think of — including how the app works and complete test credentials. The first review took 3 days, and then we were asked for additional documentation. We provided everything within a couple of hours, and we also re-shared the same key information from Notes to make it easier for the reviewer. Then another 3 days passed (which feels very long to us), and we received the exact same rejection again. It really seems like the reviewer isn’t reading our response or the Notes section. We can also see that they aren’t logging into the test account for some reason. We’ve replied again with a detailed explanation, but it feels like we’re stuck in a strange loop of rejections. What would you do in this situation? Why might a reviewer be overlooking the information even when it’s clearly provided both in Notes and in our reply? We’re building a genuinely useful product and we’re very concerned about what’s happening here.

Hi all, I've been attempting to implement the Texas age range restrictions for an app I work on. I've banged my head against it for the last week and have a flow that is 99% working. I have all of the cases working exceptt when a significant change is approved. The issue I'm running into, is that let responsesSequence = AskCenter.shared.responses(for: SignificantAppUpdateTopic.self) is not receiving a response the first time it's called. It's only after the second time it's called that a response is registered and then I allow a user to access my app. When I set significant app change declined, then responses(for: ) returns on the first call to it. I can't for the life of my figure out why one works and the other doesn't. Has anyone else encountered this or have suggestions for me? I'm happy to post more code here in order to come to a resolution on this issue.

Hello, I've just been unfortunate enough to discover a critical issue. I have two apps using Asset Packs, and I believe both apps had an Asset Pack with the same identifier. In App Store Connect for App B, I archived this Asset Pack. However, the Asset Pack has been archived for both Apps. This shouldn't happen.

It is the beginning of February and we have not yet received our 1099 from Apple. Has anyone received theirs? Can I download it somewhere or does it only come via snail mail? Thank you

Hi, I have a completely new release of my app coming out with a new tech stack. I noticed that only 1% of my users were on iPad so the new app was not created to be 'compatible' with iPad including how it looks on iPad. Can I release this new version of the app only for iPhone? Or because it was previously available for iPad I have to release for iPad as well? Really appreciate any support/guidance on this. Thank you!

Hello Developer Community, I'm encountering a persistent issue with app rejections related to iPad compatibility, even after explicitly removing iPad as a supported device family in my Xcode project for the latest submission (Version 1.0.1, Build 11). The Apple Review team continues to test on iPad devices (specifically an iPad Air 5th generation running iPadOS 18.4.1) and rejects the build under Guideline 2.1 - Performance - App Completeness, citing a login issue with demo credentials that leaves the app stuck on the login page. In my previous submission and subsequent resubmission, I clearly targeted only iPhone in the Xcode project settings (Target -> General -> Deployment Info -> Devices: iPhone). I also confirmed that the "Targeted Device Families" setting reflects only iPhone. Despite these changes, the review team's feedback indicates they are still evaluating the app on an iPad and encountering the same bug. Their response to my clarification about removing iPad support was: "Regarding 2.1, as we mentioned in our previous correspondence, users expect apps they download to function on all the devices where they are available. Since your app may be downloaded onto iPad devices, it is important that it also function as expected for iPad users." This response is confusing, as my intention with the latest build was to explicitly limit availability to iPhones due to unresolved issues on iPads. ** My Questions are: ** 1: Is there any other setting or configuration in Xcode beyond "Targeted Device Families" that I might be missing to ensure the app is only intended for and tested on iPhones for this specific build? 2: Has anyone else experienced a similar situation where the App Review team seems to be testing on devices explicitly excluded in the build settings? If so, how did you resolve it? 3: What are the potential reasons why the app might still be installable or visible on iPads in the App Store despite the Xcode configuration?

Hi, I uploaded my app to TestFlight and released but mistakenly enabled support for iPads. However, the app does not support iPads, and whenever I submit it for approval, the App Store rejects it due to design issues. When I disable iPad support and re-upload it to TestFlight, I get an error stating that it does not support the previously uploaded platforms. Can anyone please guide me how can i disable it any way around?

We have submitted our app as both iPhone and iPad compatible - we want to remove iPad, but can't find how to do that in the App Store Connect console - any ideas? Thanks in advance Kjell

Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.

Dear App Review Team, Our app – Apple ID 6756967338, has been stuck in the “In Review” status for over 10 days (Jan, 19 at 1:33 PM). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Could you please clarify: • Is there a specific reason for this hold? • Is any action required from our side? • When can we expect the review to finish? Thank you very much for your time and assistance.

I have an app that is stuck in "Waiting for review" since January 2nd. This will be one month tomorrow as I'm writing this. It's a totally new app, which I guess could take longer than an update to an existing app, but a month seems a bit much. What can I do about this? It seems weird that there isn't some kind of alarm inside the app review team that will catch some app being stuck for this long...

when I share the App Store link for my app FlexPath on say iMessages; the screenshot generated with the shared link is that of the Apple Watch’s screenshot and not the iPhone’s screenshots i have reloaded the images with new builds to fix the issue. Checked my localization settings. but I can’t fix it! please help.

When adding new TestFlight users, they are not receiving the email invite. I have had them check junk mail and/or other filtering software. Is anyone experiencing the same thing?

Hi everyone, are you experiencing this issue as well? My app has been stuck in “waiting for review” for about 5 days, and I’m not getting any responses to my tickets. We’ve prepared all our ad campaigns and advertising budgets, but Apple is not responding to the ticket, not pulling the app into review, and not approving it. It’s just stuck like this. Is there no Apple developer employee on the forum who can help?