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.

Hello everyone, I’m currently enrolling as an Organization from Albania and I’ve been stuck on the "Enrolling" status for 8 business days now. I have my D-U-N-S number sorted and everything was submitted. I sent an email last week to the support but I haven't heard back yet. I’ve already sent another support message 2 days ago but no reply so far. I’m curious to hear from others who have enrolled recently (especially in 2026): How long did your organization verification take? Did you receive a verification phone call, or was it just approved via email? For those in the Balkans/Europe, did you have to provide extra local business registry documents (like the QKB extract) manually? I’m trying to time my launch with my Google Play release, so I’m a bit anxious about the "black hole" of waiting. Any experiences or "nudge" tips would be greatly appreciated! Thanks!

Hello everyone Hoping for some insights with an issue we're having with our app store review process. Note that this is not a new app, and we've had many successful reviews in the past. We submitted the app for review just over a week ago. We received a timely review about 24 hours later, citing an issue with Apple Pay. We make use of PassKit, but the reviewer could not find where we use Apple Pay in our app. I replied within a few hours with screenshots and videos, as it is quite easy to find where we use Apple Pay. Since then, we haven't received any feedback at all. I tried resubmitting a new build after 4 day,s and that is also sitting unreviewed for a while now. We've got features and bug fixes that were supposed to go out in this release, but we are now blocked on them. Is there anything we can do?

This api is experiencing 503 errors again. Please fix it as soon as possible.

Hello, I’m seeking clarification on In-App Purchase requirements for a marketplace vendor app offering real-world, offline services. We plan to offer paid vendor listing plans (Free, Silver, Gold, etc.) that provide business benefits such as increased visibility, analytics, and also include feature limits like the number of images a vendor can upload to their business profile and enhanced dashboard views. These plans are intended to support vendors’ real-world businesses and do not provide digital content to consumers. Does gating vendor features such as image upload limits or dashboard capabilities require Apple In-App Purchase under App Store Review Guideline 3.1, or can such vendor plans be processed using a third-party payment gateway as account-based service tiers?

App is repeatedly rejected under Guideline 2.5.1 for referencing the private API:_SecCertificateIsValid Reported custom framework CommonLibrary.framework. The SDK is written in Objective-C and uses only public Security APIs. It does not use any deprecated APIs. We have verified the framework binary using nm, otool, and strings, and _SecCertificateIsValid does not appear in exported or hidden symbols. Bitcode is disabled, dead-code stripping is enabled, and the Release build uses -Os. Despite this, App Store Connect continues to detect _SecCertificateIsValid. We have attached herewith screenshots of our analysis for the reference. Can Apple’s server-side analysis or Security.framework internals still surface _SecCertificateIsValid? Is there a recommended way for SDK authors to prevent this symbol from being flagged?

Since last year, our company has been signing in new users to Apple Store Connect using our private email domain. However, since last week, when we try to sign in with this same domain, we receive the following error: "Your primary email address cannot end in @mydomain.com.br. Choose a different email address."

Or, can we consider the response completes once the prompt disappears? I will write down the sequence of events in order. A prompt appeared on our app's page asking us to respond to the survey. However, likely because the app hadn't been updated for many years, the “Edit” option for age restrictions was not displayed; instead, “View” was shown. After creating a page for the new app version, “Edit” appeared. We hadn't planned to release the new version to the App Store at this time, but we only created the new page to respond to this survey. After entering “edit” and answering the age restriction survey, the prompt disappeared. I contacted Apple Support to find out if just answering would suffice, but they told me to submit the app for review. However, as mentioned above, we have no plans to modify and release this app. Since it's an old app, I updated the environment, built it, and submitted it, but issues were pointed out. (I think it's because it's an old app.) When I asked the Apple Review team the same question as at the beginning, they suggested I post it here. Many thanks!

I just had an app approved and pending developer release. As part of my release checks, I always download the app using a promo code (even for free apps). This time, on both iOS and macOS, redeeming a promo code for the respective builds gives this error: Unable to Redeem. This content is incompatible with the current software on this device. Update your device to the latest software version and try again. The app targets iOS 26.0 and macOS 26.0, and my devices are on the latest releases. Has anything changed with promo code redemption for approved apps? I typically use promo codes for updates, but have not released a new app in a while.

I'm hoping someone from Apple engineering can help, as support tickets and callbacks have not resolved this issue. The problem: My app "Brutal Time - Typographic Clock" does not appear in App Store search results at all — not even when searching for its exact name "Brutal Time." This has been ongoing for over six weeks. Additionally, the app does not appear in Apple Search Ads when I try to set up a campaign — suggesting this is a backend indexing issue, not a ranking issue. Timeline: Dec 17, 2025: App launched, initially searchable Dec 31, 2025: Transitioned to freemium model, became invisible in search. Jan 5, 2026: Fixed the issue, submitted update (v2.02), approved same day Jan 14, 2026: Submitted metadata update (v2.03) to improve discoverability, approved same day Feb 8, 2026: Tried removing from sale and re-adding to force re-index — no effect Feb 10, 2026: Still not appearing in any search results What I've tried: Submitted multiple support tickets (most recent: Case #102797235758) Each ticket generates an automated reply stating Apple will respond within 2 business days — they never have Requested and received callbacks multiple times, was told it would be escalated to US engineering team. But no follow-up, no resolution, no explanation Removed from sale and re-added to attempt to force re-indexing — didn't work App shows "Ready for Distribution" in App Store Connect Direct link works fine: https://apps.apple.com/us/app/brutal-time-typographic-clock/id6756289461 Response from Apple Support: "The behavior you observed is expected. App Store charts and search results change regularly and we don't guarantee app placement." This response misses the point entirely. I'm not asking about rankings — I'm asking why the app is completely invisible in search, including for its own branded name. This is not an isolated issue. Other developers have reported the same problem with the same non-response from Apple: https://developer.apple.com/forums/thread/803937 https://developer.apple.com/forums/thread/73981 https://developer.apple.com/forums/thread/74110 Has anyone found a resolution? Is there any way to trigger a proper re-index, or escalate to someone who can actually investigate?

When I update my app name, the App Store URL also changes, and since the app URL contributes to ASO performance, this is a concern for me. I would like to know whether it is possible to change the app name without affecting the URL, or if the previous URL automatically redirects to the new one.

I'm attempting to use Cloud Signing to export the Release version of 3 different apps for App Store, as described in https://developer.apple.com/videos/play/wwdc2021/10204/ The process completes successfully, and appears to be signed correctly, with a newly-created certificate in the developer portal of type "Distribution Managed". When I upload to App Store Connect however, I see the following error for several third-party Swift packages, distributed as frameworks: Validation failed (409) Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “MyApp.app/Frameworks/MyFramework.framework/MyFramework” 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. If I have a manually created Distribution certificate installed in the keychain at the point of export, the same archive is signed with that certificate, and is accepted by App Store Connect without issue. The xcodebuild command I am using (roughly): xcodebuild -exportArchive \ -archivePath "$ARCHIVE_PATH" \ -exportPath "$EXPORT_PATH" \ -exportOptionsPlist "$EXPORT_OPTIONS" \ -authenticationKeyPath "$API_KEY" \ -authenticationKeyID "$API_KEY_ID" \ -authenticationKeyIssuerID "$API_KEY_ISSUER" \ -allowProvisioningUpdates The plist: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "<http://www.apple.com/DTDs/PropertyList-1.0.dtd>"> <plist version="1.0"> <dict> <key>method</key> <string>app-store-connect</string> <key>teamID</key> <string>$TEAM</string> <key>uploadSymbols</key> <true/> <key>signingStyle</key> <string>automatic</string> </dict> </plist> Is what I’m trying to do supported? Is this a bug?

My iOS app has passed App Review and is marked “Ready for Distribution,” but App Store Connect does not allow me to release it because the App Store Version Release controls are disabled. App Review is closed and the Resolution Center is unavailable. I have submitted multiple Apple Developer Support cases and called phone support, but the issue remains unresolved. This appears to be an App Store Connect backend state issue affecting a first-time app with subscriptions. Can Apple engineering assist in unlocking release permissions for iOS version 1.0?

I see many developers struggling with ASO where AI written content does not deliver results, performance analysis is unclear, localization is ignored, App Store optimization is incomplete, and keywords are often poorly chosen. I am considering running two simple group sessions to share practical tips and show clear ways to improve ASO with real effort involved, and I would like feedback on this idea whether offered for a small fee or even for free.

Hello, I’m looking for guidance regarding a new app submission that has been in “Waiting for Review” status for 6 days now, with no change or additional communication. This is a brand-new app submission (not an update). There have been no metadata changes or rejections — it has remained in the waiting state since submission. I completely understand that review times can vary depending on workload and complexity. I just wanted to check whether this timeframe is currently normal, or if there may be something specific I should verify on my end. The app is an educational medical application, and all content is original. There are no unusual entitlements, external payment systems, or restricted APIs involved. If anyone from Apple or fellow developers has insight into whether extended “Waiting for Review” times are currently common, I would appreciate your input. Thank you in advance.

Currently, I have purchased the Apple Developer Program for 4 days. However, I can not access or hear any news from Apple team that where I was wrong or do my account have any problems.

Testing with testflight the IAP work with sandbox. But Apple Review was rejected. It was explained that the IAP could not be found. I cancelled the review, added the IAP to all countries again. The IAPs are in status waiting for review. Now when preparing the version, I cannot choose anymore the IAP. I don't find the option anymore to add the IAP products on the version page. Contracts are all active and in the app for me and others it is working.

I am looking for some insight into current App Store review times. The Situation: I submitted my new app for its first review on February 3rd. It has been sitting in the "Waiting for Review" state for 11 days now and has not moved to "In Review." The Impact: We had a major launch event planned for today (Feb 14). We have marketing campaigns live and users waiting, but we have officially missed our launch window because the app is still sitting in the queue. My Questions: Is anyone else experiencing wait times this long (10+ days) just to enter the review stage? How much time does it typically take for a first-time submission to go live once it finally enters review? Is there any way to flag this delay if it has exceeded the standard 48-hour window? We are losing marketing budget every hour this is delayed. Any advice on how to get this moving would be appreciated. Thanks.

I have 9 plus years of iOS experience starting with Objective C and moving to Swift, but after 4 years in my current company with little salary growth, I am struggling to find new opportunities in a highly competitive market with fewer openings and broader skill expectations. I am unsure about the long term career path for mobile developers, concerned about compensation growth and lacking SwiftUI experience, and would appreciate guidance on what additional skills to learn to stand out and secure better opportunities.

Dear Apple Team, I am writing regarding our pending account termination. Timeline: January 25, 2026: Received Pending Termination Notice January 25, 2026: Submitted appeal and corrective update February 5, 2026: Responded to DPLA compliance notice February 10, 2026: Submitted follow-up via Review Board and Contact Us Current: Corrective update remains In Review, no response received We have submitted corrective updates addressing all identified issues. The corrected version is currently In Review. With the February 24 deadline approaching and no feedback received through any channel, we are concerned about the status of our appeal. We remain fully committed to compliance and respectfully request confirmation that our appeal is being reviewed. Thank you.