Hello, for applications using Signin with Apple feature, it seems a particular process needs to be followed when you want to transfer the app to a new owner. Generating transfer identifier before the transfer of ownership to identify a particular user. There is already "email" registered for the user, personal email or relay email (doesn't matter). Why would we need to trouble ourselves with the transfer identifier? The documentation doesn't explain anything about the background of this. It is very weak. It doesn't explain the impacts/changes when app is transferred so that one can fully understand its impact. Thank you.

Hi everyone, We’re trying to publish our app in the European Union. I’m the Account Holder, and we’ve hired an external development team to build the app. When they attempt to submit the app, they receive the following error message: “To submit this app version, you must first set up your account for alternative payment.” I’ve read that I need to configure this in App Store Connect, so I logged in at https://appstoreconnect.apple.com. According to documentation, I should go to the Business section and look for “Alternative Payment Methods” or “StoreKit External Purchase Entitlement,” but I cannot find any such option in the interface. All agreements in the Agreements, Tax, and Banking section are marked as Active, so that shouldn’t be the issue either. What am I missing? Is there a specific entitlement I need to request first, or something else I need to enable? Thanks in advance for your help!

Hello community, I'm facing a very frustrating issue for several days with successive rejections for the same guideline 3.1.2 regarding Terms of Use, despite my efforts to comply with the requirements. The problem: Apple keeps rejecting my app saying: "The app's metadata is missing the following required information: A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App Description." What I have already implemented: In the application: "Terms of Use Apple" links present on ALL purchase pages (signup, premium, boosters, settings) Functional link: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/ Complete subscription information (duration, price, features) In App Store description: Dedicated line: "Terms of Use: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/" In App Store Connect: "Privacy Policy" field filled Description updated with links My frustration: I feel like it's a bot responding to me because I receive exactly the same message every time, without taking into account my detailed explanations and evidence that I have everything in place. I'm even trying to add elements that aren't necessary out of desperation, but nothing seems to work. Questions: Has anyone else encountered this problem recently? Is there something specific I'm missing? Does the exact format of the link in the description matter? I'm really desperate after several rejections for the same reason. Any help or advice would be greatly appreciated! Thanks in advance for your help.

My app keeps getting rejected by Apple Review team. This is their reason: The app still exhibited one or more bugs that would negatively impact users. Bug description: your app was unresponsive to scan provided code or barcode on website before we purchased the subscription. Review device details: - Device type: iPhone 13 mini and iPad Air (5th generation) - OS version: iOS 18.5 and iPadOS 18.5 We have tried our own devices but it works fine for us. We aren't able to reproduce the issue. What should we do?

Looking for a solution: our app name is read more clearly when it is lower-case. We have submitted it to the store in that format, and it shows up on the App Store that way, but when it is sent to the devices, it changes to upper case. I am not seeing results on why this is happening or how to change it. The app name is 1on1 Piano, and when it is downloaded on the device, it changes to 1ON1 Piano, which people often mistake for "ioni piano" and "10 and 1 piano," so we would like it to be consistent with our branding where "on" is lowercase.

Hello, why Apple use a generic billing descriptor for charges (e.g., "APPLE.COM/BILL", "APL*APPLE"), which does not include the app name? As a result, unexperienced users associate any Apple charge on their bank statement with our app, even if it's a charge from another app or service they’ve used. This is leading to: Confusion and mistrust from our users An increase in wrongful refund requests Support burden for an issue outside of our control We kindly request Apple to consider including the app name in the billing descriptor (like Google Play does). We understand Apple manages all billing, but the current setup causes confusion that unfairly impacts our app’s reputation and support load. Thank you

Due to the violation of the rights to the font, my application was deleted. I resolved the issue with the copyright holder, they unsubscribed at AppStoreNotices @apple.com , but there has been no response for 6 business days already. How long can the response take? Is it possible to contact us about this issue in any other way or speed up the process?

I purchased a Mac mini to register for the Apple Developer program, but it doesn't have a camera. Therefore, during the registration process, I tried using someone else's phone to continue, but it failed and I couldn't continue. I contacted customer service many times, but their response was the same: they couldn't solve the problem. My software and game have been developed, so I really need an account to sell them. I hope the Apple official website can give me a chance to register again. Thank you very much.

My app was accepted onto the app store yesterday, but i just found out that my subscriptions were rejected for some reason. The localization of each subscription said there was something wrong with it so i changed them and resubmitted them. The issue/question that i have is that now that my app has been accepted with my 1.0.0 version, do i have to submit an update for them to review my subscriptions? or do they review the subscriptions separately because you have to submit the subscriptions for review, the same way you have to submit builds. I just don't want to be waiting around because i can't market my app without those subscriptions accepted

Hello, our submission rejected by the apple team and now we can't remove cancel the current submission. This is api response when we attempt remove: { "errors" : [ { "id" : "e069078e-4c57-4aa6-ab3b-913ddf9e6314", "status" : "409", "code" : "STATE_ERROR.ENTITY_STATE_INVALID", "title" : "Resource state is invalid.", "detail" : "Resource cannot be canceled at the moment, please try again later" } ] } We need to publish app asap and can't do anything because of this bug.

Hi Apple Developer Support, We're currently implementing auto-renewable subscriptions in a React Native app using the react-native-iap library. The subscription purchases are working as expected in Sandbox. We receive the transaction and purchaseUpdatedListener gives us a valid-looking transactionReceipt However, when we attempt to validate this receipt with Apple's servers, the response consistently returns status code 21002, indicating that the receipt data is either malformed or missing. We’ve confirmed the receipt is well-formed, properly passed as received, and well above the minimum size expected. The shared secret is correctly configured and matches the subscription group. We're using the correct sandbox endpoint and ensuring no modification is done to the receipt before validation. Despite this, validation fails every time. We are looking for guidance or clarification on what might cause this status, especially when the receipt is coming directly from the system after a successful test purchase. const purchaseUpdateSub = purchaseUpdatedListener(async (purchase) => { console.log("🛒 Purchase Updated:", purchase); const receipt = purchase.transactionReceipt; if (!receipt) { Alert.alert("Error", "No receipt found."); setLoading(false); return; } }); the response is: { "status": 21002 } Any guidance on why this might be happening would be appreciated. Thanks!

Hi all, We currently offer 12 auto-renewable subscription plans on the App Store. We’re looking to remove (delist) a few of these subscriptions so they are no longer visible or available for purchase by new users — but we want to ensure existing subscribers can continue renewing without any issues. To clarify: We are not changing the subscription type or pricing. There are no in-app code changes involved. This is purely about managing subscription visibility and availability in App Store Connect. Can anyone confirm: Is it possible to hide specific subscription products from new users while keeping them active for current subscribers? What are the exact steps in App Store Connect to do this? Thanks in advance for the guidance!

Hi, so we are developing app in Flutter and had enabled iPad because it is the only apple device we have. First submission was with ipad enabled in xcode so it is ok that it was rejected as app is not ready for ipad with issue Guideline 4.0 - Design. But then we have disabled ipad support in xcode and with editing file directly as xcode did not disabled it everywhere in the file (worst IDE I have ever seen). Everywhere in project.pbxproj we have TARGETED_DEVICE_FAMILY = "1" so this should support only iphone. For building we use Xcode Cloud. What else can we do to disable ipad support and not get rejected in app review? In Google Play disabling support for device is 3 clicks.

I am planning to gradually phase out the app and make it unavailable for new users. However, we would like to ensure that users who have already installed the app can continue to receive updates and support during this transition period. Please advise if this is possible? If so, what are the necessary steps or settings we need to configure in the App Store Console to achieve this? In addition, I would appreciate your guidance on the following questions: What is the process for uploading or releasing an update for an app that is currently "Removed from Sale"? If an app is "Removed from Sale", can it be republished later? What are the steps to do that? Are there any limitations when changing the app’s distribution region (e.g., is there a maximum number of times the region can be changed)? Thank you.

My application has been in "In Review" status since May 30, 2025, and it is still in that status today. Please check the status of my app, LS Tools. Our customers are waiting for the latest version

I want to clarify why both email and phone number are mandatory at registration, while still allowing users to log in with either method if one fails. Email Address (Collected at Registration) Account Creation & Verification: We use email to establish a unique, verifiable account for each user. This prevents duplicate or fraudulent profiles. Primary Communications: All booking confirmations, trip updates, support requests, and in-app chat messages between care seekers and carers are sent via email. This ensures users have a reliable record of every transaction and message. Phone Number (Collected at Registration) OTP-Based Security: We send a one-time password (OTP) via SMS during registration and login. This SMS-OTP step is critical to confirm that the user owns the provided phone number and to safeguard against unauthorized account access. Critical Trip Notifications: During a booked trip, carers and care seekers must receive time-sensitive alerts (e.g., gate changes, flight delays, check-in reminders) even if they’re not actively using the app. SMS ensures immediate delivery—even if a user’s internet connection is unavailable. Support & Emergency Contact: If there’s an urgent issue mid-trip (e.g., a missed flight, sudden cancellation, or a medical concern), our support team can reach users directly via phone to resolve issues in real time. Flexible Login Options Fallback Mechanism: If a user cannot access their email (e.g., server delay or no internet), they can request an OTP via SMS to log in. Conversely, if SMS delivery fails (e.g., network outage), they can choose to receive a OTP by email. This redundancy guarantees that users aren’t locked out due to a single point of failure. We believe both email and phone number are directly tied to our app’s security model, communication requirements, and overall user experience. All collection and usage details are transparently disclosed in our Privacy Policy (https://b4t.com/legal/privacy-policy) and User Terms and Conditions (https://b4t.com/legal/user-terms-and-conditions).

Hello The other day, my app was rejected by App Store. The person in charge told me, "Your app still provides the same feature set as other apps submitted to the App Store for review." Does this mean I can't publish my app anymore?

I was contacted to develop an app for a company and I’d like some help to know if it has a chance of being approved on the App Store. The system will be entirely built in React Native and will use a SupaBase backend. One detail: before starting, I talked to another developer who ended up dropping the project because he thought it would be impossible for the app to be approved on the App Store due to the use of WebView and because it’s a simple app. How the app works: There’s a home screen showing all the company’s units. When you tap on a unit, it shows its details. On the details screen, there’s a button that opens an internal exam consultation system in a WebView. The rest of the app (navigation, data display, etc.) is all react native. The app also stores those informations offline. My questions: Can using WebView just for this exam consultation part be a problem for approval? Does adding offline storage really help increase the chances? Is there any way to distribute the app without going through the App Store? I appreciate any information you can share.

My app uses Apple IAP. With the recent US external payment changes (May 2025), I plan to use Stripe via Superwall. Superwall allows me to remotely toggle my paywall for US users between Apple IAP and Stripe checkout without a new app build. Is it permissible to activate Stripe for new US users on an already live app version (approved with only Apple IAP) without first submitting a new build for Apple to review the Stripe integration? Or does this dynamic switch create a risk of takedown/compliance problems? Concerned about new users hitting an unreviewed Stripe flow during any potential review period for a new build. Seeking clarity on Apple's stance or community experiences. Thanks!

Hello, Can anyone help me with the below? I've been sent the below bolded, italicized message three time in a row now with no further explanation. _**Please note that links are required to be included in both of the metadata and the binary. We noticed that your app binary is still missing: A functional link to your privacy policy A functional link to your Terms of Use This information is required for apps which include auto-renewable subscriptions.**_ My reviewer initially instructed me to include my terms of use link in my app description (as my privacy policy was already displayed). I followed that instruction and that subsequently started the persistence of the bolded, italicized message. For full context, the links are in my app description and on my paywall inside of the app itself. I need help and clarity on what I'm missing so I can get the app approved. Also, if anyone knows any alternative ways of allowing users to purchase a subscription within the app that Apple allows - I would appreciate that information, as it seems this process is too complicated for me.