I am using v1/apps/{appid}/appPricePoints to get app pricepoints. Few days ago i noticed that calling v1/apps/{appid}/appPricePointsfilter[territory]=USA&limit=200 i get four pages but last page just reaches only 400$ pricepoint. As i can see also on App Store connect Then i have to click additional prices Please help what am i missing ?

Does anyone know if App Store Connect (or any subset of Apple's toolsuite) has publicly available SOC 2 report? Or if there's a relevant email we can request that from. I tried security-certifications emails and got no response so it seems decently hard to find (didn't see on any searches/with aid of GPT). Thanks!

有効期限が2026年10月10日のApple Push Servicesに記載されている証明書について、その内容を確認すると、以下の出力が表示されます。 notBefore=2022 年 7 月 14 日 10:XX:XX GMT notAfter=2023 年 8 月 13 日 10:XX:XX GMT このため、Firebase は証明書の有効期限が切れていると認識し、アップロードを許可しません。 この問題の既知のバグや回避策があれば教えていただけますか?

After contacting Apple Support regarding MDM support for my Apple Developer Account, I received a link for my MDM request. The form in the link however requests for my Apple ID which seems to only be possible if I have an App on the AppStore. Considering I am only building an MDM Server I can not provide an Apple ID for this purpose. I have tried explaining this to the AppleSupport contact but I'm not getting any real result. I would appreciate any suggestions or support from this forum. I specifically require access to the MDM Vendor CSR Signing Certificate so that I can generate the APNs MDM Push Certificate needed for our MDM server to communicate with Apple devices.

Applied to the developer program with the waiver for a non-profit that I'm associated with. Application process was initiated on July 4th 2025 and have followed up multiple times since to get an update or clarity on timelines. We have a DUNS number. We are a registered NON PROFIT in INDIA and have the relevant documentation as required by them. We have submitted all of these documents at least twice for review but there's no update from Apple's end. Anyone have any recourse for escalation?

I've got a weird issue where Passkey fails, but only on developer.apple.com. Here's how it manifests: On portal, select "Sign In With Passkey" Get prompted with TouchId (on my MacBook) Portal says "can't verify your account" However: Sign in with Password works fine Sign in with Passkey on any other website works fine Not sure if it's related, but this appears to have happened around the time I had my logic board replaced. I did have weird issues with my iCloud account where I had to sign out of all devices, then sign back in. I assume this has to do with the hardware having the same serial number, but somehow appeared like a different computer in other ways. Things I've tried: In Passwords app, searching for "apple.com", I only see passwords, no passkeys. However, Safari password auto-fill always suggests the passkey entry first. developer.apple.com does not appear to have any way of managing sign-in credentials accounts.apple.com does not appear to be any way to manage passkeys. Sign in with Passkey on iPhone also results in "can't verify your account". Called AppleCare support, they were unable to help. Since Passkeys work for other websites, they believe this is a problem specifically with developer.apple.com. They suggested calling Developer support. Called Developer support, they were unable to help. They said AppleCare Support is best suited. Filled out Feedback (FB18185623) System: macOS 15.6 Safari 18.6 Has anyone else encountered anything weird like this? Is there any way to fix this? It would be nice if I could just delete the old passkey and create a new one. But I can't find any tool that will let me do that.

Hello, I’ve attempted multiple times to enroll in the Apple Developer Program, but the enrollment consistently fails. Despite reaching out to Apple Support through several emails, I have never received a clear explanation or log details on why the enrollment was not successful. I even requested that my client (with a foreign account) attempt the payment on my behalf, yet the application was still rejected. This suggests the issue is not simply related to payment method or regional restrictions. At this point, I would appreciate clear feedback or error details explaining why the enrollment fails so I can resolve the issue. For reference, here is the Purchase ID issued to me during the attempted enrollment: DWHQ8WFZJH I kindly ask Apple Support or community members with similar experience to assist in resolving this matter.

I am writing to bring to your attention a critical issue we are encountering while implementing Apple V2 webhook notifications on our platform. We are currently unable to authorize the token due to signature verification issues. We are unclear about the expected signature and how to validate it correctly. Additionally, we observed that the kid (Key ID), which was available in the header in Apple Pay V1 and used to retrieve the public key, is no longer present in the V2 webhook headers. We have already reviewed the official documentation here: Apple Server Notifications V2, but it does not clarify how to handle the signature validation or proceed. We would appreciate any guidance or documentation that could help us complete this integration successfully. Thank you for your support

I can log in but not renew dev programm payment: Sorry, you can’t enroll at this time. Your Apple Account is already associated with the Account Holder of a membership. In trader contact i see a wrong DUNS Number but i enabled no chance to edit. When i try to get a support call, error message wrong email. But in account is the right one confirmed. Thanks for helping, how can i enroll to the dev programm and publish my new App? Android is now approved and i stuck with IOS here.

Hi, I'm new to apple, I'm planning to deploy an app in the apple app Store... for this process to be done I've created apple developer account through an iPhone, when following the steps.. it asked to enter DUNS number as I'm business not individual, I've entered it but shown a DUNS number mis match notice when submit, so I tapped back and selected individual and accepted terms and conditions(just to check if it is working), now it was fixed for individual account(can't change), but I need organisation registration, please help me out somebody. There will be pooja goods sales in the app, so the individual account is sufficient or should be as organisation?

Hello, I’m experiencing an issue in the Apple Developer portal when trying to manage my App ID capabilities. Whenever I try to enable or disable a capability and click Save, the page shows the loading spinner but then nothing is saved. App ID: com.kangarli.lucary Team ID: (my Apple Developer account’s Team ID) Tested on different browsers (Safari, Chrome), cleared cache and cookies The issue affects all capabilities, not just Associated Domains Other sections of the Developer portal work normally Is this a known issue with the Developer portal, or is there any workaround? Thanks in advance.

I have made a payment the the Apple developer program from my credit card, I have contacted my bank and they have confirmed that they payment has gone off and all that is left is for Apple to 'bank the payment' on their side but Apple isn't actioning this. I have emailed support numerous times but all I get is an automatic reply acknowledging the email but nothing else, what do I do now, is there any other email or phone number I can contact them on. I'm not from the US

Hello, I am trying to call the StoreKit In-App API, but I am consistently receiving a 401 Unauthenticated error. Here is what I have done so far: JWT creation (via https://jwt.io): Header: { "alg": "ES256", "kid": "**********", "typ": "JWT" } Payload: { "iss": "********-e662-43d2-be42-012d0138ce39", "aud": "appstoreconnect-v1", "iat": 1757389187, "exp": 1757390987 } Private Key (.p8): -----BEGIN PRIVATE KEY----- -----END PRIVATE KEY----- Algorithm used: ES256 This generates the JWT successfully. API Call: I then include the JWT in the request header as follows: Authorization: Bearer ************ Endpoint: https://api.storekit-sandbox.itunes.apple.com/inApps/v1/transactions/2000001003740262 Response: Status: 401 Unauthenticated Request ID: S3KCYHDVRMDKUT3TZVTY3QRRWM.0.0 Has anyone else faced this issue? Is there something incorrect with how I’m generating the JWT (e.g., iat/exp values, formatting, or encoding)? Do I need to generate separate keys for Sandbox and Production, or is the same key valid for both? Any guidance would be appreciated. Thanks in advance!

I am building my first app. I submitted 1.0 to the App Store, it was rejected and I needed to make some changes. Am I unable to upload a new build with changes to testflight before I resubmit those changes? Also, I accidentally removed the app for review, so I cannot respond to the changes they asked. What do I do now? Thank you for your help

Hey, I am trying to implement the apple pay process pay backend service, I have checked everything and somehow it fails. I only have 1 certificate for merchant and 1 for the apple pay process, I have the private keys and try to run this following code that fails - import crypto from 'crypto'; import fs from 'fs'; import forge from 'node-forge'; const MERCHANT_ID_FIELD_OID = '1.2.840.113635.100.6.32'; function decryptedToken() { const token = ""; const ephemeralPublicKey = ""; const encryptedData = ""; //=================================== // Import certs //=================================== const epk = Buffer.from(ephemeralPublicKey, 'base64'); const merchantCert = fs.readFileSync('merchant_full.pem', 'utf8') const paymentProcessorCert = fs.readFileSync("apple_pay_private.pem"); //=================================== let symmetricKey = ''; try { symmetricKey = restoreSymmetricKey(epk, merchantCert, paymentProcessorCert); } catch (err) { throw new Error(`Restore symmetric key failed: ${err.message}`); } try { //----------------------------------- // Use the symmetric key to decrypt the value of the data key //----------------------------------- const decrypted = JSON.parse(decryptCiphertextFunc(symmetricKey, encryptedData)); console.log("Decrypted Token:", decrypted); // const preppedToken = prepTabaPayToken(token, decrypted) //~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // Send decrypted token back to frontend //~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // res.send(preppedToken); } catch (err) { throw new Error(`Decrypt cipher data failed: ${err.message}`); } } // extractMerchantID - const extractMerchantID = (merchantCert) => { //=================================== // Extract merchant identification from public key certificate //=================================== try { const info = forge.pki.certificateFromPem(merchantCert); const result = info['extensions'].filter(d => d.id === MERCHANT_ID_FIELD_OID); //----------------------------------- // Return //----------------------------------- return result[0].value.toString().substring(2); } catch (err) { throw new Error(Unable to extract merchant ID from certificate: ${err}); } } // generateSharedSecret - const generateSharedSecret = (merchantPrivateKey, ephemeralPublicKey) => { //=================================== // Use private key from payment processing certificate and the ephemeral public key to generate // the shared secret using Elliptic Curve Diffie*Hellman (ECDH) //=================================== const privateKey = crypto.createPrivateKey({ key: merchantPrivateKey, format: "pem", type: "sec1", // because it's "EC PRIVATE KEY" }); const publicKey = crypto.createPublicKey({ key: ephemeralPublicKey, format: 'der', type: 'spki' }); //----------------------------------- // Return //----------------------------------- return crypto.diffieHellman({privateKey,publicKey: publicKey,}); //----------------------------------- } // getSymmetricKey - const getSymmetricKey = (merchantId, sharedSecret) => { //=================================== // Get KDF_Info as defined from Apple Pay documentation //=================================== const KDF_ALGORITHM = '\x0didaes256GCM'; const KDF_PARTY_V = Buffer.from(merchantId, 'hex').toString('binary'); const KDF_PARTY_U = 'Apple'; const KDF_INFO = KDF_ALGORITHM + KDF_PARTY_U + KDF_PARTY_V; //----------------------------------- // Create hash //----------------------------------- const hash = crypto.createHash('sha256'); hash.update(Buffer.from('000000', 'hex')); hash.update(Buffer.from('01', 'hex')); hash.update(Buffer.from(sharedSecret, 'hex')); hash.update(KDF_INFO, 'binary'); //----------------------------------- // Return //----------------------------------- return hash.digest('hex'); //----------------------------------- } // restoreSymmetricKey - const restoreSymmetricKey = (ephemeralPublicKey, merchantCert, paymentProcessorCert) => { //=================================== // 3.a Use the payment processor private key and the ephemeral public key, to generate the shared secret //=================================== const sharedSecret = generateSharedSecret(paymentProcessorCert, ephemeralPublicKey); //----------------------------------- // 3.b Use the merchant identifier of the public key certificate and the shared secret, to derive the symmetric key //----------------------------------- const merchantId = extractMerchantID(merchantCert); //~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // Return //~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ console.log("Merchant ID:", merchantId); console.log("Shared Secret (hex):", sharedSecret); return getSymmetricKey(merchantId, sharedSecret); //~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ } // decryptCiphertextFunc - const decryptCiphertextFunc = (symmetricKey, encryptedData) => { console.log("🔑 Decrypting Ciphertext with Symmetric Key:", symmetricKey); //=================================== // Get symmetric key and initialization vector //=================================== const buf = Buffer.from(encryptedData, 'base64'); const SYMMETRIC_KEY = Buffer.from(symmetricKey, 'hex'); const IV = Buffer.from([0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]); // Initialization vector of 16 null bytes const CIPHERTEXT = buf.slice(0, -16); //----------------------------------- // Create and return a Decipher object that uses the given algorithm and password (key) //----------------------------------- const decipher = crypto.createDecipheriv("aes-256-gcm", SYMMETRIC_KEY, IV); const tag = buf.slice(-16, buf.length); decipher.setAuthTag(tag); //~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // Load encrypted token into Decipher object //~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ let decrypted = decipher.update(CIPHERTEXT); console.log("🔑 Decrypted Data"); decrypted += decipher.final(); //::::::::::::::::::::::::::::::::::: // Return //::::::::::::::::::::::::::::::::::: return decrypted; //::::::::::::::::::::::::::::::::::: } decryptedToken();

I'm getting an error after clicking on a TestFlight Beta version invite from email. The error says The Apple Account you're currently signed in with, ****@outlook.com, doesn't match the one associated to this invitation. The invitation was sent to the email that I use to sign into my Apple account (it is my apple id) and I am signed into my iphone with that account. What can I do to get the invite to match up and go through with TestFlight?

I started the Apple Developer Program enrollment for my organization about 2 months ago. I received an email stating that Apple needed documentation, which they mentioned in an email titled “Request for Enrollment Documents” last week. However, I never received this email with the actual document request. I have written several times through the online platform in our account asking Apple to resend this email, but I have not received any reply for over a month. Instead, every Thursday I only receive the same automated email reminding me to upload the documents. I even called Apple Business Support, but they told me they could not help because the Apple Developer team is separate. How can I reach the correct team to resolve this issue?

Hi, I need help resolving an enrollment issue. When I log into my Apple Developer account on the website, I only see the message: “You’ve already agreed to the Apple Developer Agreement.” After that, nothing else loads and I can’t continue. What I’ve tried: Paid the annual fee (it shows as charged). Logged in from iPhone (Developer app), Mac, Safari, and Chrome. Same error. Cleared cookies, tried private mode, and even changed my email. Contacted normal Apple Support (they couldn’t help). Tried to reach Developer Support but I can’t since I’m technically not enrolled. Other details: I can’t access App Store Connect. My Apple ID birthday is set to 15 October 2000. I’ve already accepted the Developer Agreement. Developer app shows an error whenever I try enrollment there. At this point, I’m stuck in a loop: Apple says I’ve already agreed, but my membership isn’t activated, and I can’t contact the right support channel.

Hi Forum, I am currently facing an issue with the Apple Developer enrollment process. My legal entity, Medinertia Technologies Pvt Ltd, is registered in India, and I have obtained a valid D-U-N-S number for it. I also purchased the domain medinertia.co.in and created a business email (support @medinertia.co.in). However, this email is still not being accepted during enrollment. Could you please clarify what domain extensions or email formats are supported for business verification? Without clear guidelines on acceptable domain names and email IDs, it becomes difficult and costly to keep purchasing multiple domains. Your guidance on the correct domain/email requirements will be greatly appreciated. Best regards, Uday

Hi Forum members, I am currently facing an issue with the Apple Developer enrollment process. My legal entity, Medinertia Technologies Pvt Ltd, is registered in India, and I have obtained a valid D-U-N-S number for it. I also purchased the domain medinertia.co.in and created a business email (support @medinertia.co.in). However, this email is still not being accepted during enrollment. Could you please clarify what domain extensions or email formats are supported for business verification? Without clear guidelines on acceptable domain names and email IDs, it becomes difficult and costly to keep purchasing multiple domains. Your guidance on the correct domain/email requirements will be greatly appreciated. Best regards, Uday