We use store kit original API for in-app purchase,I set a UUID to the SKMutablePayment object applicationUsername property, when finish the payment, In the App Store Server API, the JWSTransactionDecodedPayload object returns no appAccountToken field.This probability is extremely small, about 17 in 100,000.Does anyone have the same situation?

We have an iOS app which is currently available in AppStore. Now we are enabling Mac Catalyst support for the Mac users. As our app is contains In App purchases and it is working fine in iOS devices. But when we try to purchase subscriptions from Mac Catalyst app using TestFlight, it gives the error “Your account is not valid for use in the U.S. store. You must switch to the Japan store before purchasing.” Then after we have checked an AppStore region and the region is already Japan. Any assistance would be appreciated.

The page you’re looking for can’t be found. The page you’re looking for does not exist, or you do not have permission to view it. I have Admin role but whenever I select the tab "Xcode Cloud" on any app, the page is not loaded.

Being a software company we create and distribute an iOS SDK with our customers world wide. The distribution of the software is in the form of a static library / XCFramework to our customers. They will integrate the SDK and use it to collect data from their hosting as first party. As Apple enforced through this article “Describing use of required reason API” - “starting from Fall 2023 you’ll receive an email from Apple if you upload an app to App Store Connect that uses required reason API without describing the reason in its privacy manifest file”. We are using "NSUserDefaults” in our SDK which is one among the required API listed, and as of now we didn’t create a Privacy manifest file and declared this on the SDK. We tried uploading our app to the Appstore connect portal, as we are not complying with the requirement from Apple we expect to see the warning message. Currently we are unknown about the impact of not having the Privacy manifest, and we would like to test the scenarios and make sure we are declaring the correct information on our SDK. Please could you review this and let us know why we are not receiving the emails. Or is that Apple didn’t harden the uploads yet and something planned for future date?

Hi everyone, We're fighting an issue that's driving us up the wall. We developed an Apple Watch Only standalone app, which cost $2.99; once you paid, you could download and use the app on your Apple Watch. We've released a companion iOS app for iPhone that goes into the same bundle (as it's the same app, now supporting two platforms). Nevertheless, the Watch app is still available as a separate app (you can download the Watch app only if you wish without needing to download the iPhone app as well). The iOS companion reads information from the watch and provides more insights into the data it displays. Similar to the sleep tracking apps where you use the watch to sleep and track and the iPhone to see the results. When we released the latest version, including both, we changed the price to Free in all countries. After this, we now have a huge problem we haven't been able to solve: Our existing users (who paid for the Apple Watch-only app) cannot download the companion iOS app. If they go to the App Store, it'd just say "Purchased" with no option to download it (nor the "Get" button or the "Cloud" icon). If you go to your App Store account in your iPhone and then to "Purchases," the app won't appear there. Because technically, you never bought it, and it's now free. If you do the same on your Apple Watch, you can still see the app on your purchases, but that would only download the Apple Watch app, not both. But on top of that, I want my users to be able to download the companion app from the App Store with their iPhones because that's what they'll do anyway (only 9% of our app downloads happen straight in an Apple Watch; most come from iPhones). Did anyone have this problem? I'm already talking with support because this is having a very negative impact on our app, and it all looks to be a bug on the App Store or an edge case that Apple hasn't considered. The thing is, I experienced this issue myself with an app from another dev previously where I had the Apple Watch app installed and paid for it. When I wanted to download the companion they released, it was impossible for the same reasons stated above. He managed to fix it, but I couldn't find any information.

When trying to refresh a sandbox receipt of my macOS app by using exit(173), storekitd on macOS Sonoma 14.1 logs the following (German) error: fehler 18:32:58.421785+0100 storekitagent com.(redacted): Failed to renew receipt for exit(173): Error Domain=AMSErrorDomain Code=100 "Authentication Failed" UserInfo={NSMultipleUnderlyingErrorsKey=(``` "Error Domain=AMSErrorDomain Code=2 \"Ein unbekannter Fehler ist aufgetreten. Versuche es erneut.\" UserInfo={NSLocalizedDescription=Ein unbekannter Fehler ist aufgetreten. Versuche es erneut.}", "Error Domain=NSURLErrorDomain Code=-1202 \"Das Zertifikat f\U00fcr diesen Server ist ung\U00fcltig. Eventuell wird eine Verbindung mit einem Server hergestellt, der vorgibt, \U201eauth-sandbox.itunes.apple.com\U201c zu sein und vertrauliche Daten gef\U00e4hrdet.\" UserInfo={NSLocalizedRecoverySuggestion=Soll die Verbindung zum Server trotzdem hergestellt werden?, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9843, NSErrorPeerCertificateChainKey=(\n \"<cert(0x14f033000) s: daiquiri-ext.itunes.apple.com i: Apple Public EV Server RSA CA 2 - G1>\",\n \"<cert(0x14f01d000) s: Apple Public EV Server RSA CA 2 - G1 i: DigiCert High Assurance EV Root CA>\",\n`` The error translates to: The certificate for this server is invalid. A connection may be established with a server pretending to be "auth-sandbox.itunes.apple.com" and compromising confidential data. The certificate returned by the sandbox auth server seems to be for daiquiri-ext.itunes.apple.com and not valid for auth-sandbox.itunes.apple.com. When I try to enter https://auth-sandbox.itunes.apple.com in Safari, it tells me that it cannot establish a secure connection to the server. curl -v https://auth-sandbox.itunes.apple.com logs this: * Connected to auth-sandbox.itunes.apple.com (17.36.202.9) port 443 (#0) * ALPN: offers h2,http/1.1 * (304) (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/cert.pem * CApath: none * (304) (IN), TLS handshake, Server hello (2): * (304) (IN), TLS handshake, Unknown (8): * (304) (IN), TLS handshake, Certificate (11): * (304) (IN), TLS handshake, CERT verify (15): * (304) (IN), TLS handshake, Finished (20): * (304) (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384 * ALPN: server accepted h2 * Server certificate: * subject: businessCategory=Private Organization; jurisdictionCountryName=US; jurisdictionStateOrProvinceName=California; serialNumber=C0806592; C=US; ST=California; L=Cupertino; O=Apple Inc.; CN=daiquiri-ext.itunes.apple.com * start date: Aug 28 18:07:16 2023 GMT * expire date: Dec 30 18:17:16 2023 GMT * subjectAltName does not match auth-sandbox.itunes.apple.com * SSL: no alternative certificate subject name matches target host name 'auth-sandbox.itunes.apple.com' * Closing connection 0 curl: (60) SSL: no alternative certificate subject name matches target host name 'auth-sandbox.itunes.apple.com'

Why does App Store Connect mess up the order of uploaded screenshots?

Since updating to 14.2 beta 2 I see the following error when trying to sign in to the TestFlight App on macOS. "Password reuse not available for account" It seems like it possibly affecting the AppStore too, from the device logs I see: Error Domain=AMSErrorDomain Code=2 \"Password reuse not available for account\" UserInfo={NSLocalizedDescription=Password reuse not available for account, NSLocalizedFailureReason=The account state does not support password reuse.}" I've tried signing out of the App Store to fix it but now I can't sign into either the store of TestFlight. I've also tried, multiple restarts and safe mode. Things seem fine on other platforms. Is this a known issue? Are others seeing it? Any ideas for how to reset things or what the error might be referring to?

I can't upload a build via Xcode Organizer on Sonoma with Xcode 15.0.1. When I try to upload the build to App Store Connect via Xcode Organizer I get an error message: "App Store Connect access for ... is required. Add an account in Accounts settings." + "No App Store Connect access for the team". For info, I use my Apple ID as admin. I've tried several reboots (device and Xcode), in addition to many sign in/out from the account manager. All my certificates are created. No success. But I've found a strange issue with the WDRC (Apple Worldwide Developer Relations Certification Authority) certificate that may explain this error message (probably generic). I've create a dummy iOS project, and every time Xcode is managing the signing process (Automatic), an expired WDRC certificate is generated in Keychain. I can delete the certificate (Certificate Tab) but Xcode keep generating the file every time I open the project. The certificate sits next to the valid WDRC certificate. I've cleared all the provision profiles, and those in App Store Connect but Xcode keeps creating this expired certificate. I guess it's related to the "App Store Connect access" issue. I have several apps on the App Store, this is the first time I get blocked with such issue. I need help.

Like the title says. Can you submit an app update and release it while the app is in pre-order? I would assume that yes it is possible but I've never used pre-orders so I'd like to know if anyone here knows... Thanks!

A couple of months ago I released an app made with react-native expo in the app store. In the app i use a library called expo-store-review, which uses the SKStoreReviewController from swift. The in app review modal shows up as expected, but when users leave a review, I don't receive it. I've tested it with multiple friends and family, standing next to them while they where leaving the review, and everything on their end went correct and no errors show up. It looks like the only reviews I do receive is when users also leave a text with the review or do it in the appstore directly. I've tried using a different library for the in app review, but that also didn't fix the problem. Has anyone had a similar issue and if so, knows how to fix it?

Payment completed with error:Error Domain=ASDServerErrorDomain Code=3539，UserInfo={storefront-country-code=CHN,client-environment-type=Sanbox,AMSServerErrorCode=3539,NSLocalizedDescription=No information about in-app purchases is provided. Please try again later}

I use String Catalog to localize my app (built in English) to Japanese. The app works fine and supports both languages. I have tested on TestFlight, and the live version download from App Store also supports 2 languages. But the display on App Store only indicates Japanese. I have no idea why the number for localized files show 0 for both English and Japanese. The Localization of Japanese works fine. How to fix this?

Hello. I have an app in the app store that I have localized into several languages. But the list of languages that the app supports in the App Store lacks English, which is the main language (and the language I developed the app in). I'm localizing the text by using String with a "localized" key and a defaultValue (in English). I also created a localization string catalog where I added added the values for each key on each language. On Xcode (15.0.1), in the app file, info, localization section I see that all languages are there with green checkmarks, except English which is at the top and is the default language. However, when I build, archive and send the bundle to AppStoreConnect, the Localizations in the Store Information section for the bundle does not include English, and so on the AppStore it looks like the app supports all of the additional languages but it does not list English. I can't figure out exactly what I'm missing. Can anyone help?

I can't create a new application. An error has occurred. Try again later app

My In-App purchases are actually JSON files which provide metadata for my app. I am required to provide a "screenshot" for each of these IAPs before they can be accepted. What is the common practice for screenshots when it is just a JSON file of structured data to be used within the app. Surely someone else has run into this issue by now. What are we supposed to do?

Let's say I have an app version of 1.1.0 that currently supports from iOS 14.0 and above, and now I'm planning to release an app version of 1.2.0 but I'm dropping the support for iOS 14.0 (meaning that the app v1.2.0 will only support iOS 15.0 and above). Now let's say there's an issue happening in the app v1.1.0 but only affecting iOS 14 users and I somehow need to release a hotfix release. My question, is it possible to release an update of v1.1.1 but only targeted towards iOS 14 users while keeping the v1.2.0 for iOS 15 users and above? If it is possible, how can I do that? Or if it's not possible, what kind of approach can I do to mitigate this kind of issue?

I manage apps for multiple clients , it seems that since updating to Xcode 15 I'm no longer able to upload updates to them. I have valid certificates and provisioning profiles associated with the apps in Xcode but whenever I attempt to upload the app I get the following errors: No Account for Team "xxxxxxxxx". Add a new account in Accounts settings or verify that your accounts have valid credentials. No profiles for '***.xxxxxxx.xxxx' were found Xcode couldn't find any iOS App Store provisioning profiles matching '***.xxxxxxx.***'. I have valid users on each of the affected dev accounts and am specified as an admin. This just started happening in the last 2 weeks.

Our 13 engineers spent 197 days developing a live broadcast application, and we were very happy on August 23 because it was completed. Then came the indifferent bad news. The first time we submitted the app it was rejected. We noticed your app shares a similar binary, metadata, and/or concept as apps previously submitted by a terminated Apple Developer Program account. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts Learn more about our requirements to prevent spam in App Store Review Guideline 4.3. We accepted some suggestions, modified some codes, and made a second submission, and then unfortunately, we were told that 4.3 appeared. I am here to ask for help. Is there any other method that can help me prove that this code was developed by us and was not purchased or used by others. For example, if we apply for a "USPTO", will it be helpful for the review? We have modified it. There is a lot of code, and if we modify it again, there will be many bugs, which we cannot accept.

Hello, I have been trying for several days to create an app in App Store Connect, but I keep encountering the error 'An error occurred. Please try again later,' and I am unable to create any app. My license expires in February 2024.