In order to submit my new subscription for review I need to upload a screen. No matter what resolution image I upload it fails saying "Your file could'nt be save. Try again if the problem persists, contact us" I am using many different types of simulators (Iphone 15 - Iphone Xs) and physical devices to take a screenshot and nothing is accepted. I can see the error message being returned from apples API is "IMAGE_BAD_DIMENSIONS_SM_LESS_MIN" so assume its a resolution issue. I am following the current guidelines here: https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications

Hello, We are seeing some confusing output from an App Store Connect API service: https://developer.apple.com/documentation/appstoreconnectapi/list_all_price_points_for_an_app curl -H 'Authorization: Bearer <REDACTED>' 'https://api.appstoreconnect.apple.com/v1/apps/354902315/appPricePoints?limit=200&filter[territory]=USA' { "data" : [ ... ], "links" : { "self" : "https://api.appstoreconnect.apple.com/v1/apps/354902315/appPricePoints?filter[territory]=USA&limit=200", "next" : "https://api.appstoreconnect.apple.com/v1/apps/354902315/appPricePoints?cursor=AMg.AMZSC44&filter[territory]=USA&limit=200" }, "meta" : { "paging" : { "total" : 658, "limit" : 200 } } } The above API call is successful for us and returns a list of price points for the app. However, it appears to be missing some values - the full set from the above API call indicates that there are 658 entries, but if we call the same service for a different app there is a larger result set: curl -H 'Authorization: Bearer <REDACTED>' 'https://api.appstoreconnect.apple.com/v1/apps/947178208/appPricePoints?limit=200&filter[territory]=USA' { "data" : [ ... ], "links" : { "self" : "https://api.appstoreconnect.apple.com/v1/apps/947178208/appPricePoints?filter[territory]=USA&limit=200", "next" : "https://api.appstoreconnect.apple.com/v1/apps/947178208/appPricePoints?cursor=AMg.AMeaC5w&filter[territory]=USA&limit=200" }, "meta" : { "paging" : { "total" : 801, "limit" : 200 } } } Why is a larger set available for one app and not the other and how can I make the same set available for all of our organization's apps?

In App Store Connect, is an organization's Legal Entity name separate from the App Store display name? My organization currently has the same name for both App Store display name and Legal Entity name. It contains an apostrophe, which is desired on the App Store for brand consistency. However, an apostrophe is no longer permitted in the Legal Entity name (it was entered in before that restriction came into effect). If I remove the apostrophe from the Legal Entity name to satisfy compliance warnings, will that update the App Store display name as well? I ask here because I'm supposing that if I remove the apostrophe and it does update the display name, the input validation won't let me enter it back. Any help would be appreciated - thanks!

My app was rejected due to Wrong OTP issue. But when I test using the same credentials it works fine. I am not able to reproduce the rejected issue. How I will check that issue ? In our previous build getting same issue but after few communication it was approved automatically. May I know why it is happen every times?

We run automated app uploads to Appstore Connect and TestFlight from our company servers, which are behind a firewall. Our firewall is configured to allow connections to the HTTPS servers listed in the Transporter User Guide The problem is, Apple adds new servers (e.g northamerica-1.object-storage.apple.com) to this list without prior announcements and this breaks our automated uploads because our firewalls are not yet updated with the new servers. Transporter logs report vague errors which are difficult to correlate with the new servers that were added. For example, the error msg is: [06:45:19]: [iTMSTransporter] data: null [06:45:19]: [iTMSTransporter] } [06:45:19]: [iTMSTransporter] buildAssetSpi: class BuildRelationshipsBuildAssetDescription { [06:45:19]: [iTMSTransporter] links: class AlbumLocalizationRelationshipsAlbumLinks { [06:45:19]: [iTMSTransporter] self: https://contentdelivery.itunes.apple.com/<redacted>/iris/v1/builds/<redacted>/relationships/buildAssetSpi [06:45:19]: [iTMSTransporter] related: https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/builds/<redacted>/buildAssetSpi [06:45:19]: [iTMSTransporter] } [06:45:19]: [iTMSTransporter] data: null [06:45:19]: [iTMSTransporter] } [06:45:19]: [iTMSTransporter] } [06:45:19]: [iTMSTransporter] links: class ResourceLinks { [06:45:19]: [iTMSTransporter] self: https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/builds/<redacted> [06:45:19]: [iTMSTransporter] } [06:45:19]: [iTMSTransporter] } [06:45:19]: [iTMSTransporter] [2024-03-11 06:45:17 GMT] <main> DBG-X: Returning 1 [06:45:19]: iTunes Transporter output above ^ [06:45:19]: <redacted>.ipa11966153618006795338-swinfo.plist (1) - Bad Status received from server: 401 The above error had nothing to do with authentication or incorrect tokens. We solved it by adding "northamerica-1.object-storage.apple.com" to our firewalls and retrying appstore connect upload. I'm trying to figure out ways to solve this problem. Is there any way to subscribe to Apple notification emails/RSS feeds etc to get to know about new servers being added ahead of time ? Are the wildcard domains - *.object-storage.apple.com *.blobstore.apple.com sufficient to cover any new server that Apple adds to the list mentioned in the Transporter Guide ?

While this isn't an issue directly related with programming, I would like to share my frustration with Apple Care and their knowledge of how App Store and third-party apps work. Perhaps someone at Apple can do something about it. Every now and then a user of one of my apps contacts me asking why they get an error when downloading or updating the app in the App Store ("Unable to Download App. “App” could not be installed. Please try again later."). I tell them that third-party developers have no power over the App Store or its download/update process, and this is an issue they have to solve with Apple Care. But when they contact Apple Care, they are told that since it's an issue with a third-party app, they have to contact the app developer. Sometimes the user is more inclined to believe what Apple Care tells them and they get angry at me. In any case, I feel helpless and frustrated, because I would love to help them, but have no means of doing so. There is something about the concept of App Store that makes some users believe that third-party developers have more power than they actually have: sometimes, for example, users contact me directly, or even leave reviews on the App Store, asking for a refund, which of course only Apple can do. Have you had a similar experience? Can some engineer at Apple instruct Apple Care that third-party developers cannot help with App Store download/update issues, so that App Store users don't get mad at the app developers for not being able to install/update their app?

I am trying to use the AppStoreConnect API to set the price of an app. In the documentation (here) it suggests that it is possible to set the price using the API. "To set a price for your app using App Store Connect API, create a relationship between the apps resource and appPrices" However it links to the instructions on how to set a price using the AppStoreConnect web site. Looking at the website it appears that the pricing is being set by sending a PATCH to the app record itself but on the API this results in a 405 (METHOD_NOT_ALLOWED) Is it possible to set a price using the API, and if so what endpoint should I be sending to?

Before Apple Silicon was a thing, I published a separate version of my iOS app for macOS. I'm no longer able to maintain this version, so I would like users to be able to use the iPadOS version of my app on Apple Silicon. Unfortunately I can't make it available through Prices &amp; Availablity, because it says: "Once your macOS version has been approved, your iOS app will no longer be available to Mac users." (translated from the German user interface) How do I remove the previous version and publish the iPadOS version to the mac app store?

I have several apps that contain extensions. For example an App Clip, Widget, Background Assets extension, etc. In Xcode Organizer Version 15.3 (15E204a), attempting to view crash data for these apps results in a failure. I have explicitly seen this error print out the app clip extension bundle identifier, as well as the background assets extension bundle identifier. It says the following error: An error occurred preventing Xcode from downloading crashes list. "" failed with error: Access Restricted with bundle id: com.example.app-name.extension-name Is anyone else experiencing this? I created a feedback a few weeks ago, it seemed to coincide with the release of Xcode 15.3 and or the new App Store Connect metrics APIs. App IDs and bundle identifiers detailed in the feedback if anyone at Apple wants the info. FB13677615 - Xcode: Cannot download crashes for apps that containg extensions --> "Access Restricted with bundle id:

Today the Connect page asks me to confirm if I am a trader or not under DSA. I am an independent developer and have several apps in App Store. I have no idea what a trader is. The DSA defines a trader as “any natural person, or any legal person irrespective of whether privately or publicly owned, who is acting, including through any person acting in his or her name or on his or her behalf, for purposes relating to his or her trade, business, craft or profession.” If you have questions about your status as a trader, consult with your legal advisor. I emailed Connect support but their reply is very "official" which confuses me more.

On App Store Connect, we're required to upload a screenshot of in-app purchase screens to submit them for approval. Unfortunately the uploader only seems to work about 5% of the time, with it failing (see screenshot) every other time. I've tried several different browsers and it's the same every time. Can something please be done about this? It's not acceptable for the developer tooling to be this buggy, and it's preventing many people from being able to submit in-app purchases.

The docs here: https://developer.apple.com/documentation/appstoreconnectapi/certificatetype Imply that you can create a certificate with a certificateType of PASS_TYPE_ID_WITH_NFC or PASS_TYPE_ID. However, when using the API, I get a 404 or a 403 status code when attempting to use them. Additionally, there is no documented way to associate the certificate to a particular bundle id for the pass type. Has anyone been able to successfully create a certificate for passes? If so what request did you send?

Hello! In our applications we consume several 3rd party libraries that use one or more API from this list - https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api?language=objc. These XCFrameworks contain static frameworks (a framework with a statically linked binary inside), so after linking, the machine code inside these frameworks becomes either a part of the app's executable or a part of a dynamic library. We integrate these libraries using Swift Package Manager's ".binaryTarget" feature and have been having trouble understanding where should the privacy manifest be located in the final app, so that we can pass the App Store review process. It seems that with SPM the privacy manifest (PrivacyInfo.xcprivacy file) is lost - https://github.com/apple/swift-package-manager/issues/7317 If the static framework is linked as a part of the app's executable, does that mean we have to manually merge the app's privacy manifest with that of a 3rd party static library? If the static framework is linked as a part of a dynamic library within the app, where should the privacy manifest be located? And what should happen if there are multiple static frameworks each with a privacy manifest being linked into this dynamic library? Thank you very much!

Our team uses a static library (.a) consisting of C and C++. Our team is developing static libraries internally and not sharing them to the outside. Should we still provide 'Privacy Manifest' in this case?? I added the contents of our team's static library (.a) to the app's 'Privacy Manifest' and there was no problem. Nevertheless, if I have to add it separately to the static library (.a), should I create a new framework project itself and not use the .a? Or can I just create a new framework and wrap the .a file??

I'm trying to submit an app that we have successfully tested in TestFlight. After completing all the distribution steps and submitting for review, the review is failing with the response: "Your app version was rejected and no other items submitted can be accepted or approved. You can make edits to your app version below." I haven't received an details in app or via email to provide further information. The version in TestFlight that I have uploaded is: v1.0.23(23). When entering the distribution details, and from the rejection response., it looks like the version number I'm entering on the main distribution page is the issue - maybe? I have tried entering 1.0.23, 1.0.23(23), even just 1.0 - but it constantly keeps getting rejected. Is it really the version no. that is wrong, or potentially something else? How can I get more information on why the submission was rejected?

Hello, With the new App Store Connect, iOS apps become available on the new Macs with Apple Silicon natively. A couple of my apps got quite some complications with Catalyst and do not need it anymore. I would like to know how to completely remove a platform from App Store Connect, without impacting the iOS version, so that I can let my iOS app be available on the Mac App Store instead of the Catalyst app. Thank you

Hi, We aim at delisting our MacOS app from the Mac App Store, so that it is no longer available for new users, while maintaining uninterrupted access for our existing MacOS user base. However, this MacOS app is associated to an iOS app in the same app group. Our current challenge lies in the process of removing the older MacOS app from sale without affecting the availability of the associated iOS app. We have explored the "remove from sale" option in App Store Connect, but it appears to be common to both MacOS and iOS, preventing us from delisting the MacOS app separately. We'd like to understand if there is a way to remove the MacOS app from sale without impacting the associated iOS app. If there are any alternative solutions or best practices that can help us achieve this, we would greatly appreciate your advice. Any advice or suggestions you can provide would be highly appreciated !

I know that most people on this forum will likely not be lawyers, but I am hoping someone with experience or insight can point me in the right direction. I am trying to publish an application to the iOS app store and getting ready to publish, but I never addressed the part about export control documentation. I use some hardware components made in the UK, and the only cryptography I'm aware of using is HTTPS and AES-128 (LoRa security) in the hardware. My app will only be available in the U.S. I will not be exporting any data or hardware, and everything I am hosting my application on is in the U.S. Does my application still fall under the EAR? Or is it something else I am supposed to be looking for? Someone I originally asked this about said that simply using imported hardware means it falls under the EAR, but that doesn't make sense to me. I am new to all of this, so if anyone can at least point me in the direction to look or has experience, that would be greatly appreciated.

I currently have an app listed in the App Store under my company's name. Recently, we restructured our company and adopted a new name that better reflects our product. My question is: Can I update our company name and DUN (Data Universal Numbering) number in the App Store, or do I need to create a new account for our restructured company? Alternatively, should I submit the updated version of the app under the original company name and DUN number?

In my iOS app, I'm planning to use CryptoKit to decrypt a data file downloaded remotely from my backend servers. I'm only using standard cryptography provided by iOS itself (Swift CryptoKit framework). According to App Store Connect documentation: "You're required to provide documentation if your app contains any of the following: Encryption algorithms that are proprietary or not accepted as standard by international standard bodies (IEEE, IETF, ITU, etc.) Standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple's operating system" I assume that since I am only using cryptography provided by the underlying OS itself, I can safely set ITSAppUsesNonExemptEncryption to NO. Can someone provide me with some guidance or opinion? Thank you!