have successfully created subscription with all metaData: Localization(inside subscription and also for subscription group), logo, description and also screenshots but subscription shows missing metadata instead of ready to submit causing flutter app package inAppPurchase to not found the subscription id or product it. Flutter code level : Future<void> _loadSubscriptions() async { Set<String> kSubscriptionIds = {'monthly_689'}; ProductDetailsResponse response = await _inAppPurchase.queryProductDetails(kSubscriptionIds); if (response.notFoundIDs.isNotEmpty) { kLog("Subscription IDs not found: ${response.notFoundIDs}"); } print("God it works seriously"); print(response.notFoundIDs); print(response.productDetails); print(response.error); subscriptions.value = response.productDetails; } Says: Subscription IDs not found is been logged I try with storekit it works!!! but as apple asking me we test on sandbox environment and it's not working I also created sandbox account login with same credentials and test it not works. Point is package I used in flutter not finding the above product_id I successfully added subscription group, localization, image and all still why my subscription not found ?

Hey, is it possible to test with an Xcode test build if the subscription notifications are correctly being sent to the backend? Currently nothing appears on my backend after subscribing. For some reason i can also subscribe multiple times to the same product. It looks like nothing is being saved anywhere which is why I also can't cancel a test subscription. All of this was fairly easy and possible when setting up the google play version of our app.

Hi, I have an application published in the Marketplace. I made certain updates to the app. I did my tests.No problem. I did my tests via Testflight. There is no problem I encountered. But my app update request was returned by app review. The answer i got from them ;  "Specifically, our login attempt displayed loading indefinitely; we were unable to access the app features and functionality." Here are the ways that I tried and the app worked successfully. Connect from America using VPN.No problem, it works. I connected from using IPV6.No problem, it works. I tried with simulator.No problem, it works. I tried real device.No problem , it works. I tried testflight.No problem, it works. I tired version 15.2 and earlier.No problem , it works. I have no idea why apple staff are getting this error. Has anyone encountered such a problem before? What solutions would you suggest? I'm waiting for your help.

Dear Experts, If a user with an older device tries to download an app, and the current version of the app requires an iOS version which their device does not support, the App Store will offer them an older most-recent-compatible version instead. I've just had an enquiry from a user of my app for whom this has not worked. Specifically he has an iPad 2. He foolishly deleted my app from the device, and now the App Store will not let him re-install it. Does anyone know why this may be? Is it simply that this App Store feature does not work for devices as old as the iPad 2? Thanks.

I'm getting this error from inside the TestFlight tab in Appstore Connect. For a MacCatalyst app. This has worked for amost 4 years now I'm getting this error. I did update my version of Xcode to 26.0.1. And I migrated all the project settings it asked me to migrate. I ran the Validation in the Archive window of Xcode. No issues found there.

I’m reaching out regarding our existing in-app subscription implementation that currently uses App Store Server Notifications version 1 (v1). Our live application has a significant number of active recurring subscriptions that are being managed through the v1 webhook integration. We have now developed a revamped version of our application, which uses the same Apple Developer Account and App Store Connect setup, but in this new app version, we’ve implemented App Store Server Notifications version 2 (v2). Before moving forward with the migration, I would like to clarify the following points to ensure a smooth transition and avoid any disruptions to ongoing subscriptions: Backward Compatibility: Will existing active subscriptions (originally created and managed via v1 notifications) continue to work seamlessly once we switch to v2, or do we need to maintain both v1 and v2 endpoints during the transition? Notification Delivery: If both webhook versions are configured simultaneously, will Apple send notifications to both endpoints, or only the one currently configured in App Store Connect? Migration Strategy: What is Apple’s recommended best practice for migrating from v1 to v2 in a scenario where the live app still has active subscriptions tied to the v1 webhook? Potential Risks or Considerations: Are there any known limitations, delays, or issues that we should prepare for during this migration (for example, differences in payload structure or event types between v1 and v2 that could affect subscription lifecycle management)? I would greatly appreciate your guidance or documentation links that outline the correct migration steps and recommended approach for ensuring continuity of service for all existing subscribers.

Hi, I'm here hoping for some help or advice in terms of a critical situation I'm currently facing. I want to change the copyright of an app, which was my previous app but now transferred to another company. In the Apple developer panel, is there anywhere that can change the copyright? Here is a quick summary of the app development, Software Vendor 1 developed the app, then transferred to Software Vendor 2, eventually the Client user(only paid for the app but don't have developer account) can use it. Now, I'm the Software Vendor 1 and has transferred the app to Software Vendor 2, but the copyright is still Software Vendor 1; and I want to ask Vendor 2 change the copyright to Client user directly as the Client user has bought the app. I’ve contacted Apple Support multiple times through mails. They just tell me to ask the Account Holder/Admin of the organization account that now owned the app to contact them in order to receive support. Then, I've asked Software Vendor 2 to contact Apple support, but have no response from Apple support after 1 week. My Case number is: 102708379460 This case is quite urgent for me, if anyone from the App Support team sees this post, or if any developers have experienced a similar situation and can offer advice, we would be truly grateful. Thank you in advance for your time and support.

This might sound ridiculous, but even more ridiculous is who ever thought of not putting a link to it... where can I find the Apple Developer Program License Agreement so I can accept it? I'm getting the following message: The updated Apple Developer Program License Agreement needs to be reviewed. In order to update your existing apps and submit new apps to the App Store, the Account Holder must review and accept the updated agreement. I go to the agreement section https://appstoreconnect.apple.com/agreements/ I it doesn't show anything...

Hello, I received an e-mail like this and my account was closed, there were balances to be paid inside. In this case, can anyone get paid? Can anyone with information answer? I'm going crazy about thinking about it. Please help This letter serves as notice of termination of the Apple Developer Program License Agreement (the “ADP Agreement”) and the Apple Developer Agreement (the “Developer Agreement”) between you and Apple effective immediately. Pursuant to Section 3.2(f) of the ADP Agreement, you agreed that you would not “commit any act intended to interfere with any of the Apple Software or Services, the intent of this Agreement, or Apple’s business practices including, but not limited to, taking actions that may hinder the performance or intended use of the App Store, Custom App Distribution, TestFlight, Xcode Cloud, Ad Hoc distribution, or the Program…” Apple has good reason to believe that you violated this Section due to documented indications of fraudulent conduct associated with your account. Apple is exercising its right to terminate your status as an Apple developer pursuant to the Apple Developer Agreement and is terminating you under the ADP Agreement for dishonest and fraudulent acts relating to that agreement. We would like to remind you of your obligations with regard to all software and other confidential information that you obtained from Apple as an Apple developer and under the ADP Agreement. You must promptly cease all use of and destroy such materials and comply with all the other termination obligations set forth in Section 11.3 of the ADP Agreement and Section 10 of the Apple Developer Agreement. If applicable, no further payments will be made to you pursuant to Section 7.1 of the Paid Applications agreement (Schedules 2 and 3 to the ADP Agreement). This letter is not intended to be a complete statement of the facts regarding this matter, and nothing in this letter should be construed as a waiver of any rights or remedies Apple may have, all of which are hereby reserved. Finally, please note that we will deny your reapplication to the Apple Developer Program for at least a year considering the nature of your acts. If you want to file an official complaint pursuant to an applicable Platform Regulation in your country or region you may Contact Us. Sincerely, Apple Inc.

We are planning on renaming our app. The new name is not like the current name. It will be renamed in the App Store as well as the App display name. Yet, we still want new and existing users to be able to find the app by using the old name in search/spotlight under iOS. A great example of this is entering Twitter to find the X app and it shows up in the App section in the Spotlight search. Are there any guidelines, settings, or tricks for doing this? Some have suggested adding a Spotlight search term but that will not have it show up in the App section I fear.

I have tried everything and still I am getting this. Just for a test I created a new app (Master-Detail template Xcode 11.5) I have created an entry in the iTunes Connect to receive the app upon archiving and uploading. I regenerated all new certificates for iOS Development and Distribution. I created all new Provisioning profiles. The Dev profile builds deploys and runs on my device The Dist profile builds but when I select the distribution profile I get the "Profile doesn't include the com.apple.application-identifier entitlement." error. When I download the profile within Xcode all looks good for the distribution profile: App ID: matches correctly Certificated: 1 Included includes the new signing certificate "iPhone Distribution...." Capabilities: 3 Included Includes Game Center, In-App Purchase, and Keychain Sharing Entitlements: 5 Included Includes application-identifier, keychain-access-groups, beta-reports-active, get-task-allow, and com.apple.developer.team-identifier. Im not sure what is going on. This is a standard process I have performed for quite a while. As a matter of fact I just submitted 3 applications last Sunday. Thank you for any suggestions.

Since 1st of September archives uploaded via Xcode 26 beta 7 or builds distributed via CD (fastlane deliver) don't appear in App Store Connect. No errors reported during/after upload process, no e-mails with errors received. Xcode reports successful upload (with a few warnings regarding dSYM) I'm not getting any e-mails with ITMS errors Builds don't appear at in App Store Connect in TestFlight section (not even in "Processing" or "Failed" states). For me it seems like App Store Connect outage but all statuses in https://www.apple.com/support/systemstatus/ are green.

What are guidelines for apps being released in the US App Store in order to comply with The Texas App Store Accountability Act? I mean there's no way to differentiate an app downloaded in Texas from the other states and it would be ridiculous to add location awareness to an app to comply with this, so effectively it means any developer of any app for release in the US must comply with this in case it might be being used in Texas? This new Apple API has zero background, zero context, zero example of usage, zero guidelines about how to use it in practice: https://developer.apple.com/documentation/declaredagerange/

1) The circumstances: iPADOS~>18, USB still-imaging-gadget, 1-3 gadgets might connect simultaneously via USB-hub, proprietary DExt, UserClient App in developers' iPADs or in TestFlight. = 1 variation A) UserClientApp has attribute [Background modes][Enable external communications]. = 1 variation B) "active USB-hub" vs "passive". = 1 variation C) "ConsoleApp logs iPAD" vs "ConsoleApp is not started". = 1 the term "zombie" below assume issue: == after plug-in ConsoleApp logs "IOUsbUserInterface::init", "::start"; == UserClient never receives respective callback from IOServiceAddMatchingNotification == further IOKit APIs "teardown", "restart" and "re-enumeration of connected gadgets" doesn't reveal the zombie (while it sees another simultaneous gadget); == unplug of the gadget logs "IOUsbUserInterface::stop". =2) The situation when UserClient is in foreground: ~ everything is fine. Note in MAC OS everything (same DExt and UserClient-code) works fine in background and in foreground. =3) The situation when UserClient is in background (beneath ~"Files" or "Safari"): =3A) "1A=true" phys plugin causes zombie in ~1/20 cases (satisfactory) =3B) "1A=false" phys plugin causes zombie in ~1/4 cases (non-satisfactory) =3C) "1 variation B" and "1 variation C" reduce zombies by ~>30%. =3D) ConsoleApp logs with filter "IOAccessory" (~about USB-energy) always look similar by my eyes. =4) From Apple-store: "The app declares support for external-accessory in the UIBackgroundModes"..."The external accessory background mode is intended for apps that communicate with hardware accessories through the External Accessory framework."..."Additionally, the app must be authorized by MFi," =5) My wish/ask: =5 option A) A clue to resolve the "zombie-plugin-issue in background" in a technical manner. = E.g. find a straightforward solution that ~elevates UserClient's "privileges" in background like [Enable external communication]... E.g. what ConsoleApp-logs to add/watch to reveal my potential bugs in DExt or in UserClient? =5 option B) A way to pursue Apple-store to accept (without MFI) an UserClientApp with [Enable external communication].

Hi everyone, I created my app icon using Apple’s Icon Composer tool, a single AppIcon.icon file, set the iOS and Mac Catalyst using shared mode. There’s no AppIcon imageSet in Assets.xcassets. The app displays the icon correctly at runtime — both on iOS devices and on macOS (Catalyst build). On macOS versions prior to 26, the App Store icon looked completely normal. However, in App Store Connect and in the Mac App Store on macOS 26, the icon appears with a gray border. Thanks in advance for any insights or suggestions!

Hello everyone, I'm facing a strange issue with one of my apps and was hoping for some guidance or to see if others have experienced something similar. My app, Trackless Links (App ID: 6749830894), has recently become unsearchable in the App Store. Even when searching for the exact name, it does not appear in the results. The only way to access the product page is via a direct link. The app was previously indexed and searchable without any issues. What's particularly strange is that my other app (Mindful Coffee), which is on the same developer account, remains perfectly searchable. This seems to indicate the issue is specific to "Trackless Links" and not my account itself. I've already gone through the standard checklist: The app status is "Ready for Sale" in App Store Connect. Availability is set for all major regions. My developer account and all related agreements are active and in good standing. It has been well over 48 hours since this issue started. Has anyone else experienced an issue where a single, previously indexed app gets de-listed from search? I'm trying to determine if this is a temporary indexing glitch that might resolve itself, or if there's a specific action I can take to trigger a re-index. Any insights or similar experiences would be greatly appreciated. Thank you.

Starting around October 12, 2025 at 19:51 UTC, we're seeing intermittent failures when verifying StoreKit transaction JWTs. The issue appears to be related to certificate expiration in the x5c chain in the JWT tokens provided by Apple. What We're Seeing Some JWTs are being signed with different certificates. Some work, some fail certificate validation. Old Certificate (Expired - causing failures): Subject: Prod ECC Mac App Store and iTunes Store Receipt Signing Issuer: Apple Worldwide Developer Relations Certification Authority (G6) Serial: 166451396673336810269824643773700992094 Valid From: 2023-09-12 19:51:53 UTC Valid To: 2025-10-11 19:51:52 UTC ❌ EXPIRED New Certificate (Valid - working): Subject: Prod ECC Mac App Store and iTunes Store Receipt Signing Issuer: Apple Worldwide Developer Relations Certification Authority (G6) Serial: 95385247725814954943813376527885434295 Valid From: 2025-09-19 19:44:51 UTC Valid To: 2027-10-13 17:47:23 UTC ✓ VALID Current Status Most JWTs use the new valid certificate. Some JWTs still use the expired certificate. This appears inconsistent/random. I don't know if it's an issue with some of Apple's servers, or an issue with StoreKit on-device cache, but seems to me like a bug on Apple's side either way. Are we missing something? Is this a known issue? Any guidance or timeline from Apple would be greatly appreciated, as this is blocking legitimate paying users.

Hey everyone, I’ve noticed a big drop in my keyword rankings lately, and it seems linked to Apple’s recent ASO update that’s been trending on Twitter. Has anyone figured out what changed? It looks like app titles may now have less impact on rankings.

Erro na App store persistente de preenchimento de senha , não conseguindo baixar app ou reinstalar app excluido

I am posting here to express my significant concern regarding the excessive time my Apple Developer Program account application has been held under review. It has now been over a month. This application is for a non-profit church service app. I have provided every single piece of documentation requested—and then some. It honestly feels like I've submitted enough information that if they asked for the original blueprint of the church building, I could hand that over too. The entire process is currently stalled, preventing a service-oriented application from being deployed and ultimately hindering our outreach efforts. Has anyone else experienced a review period this long for a clear-cut non-profit application? More directly, to the Apple Developer Team: What is the current expected timeframe for approval, and why is this particular application still pending after more than 30 days, despite comprehensive documentation? This delay is beyond frustrating and needs an immediate resolution.