Since yesterday when I try to open App Store Connect app on iOS I get: app store connect is temporarily unavailable due to planned maintenance On the desktop website there's no problem and also on Apple Services status website there's no outages. Someone having the same problem?

We’re looking forward to completing our review, but we need additional information about your app's cryptocurrency exchange services. This information is required to review the app for compliance with App Review Guideline 3.1.5(iii), which requires exchange services only be offered in countries or regions where the app has appropriate licensing and permissions to provide a cryptocurrency exchange. Next Steps Please provide the following information and/or documentation: Confirm in which specific countries or regions you intend to make your app's cryptocurrency exchange services available. Provide documentary evidence of the licensing and permissions for the cryptocurrency exchange services in your app for all of the countries or regions where your app is available. The documentation you provide should indicate where you intend to distribute your app. Provide links to government websites that display the licenses you've secured to provide exchange services in all the countries or regions where your app is available. Provide information on the third-party exchange APIs that your app connects with, including links to public APIs and documentation of partnership with specific third-party exchanges. Do the cryptocurrency exchange transactions occur between the users and the exchange(s) or do you, as the developer, handle the transaction requests with the exchange(s) directly? Are the cryptocurrency exchange features provided in your app decentralized, centralized, or a mix of decentralized and centralized exchange features? Does your app offer new or exclusive tokens or cryptocurrency to users? If so, which ones and on which exchanges can users obtain the currency? Explain the precautions you've taken to comply with anti-money laundering ("AML") and Know Your Customer ("KYC") requirements. If you intend to distribute your app in the United States, provide a copy of your Money Services Business (MSB) registration. Additionally, confirm that you will restrict your app's availability to the states listed on your MSB registration. I'm so confused about this. The reviewer has mention about cryptocurrency exchange services. We enrolled as an organization, in our app doesn't provide cryptocurrency exchange. We just provide decentralized application for users to easily interact with our smart contracts. Basically, all transactions calling smart contracts are generated by our DApps and presented to the users for further verification (meta mask, trust wallet etc) before being sent to the blockchain. So, our app doesn't have any control of user crypto assets. I have no idea. If we need licensing and permissions for the cryptocurrency exchange services. Because, we don't provide cryptocurrency exchange in our app. Am I missing something? anyone can help me to explaine for this case? Thanks

Hi all, I’m currently developing an App Clip, and for our first version, I want to exclusively use the default app clip link generated on App Store Connect to invoke the App Clip (of the form https://appclip.apple.com/id?p=<bundle_id>). I've published a build to App Store Connect, and I can see it has generated the link.
 There is good documentation around testing App Clip invocations when using an associated link pre-release, but not so much for testing the default link.
 I've read some things online that would suggest that the default App Clip link is not able to be tested before App Store approval, as the link only becomes active at this point. If that is the case, can we test the default App Clip link invocation via an external beta TestFlight release, or do we need to fully release the app to the App Store to test the link invocation?
 Any insights or experiences you could share would be greatly appreciated.

I see that there's an updated requirement for iPad screenshots (iPad 13"), but there's no info on the screenshot specs page and the device bezels are outdated

We have identified Subscription Groups for our use-case based on the below note from Apple, but there is no mention of any limitations in the doc. Can we create unlimited number of Subscription Groups or is there a limit? If your app needs to offer users the ability to buy multiple subscriptions — for example, to subscribe to more than one channel in a streaming app — you can add these subscriptions to different groups. Users who buy subscriptions in multiple groups will be billed separately for each subscription. Thanks in advance!

Hi, our app has been using single size app icon for a while and today when I trying to upload a new version of our app I got an email from App Store Connect saying ITMS-90013: Corrupt Image File - The image file 'AppIcon60x60@2x.png' appears to be corrupt. We haven't touched the image for ages and these 60x60 image were generated by Xcode from the single 1024x1024 image supplied. I've tried to use a new image and still got the same error. Does anyone experienced this recently?

I have already created consumable in-app purchases in App Store Connect which are available in my app. Then I created a "Discount Code" UIButton which presented custom UI for the user to input a code for another in-app -purchase at a lower price but that build was rejected because you cannot have custom code for this sort of thing. Ref: Apple Documentation: presentCodeRedemptionSheet() Finally I got it through review when I changed the UI but then I realized that I can't offer a free consumable in-app purchase. The minimum price is US$0.29. I would prefer a free consumable in-app purchase to give to freelancers I am owkrin with for them to test the app with. I know that there are ways to do it when using subscriptions but my app only using consumable in-app purchases which align better with my business model and the value offering of my app. There must be some way of creating a single-use free consumable discount code which will also get through App Store Review. Anyone managed something like this? Thanks.

Upon attempting to load an .ipa file from our build system into Apple Transporter 1.3 (newly updated this week from 1.2.5), the following error was presented. This occurs when selecting the file to load (or drag/drop the .ipa file onto the app). Never seen this before and it is unclear what the issue is (and why it might persist for 24 hours) or why it mentioned macOS App. This is an iOS/iPad app (not a macOS app) but the iPad app can be installed on a Mac as many iPad apps can. I had another Mac with the 1.2.5 version of Transporter and the same file was loaded (and then uploaded to the App Store) without a hitch. Does anyone have any idea or has seen something similar?

On our CI (GitHub Actions) we are signing our .ipa with codesign and after that uploads the resulting .ipa with altool to TestFligt. The problem is that the entitlements added by codesign no longer appear when we view the build on TestFlight. The app requires entitlements for push notification and for associated domains. codesign -s Distribution prod.entitlements prod.ipa Immediately after we do a codesign --verbose --display --entitlements - and the entitlements show fine. Next command is xcrun altool --upload-app --type ios -f prod.ipa --apiKey $api_key_id --apiIssuer $appstore_api_key_issuer To us it seems like altool strips the entitlements from the .ipa. What are we doing wrong?

This bundle is invalid. The value for key CFBundleVersion [1.0.1] in the Info.plist file must contain a higher version than that of the previously uploaded version [5]. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion (ID: 978303b8-eb71-4d71-9169-b0b0860fd8ec) The issue is an error while uploading macOS version 1.0.1 to the App store. If I want to solve it simply and quickly now, do I have to skip 1.0.1 and upload version 5.0.1 right away? I made an inquiry to Apple, but they only asked me to ask the forum or provide technical support. I would appreciate it if you could reply even if it's not accurate. I don't know if the problem is mine or Apple's problem, so I can't solve it for a long time.

Below, I have a button designed to facilitate the purchase of a subscription, which depends on the availability of the subscription in App Store Connect. This button is visible when testing locally using a StoreKit Configuration File synced from App Store Connect, and I have linked my subscription to my app in the information section. Currently, my app is in a "waiting for review" status, and the subscription is marked as "developer action needed - rejected." However, this issue of the button not appearing persisted even when the subscription was previously in the "waiting for review" status, indicating that the problem may not be related to the subscription status. I'm encountering an issue where the 'request products' function returns no results in the TestFlight environment, even when using a sandbox Apple ID. This problem has led to repeated rejections of my app, as testers are unable to verify its functionality. What could be causing these issues? VStack { if storeVM.subscriptions.isEmpty { if storeVM.isLoading { ProgressView("Loading subscriptions...") .progressViewStyle(.circular) .scaleEffect(2.0) .padding() } else if let errorMessage = storeVM.errorMessage { Text("Error: \(errorMessage)") .foregroundColor(.red) .padding() } else { Text("No subscriptions available") .padding() } } else { ForEach(storeVM.subscriptions, id: \.id) { product in Button(action: { Task { await buy(product: product) } }) { HStack { Spacer() Text("Unlock 3-day free trial. \nThen $23.99 per year. Cancel anytime.") .font(.custom("Lora-VariableFont_wght", size: 20)) .foregroundColor(.white) .lineSpacing(5) Spacer() } } .padding() .background(Color.black.opacity(0.6)) .cornerRadius(10) .padding(.horizontal, 10) } } .onAppear { Task { await storeVM.requestProducts() } } func requestProducts() async { isLoading = true errorMessage = nil do { subscriptions = try await Product.products(for: productIds) isLoading = false } catch { print("Failed product request from App Store server: \(error)") isLoading = false errorMessage = "Failed to load products" } }

Queria saber como altero a linguagem do meu aplicativo postado, pois escolhi tudo português no cadastro do App e quando foi publicado aparece o idioma EN(Inglês) na App Store. Não sei mais o que fazer, alguém pode me ajudar por gentileza.

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 ?