The documentation says I can update images when the app is in states: Prepare for Submission Ready for Review When I submit a new version it goes from Ready For Review to Waiting For Review within the same minute. Did I do something to make it go to Waiting For Review? Is it only in state Prepare For Submission before I submit the first version or can it be in that state for subsequent versions? Why do they make it so hard??? When and how can I update app store images on existing app?

Hello, I have a few questions about increasing a price increase for an existing subscription on an iOS application: 1.) Is it possible to test the price increase in the sandbox environment? If so do I have to plan the scheduled increase first or can I create this scenario in the sandbox environment without any scheduling? I ask because id like to test the new price update in some of the local code first without having the risk of a user getting notified that a price increase is coming before the app is ready to display it properly. 2.) When a price increase is scheduled say two weeks out, but then its determined that we need to cancel it by deleting it from app store connect. Are users that were potentially notified of the price increase via the consent form notified a second time that it has been cancelled? Thanks for any help!

What happen when a deprecated method is used in project submitted to Apple Store Connect ? Generally the Apple documentation give the alternative like "Use ***: instead" but sometime the documentation do not suggest anything. What to do when a such Warning happen ?

Can I use the same bundle ID for different developer accounts? I want to use a separate account for different environment schemes (DEV, QA, UAT) and PRODUCTION but I want to use the same bundle IDs.

I'm just want to create a sandbox test account, but when I click the sandbox, it just glance in a second, and then display nothing but white page. Any one had encounter this problem? My account works fine until this problem, I don't know the reason.

Hi There! I released an app called Taino VPN with Russian IP on AppStore a month ago. After that, I updated the app successfully several times with minor fixes. Last time I submitted a new release with only small metadata and keyword updates and got rejected by Guideline 4.3(a) - Design - Spam. Original message is "We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences." I'm now very confused! On Apple's official website Guideline 4.3(a) says: Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase. It does not make any sense because I have only 1 app developed from the scratch by me. Also, it does not match with Original reject message and 4.3(a) says nothing about other developers. I hope apple review support could guide me on it. Looking forward and thanks!

Hello I'm developing a React Native application and I added IAP (like subscriptions) to my app. For it I user react-native-iap, I suppose It's the most common library to integrate in-app purchases. So, I created 3 subs on App Store Connect and tested it on the iOS simulator. Firstly I was receiving the empty array instead of subs data, but when I have been add StoreKit to my project I became to receive an appropriate subs data with all corresponding information. Moreover, I could successfully subscribe on them. But, when I released app on the TestFlight for internal testing I forced with the familiar issue, I received an empty array. In conclusion, on the debug version everything works (subscriptions data returns), but on the release I can't to receive the same result.

I'm adding my first in-app purchase to an app, and I'm finding the process incredibly frustrating. Aside from the Apple Developer Documentation not being clear enough, and kind of glossing over the technical steps required (and their sample code being woefully inadequate), App Store Connect and the testing sandbox simply don't work as they say they do. For example, in my app I've purchased the IAP and now I want to request a refund. I select the purchase, I choose a refund reason, and this page says, "To set up a test for approved refunds, select any refund reason on the refund request sheet, and submit the sheet. The App Store automatically approves the refund request in the testing environment." Well, when I re-launch the app the purchase is still there. I can't request a refund again because it says this is a duplicate refund request, so it knows that the purchase has had a request, and it's supposed to have automatically refunded it, but it clearly hasn't. So, I try clearing the purchase history via the Settings app > Developer > Sandbox Apple Account. Same thing. Purchase remains. Try clearing purchase history in App Store Connect. Same thing. How on Earth does anyone get an in-app purchase to work when the entire testing environment is so badly executed? How do I get past this? The IAP is the last part of the app that needs to be implemented, and I've lost a week on this already.

How do I fix this error when uploading my app to App Store Connect? validation failed invalid executable. the executable 'ridein.app/frameworks/cardinalmobile.framework/cardinalmobile' contains bitcode.

Hi all, Our app was initially rejected for 5 minor issues, which we promptly fixed and resubmitted within 24 hours. However, it was rejected again for 4 of the same issues, even though we 100% know they've been addressed. We submitted two follow-up messages to the App Review team via App Store Connect over 5 days ago but haven't received any acknowledgment or response. Does anyone know if we need to resubmit a new build with notes, or how long it typically takes to get a reply from App Review through App Store Connect? Thanks in advance!

Hello, I submitted a request to migrate my developer membership from individual to organization over 6 days ago. Before submitting this request I was told it was a "quick process". When I ask for updates, all I get is "we have confirmed that the team is continuing to review your case and we will contact you again once they have provided an update." I never get any said updates. Not only can I not submit my app, I've been locked out of TestFlight, meaning I haven't been able to send the app to beta testers. I'm curious, has anyone done this migration and how long did it take?

We encountered a weird situation recently. Our daily build process upload an app with a daily incremental 4-digit build number, e.g. 4000, 4001, 4002, etc. Our release build number has a specific requirement to use the date, such as 20240719. In the past I have learned that in order to upload a new build for the same version number, the new build number needs to be greater than the old one. Thus, if I have uploaded 200.1.0 (20240719), I cannot upload 200.1.0 (4001) anymore, because the daily build's build number is smaller than the release build. I have to expire the 20240719 build in order for the daily build to continue, which is fine. The problem is, yesterday I submitted 200.1.0 (20240719) for App Store review then got approved. While today's daily build is 200.2.0 (4001) and when it is uploaded, it got rejected for the following error message: This bundle is invalid. The value for key CFBundleVersion [4001] in the Info.plist file must contain a higher version than that of the previously uploaded version [20240719]. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion With error code STATE_ERROR.VALIDATION_ERROR.90061 for id [redacted] Asset validation failed (-19208) This befuddles me, because the 20240719 build submitted for review is in an older release version, while the daily build 4001 is using the newer release version number. It seems that TestFlight decided to compare build numbers while ignoring the version numbers?! Furthermore, after I canceled my approved submission for 200.1.0 (20240719), surprisingly the 200.2.0 (4001) can be uploaded without an error! 😲 It seems that the only factor is whether the build is submitted or not. If an older version number higher build (200.1.0 (20240719)) is not submitted, then TestFlight happily allows newer version number lower build (200.2.0 (4001)) to be uploaded. In contrast, if submitted, then 4001 is not allowed to be uploaded! Is it an expected behavior? Thank you for the patience.

I created a new Custom Product Page with a Deep Link, according to the WWDC '24 session "What's new in App Store Connect", and everything has been approved, but the Deep Link does not appear to be working. Is this feature fully operational yet? When the app is installed via this product page, the user should be directed to a specific page in the app, however this does not happen. It does work properly when installing directly via the Deep Link This is the link to the product page: https://apps.apple.com/app/bills-to-budget/id1636872963?ppid=ff079a93-be32-43fe-a88e-ad97a68ff725

We have developed an application that we sell to clients, and with their accounts, we have successfully published the build on the App Store. We have all the legal rights, including trademarks for the app icon and other assets, which are fully documented and verifiable. The application was initially sold to a client with the agreement that it would be published exclusively in the Asia region, and the client is currently doing so. Now, the main issue arises: We wish to publish the same application for the USA region, using our organization’s account to serve U.S. users. However, our app submission is continually being rejected by the App Store review team, citing that the app icon is already in use and requesting a change. We are not in a position to change the app icon, as it is integral to the branding and trademark rights we hold. If anyone has experience with this issue or can provide guidance on how to proceed, your support would be greatly appreciated !!

I'm trying to upload a new version of my app, and my Apple Developer Program contract is active until 2026. However, I'm receiving the following error: 'A required agreement is missing or has expired. Sign the agreement on the Apple Developer Program to resolve this error.' How can I resolve this issue?

Hello, I’ve been experiencing an issue with the Quebec QST Form FP-2506-V that is preventing me from submitting my application. When I attempt to update my TQ number, I receive the error message: “The Tax ID entered already exists.” This contradicts the note on the form stating: “You can return to this form and update any numbers after clicking Submit.” Steps I’ve Taken So Far: Opened two cases with Apple Support (over three weeks ago). No response. Contacted Developer Support via email and phone – Unfortunately, they were unable to make the necessary corrections. Tried using the official contact form again – No success in getting a response or resolution. Emailed canada_tax(at)apple.com – Even though this email is meant for users outside of Canada, I reached out in the hope that someone could assist. At this point, I am completely stuck, as I cannot move forward with my application submission until this issue is resolved. Has anyone else encountered a similar problem? Is there another way to escalate this within Apple to get proper support? Any help or suggestions would be greatly appreciated! Thanks,

Hi Team, I hope this email finds you well. I currently have one Apple Developer account, which is an organization account. I would like to be part of another team (another app) and was wondering if it is possible for one developer to have access to multiple teams. If this is possible, does the access need to be provided by the owner of the account? For example, I already have one team assigned to me with the role of Admin (Team ABC), and there is another app from my team where I would like to be part of that team as well (Team XYZ) with the same Admin role. Am I allowed to be part of two teams in this manner? Please reply and share the process if it is allowed. If it is not, could you suggest a way to handle this situation? Thank you for your assistance. Anil

Hello, I want to update the prices in all territories of an auto-renewable subscription at once (in a single request). I know it's possible to do it territory by territory using the Create a Subscription Price Change API endpoint, but this means I need to call this API for every territory. And I have a lot of subscriptions I need to update. There is an another API endpoint that seems to allow to Modify an Auto-Renewable Subscription. For the countries where I want to change the price, I fetch the subscription price points using the List All Price Points for a Subscription API endpoint. When I call this API endpoint with the following body (that is the expected body content for this endpoint): { "data": { "type": "subscriptions", "relationships": { "prices": { "data": [ { "id": "eyJzIjoiNjc0MDAyMTQ5NiIsInQiOiJDQU4iLCJwIjoiMTAwMDEifQ", "type": "subscriptionPrices" }, { "type": "subscriptionPrices", "id": "eyJzIjoiNjc0MDAyMTQ5NiIsInQiOiJVU0EiLCJwIjoiMTAwMDEifQ" } ] } }, "id": "6740021496" }, "included": [ { "relationships": { "subscriptionPricePoint": { "data": { "id": "eyJzIjoiNjc0MDAyMTQ5NiIsInQiOiJDQU4iLCJwIjoiMTAwMDEifQ", "type": "subscriptionPricePoints" } }, "territory": { "data": { "type": "territories", "id": "CAN" } }, "subscription": { "data": { "id": "6740021496", "type": "subscriptions" } } }, "id": "eyJzIjoiNjc0MDAyMTQ5NiIsInQiOiJDQU4iLCJwIjoiMTAwMDEifQ", "attributes": { "preserveCurrentPrice": true }, "type": "subscriptionPrices" }, { "attributes": { "preserveCurrentPrice": true }, "id": "eyJzIjoiNjc0MDAyMTQ5NiIsInQiOiJVU0EiLCJwIjoiMTAwMDEifQ", "type": "subscriptionPrices", "relationships": { "subscription": { "data": { "type": "subscriptions", "id": "6740021496" } }, "subscriptionPricePoint": { "data": { "type": "subscriptionPricePoints", "id": "eyJzIjoiNjc0MDAyMTQ5NiIsInQiOiJVU0EiLCJwIjoiMTAwMDEifQ" } }, "territory": { "data": { "type": "territories", "id": "USA" } } } } ] } I receive a 409 error: { "errors" : [ { "id" : "5b6a4b62-686c-4a65-87ba-e16131db517b", "status" : "409", "code" : "ENTITY_ERROR", "title" : "There is a problem with the request entity", "detail" : "User is not allowed to edit.", "source" : { "pointer" : "subscriptionPrices" } } ] } I made sure my bearer authorisation token is correct and still valid (not expired). the p8 key has Admin rights Can this PATCH endpoint be used for what I want to do? If yes, is there anything special to do to use this PATCH endpoint? Thanks, Axel

Hello, I setup a leaderboard in the default language English and everything works and the app is live in the store. Now I am adding localization to the leaderboard and noticed than some languages have the data entry "Score Format Suffix" and some languages the data entries "Score Format Suffix (Singular)" and "Score Format Suffix (Plural)" instead. Is this an error or intentional? Kind Regards, Chris

hi There, I am trying to upload my app which contains the app for watchOS as well as iOS built on Xcode 15.2. I get this error when uploading the ipa using local command from mac as well as using bitrise online tool. [18:57:47]: Making sure the latest version on App Store Connect matches '4.2.0'... [18:57:47]: '4.2.0' is the latest version on App Store Connect [18:57:47]: Uploading binary to App Store Connect [18:57:48]: Going to upload updated app to App Store Connect [18:57:48]: This might take a few minutes. Please don't interrupt the script. [18:57:52]: [altool] 2024-02-27 18:57:52.359 *** Error: Unable to determine app platform for 'Undefined' software type. App Store operation failed. (1194) [18:57:52]: [altool] { [18:57:52]: [altool] NSLocalizedDescription = "Unable to determine app platform for 'Undefined' software type."; [18:57:52]: [altool] NSLocalizedFailureReason = "App Store operation failed."; [18:57:52]: [altool] NSLocalizedRecoverySuggestion = "Unable to determine app platform for 'Undefined' software type."; [18:57:52]: [altool] } This worked fine up until a few days ago but have stopped working since the info.plist changes went live forcing to use only one info.plist for the entire app to manage the bundle version and app version. thanks, -CJ