I have uploaded 5 binaries to the app store, intending to publish it, not to test it. Every time I do, the builds appear inside TestFlight marked as “invalid binary”. Why do they appear on TestFlight is a mystery... I have uploaded it by two methods, Xcode and xcrun altool. The app passes the validation. No reason is given, no email received from Apple. I have contacted Apple two days ago, and as expected, no answer. How can I discover what is going on?

Hi, Our organization has an app that serves as the remote control for an IoT device. The app is free, with no in-app purchases. Any person who purchases the IoT device can use the app for free to set up the device. Can I opt for non-trader status for the app?

I'm working with a business who is now offering to white label their service. This will greatly benefit me and the other clients they have. Currently, they have an app that allows us to communicate with their AI directly from our phones. Now that they are offering to us to white label their services to clients of our own, we would like to white label their app as well. The developer said that he doesn't want to fight with the Apple App Review Dept. because they reject apps that are too similar. Here is my suggestion: Since there will only need to be one more app added (we will all use the same "gray-label" nondescript app), there will only be two similar apps on the App store. That's hardly spamming. We don't need to create branded apps for each of us. We all simply want to be able to use the same gray-labeled, nondescript app instead of our partner's branded app. For example: His app is App_A. We want him to create an App_B that is not branded to his or our stores, but is generic enough that we can use it with our own clients. I've read the documentation (https://developer.apple.com/app-store/review/guidelines/#minimum-functionality) and many of the forums. But to be honest, it seems that the Apple App Review team arbitrarily chooses apps to approve and others to reject. Sometimes a simple icon change and the Review Team accepts. Other times, it's rejected. It doesn't seem like there is a clear distinction between who gets accepted or rejected. Still the solution which is offered by Apple App Review is to put all the apps into a container. This is not a solution as we need to direct our customers to our app, and our partner will not want to put his app into a container to share with other apps. I would like to work with someone to help push this gray-label app through. We only need one similar, gray-labeled app so that we don't have to use our partner's branded app. That will add much functionality to our offers. Plus, it will not be spam or clutter because our partner will continue to direct their clientele to their branded app, App_A, and we will all direct our clientele to the gray-label app, App_B. So there will be no confusion. I've heard of other solutions such as obfuscating the code or opening up a new developer account, as well. If there is anyway to work with a single person to help this project get pushed through, that would be very appreciated.

I received an email from Apple saying my app is using the following privacy-restricted APIs without an API declaration. NSPrivacyAccessedAPICategoryUserDefaults NSPrivacyAccessedAPICategoryFileTimestamp NSPrivacyAccessedAPICategorySystemBootTime It's true, my app is using those features, in multiple pods that I depend on. For example, my app depends on the FBAudienceNetwork cocoapod, and I've upgraded it to version 6.15.0, which added a privacy manifest specifically to ensure that Apple wouldn't flag my app with an error. https://developers.facebook.com/docs/audience-network/setting-up/platform-setup/ios/changelog/ I can see its privacy manifest explicitly covers these APIs, below: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>NSPrivacyTrackingDomains</key> <array> <string>ep1.facebook.com</string> <string>ep6.facebook.com</string> </array> <key>NSPrivacyCollectedDataTypes</key> <array> <dict> <key>NSPrivacyCollectedDataType</key> <string>NSPrivacyCollectedDataTypeAdvertisingData</string> <key>NSPrivacyCollectedDataTypeLinked</key> <true/> <key>NSPrivacyCollectedDataTypeTracking</key> <true/> <key>NSPrivacyCollectedDataTypePurposes</key> <array> <string>NSPrivacyCollectedDataTypePurposeThirdPartyAdvertising</string> <string>NSPrivacyCollectedDataTypePurposeAnalytics</string> </array> </dict> <dict> <key>NSPrivacyCollectedDataType</key> <string>NSPrivacyCollectedDataTypeDeviceID</string> <key>NSPrivacyCollectedDataTypeLinked</key> <true/> <key>NSPrivacyCollectedDataTypeTracking</key> <true/> <key>NSPrivacyCollectedDataTypePurposes</key> <array> <string>NSPrivacyCollectedDataTypePurposeThirdPartyAdvertising</string> </array> </dict> </array> <key>NSPrivacyAccessedAPITypes</key> <array> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryUserDefaults</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>CA92.1</string> </array> </dict> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategorySystemBootTime</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>35F9.1</string> </array> </dict> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryFileTimestamp</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>C617.1</string> </array> </dict> </array> <key>NSPrivacyTracking</key> <true/> </dict> </plist> So, why is Apple flagging my app with "Missing API Declaration" errors? The API declaration is right there. What am I still missing?

I am new developer and I did app for iPhone and it works fine at 17.2. environmen. Do I have convert it to something like 14.4. iOS version before It will be accepted into AppStore?

Hello, I'm unsure what option to select when it comes up to specify what type of encryption my app is using and if en export compliance is required to distribute my app in France. The app is using SSL certificates to communicate with a connected device, such as https works. I have to select one of the following options: 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 Both algorithms mentioned above None of the algorithms mentioned above Does SSL (RSA, SHA-1, etc.) falls under A) "standard encryption algorithms" or is that something that is provided by default on the OS and falls under B) "accessing the encryption within Apple's operating system" ?? If B) I would need to check the "None of the algorithms"-option because I do not use standard encryption "instead of, or in addtion to", only OS provided encryption. Am I right? Or does SSL is not used as standard in the OS and falls under A) ??

The error "Address validation failed. Please update the legal entity address" is encountered when attempting to rectify the issue. However, efforts to resolve this problem lead to another issue: "We are currently unable to process your request. Please try again later."

I have published the app on the App Store along with its corresponding app clip, my app clip is configured with some advanced experiences for each one of my clients, but whenever some users try to scan an NFC or QR Code they see the card rendering correctly with their configured banner image, but with the message "App Clip Unavailable". The weird thing is that both iMessage and the website to which the associated domain is set and the apple-app-site-association is stored, renders the banner or card correctly, and when the users tap the banner or card they open the advanced app clip experience correctly without any issue. I have attempted to troubleshoot the issue by checking the following: if the app clip is below 15MB if we are using a second level domain in my associated domain both for my app clip and app (excluding the www subdomain). checking if the AASA is correctly stored inside .well-known directory checking the configuration for the advanced experience I opened a case: 102233443873, and added a bunch of videos and screenshot showcasing the issue, but I have not yet received a reply

Hello, we are developing an open source vpn program that is developed with Flutter and native parts with Swift, and we plan to publish it on the App Store soon, but the project programmers say that you must have an account to publish this app on the App Store. On the other hand, my other friends say that this is not the case, and to publish a vpn app, only one Apple Developer account is enough, and there is no need for a business account!

Many unique app names are taken by apps that are not on the App Store. It would be nice if Apple could provide a convenient way to forward requests to the developers of those apps to remove or rename their app. This could appear in a developer's App Store Connect page as a notification on the unreleased app.

X button not working in the wish list page of itunes #713black

I am really stuck. I uploaded my Mac Catalyst app. The binary passes validation beforehand. I submit for review. After being in "waiting for review" for a couple of minutes it is rejected with "invalid binary" and comes back with an email saying "ITMS-90053: This bundle is invalid - The bundle identifier is already in use by a different software package." The only app that is using the same bundle is the IOS version where I added the Mac platform.

I know apple updated their policy related to sign in (see https://developer.apple.com/news/?id=f1v8pyay, "More flexibility for sign in options in apps" section), but the wording of the guidelines (https://developer.apple.com/app-store/review/guidelines/#login-services) is a bit difficult to understand: Apps that use a third-party or social login service (such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer as an equivalent option another login service with the following features: the login service limits data collection to the user’s name and email address; the login service allows users to keep their email address private as part of setting up their account; and the login service does not collect interactions with your app for advertising purposes without consent. As far as I can tell, FB, Google, Amazon, etc. do not offer these protections. Would Apple Sign In still be required in this case?

My app is only available in some regions. During one of the review versions, the reviewer asked to remove accessibility from one of the countries or provide documents that allow to conduct activities in this country. At that time, there was no such document and I removed the availability in this country. Now - I have a document that confirms that I can conduct activities in this country. Availability is a separate section and is not related to versioning. How and where do I request app availability in a specific country?

Need help as the the option to "make a version unavailable for download" is broken. 1- Go to the app store and select your app 2- On the left menu scroll down and click on "pricing and availability" 3- Scroll to the bottom to "Edit your last-compatible version for iOS apps" and expand the section 4- Click on the app versions 5- On the new pop-up window un-check the boxes for the versions you need to remove and click done. HERE IT IS BROKEN.

Hi, Can we install and use a XCode 15.2 on a MacBook Pro 13in 2017. On the Mac, the OS version stop at Ventura 13.6.6 and the installed XCode require Sonoma 14++ to install. But on the doc, this is written that works with macOS Ventura 13.5 or later : https://developer.apple.com/documentation/xcode-release-notes/xcode-15-release-notes Best regards.

I have a question for fellow developers from non-English speaking countries who had successfully submitted the DSA form as traders on App Store Connect specifying a PO box as address. I've read somewhere (likely on Mastodon) that Apple requires the PO box documentation to be "officially" translated in English to accept it. I am 100% positive this is not something I would be able to get from Italian Posts, because the contract will only be in Italian. How did you handle this? Were you able to submit the PO box documentation in your own language?

Hello, Trying to upload build to AppStore but reciving ITMS-90809: Deprecated API Usage. We have tried all possible solutions i think. Searching some help and advice here. All help is appreciated. cmd + shift + f) to find if UIWebView command grep -r "UIWebView". Searched out in the code. There is no web view WKwebview is used in every file ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).