I’m experiencing a critical issue with my app’s review process under my developer account (App ID: 6744330283). The app was initially approved and published, but starting with version 1.2 and later updates, every submission faces prolonged review times (over 1 week) only to be automatically rejected without clear justification. I’ve resubmitted multiple times, confirmed compliance with guidelines, and even tested with minor changes—same result. Meanwhile, a separate developer account of mine gets approvals within 24 hours for the same type of apps, suggesting an account-specific issue. Actions Taken: Appealed via the Resolution Center and App Review Board. Communicated via email and even a Meet call with Apple Support, but was told my account has "no issues." The app has real users and active IAPs, making this disruption unacceptable. Next Steps: I’m pursuing legal counsel in LA to escalate this, as the lack of transparency is harming my business. Questions for the community: Has anyone resolved a similar issue? Are there hidden account flags or escalation paths beyond standard channels? Any advice or shared experiences would be greatly appreciated.

Dear App Review Team, We are raising serious concerns regarding the ongoing review process for the app (App ID: 6737148404), which has once again been escalated to the App Review Board—just days after the previous issue was finally resolved. We submitted a new build on June 18 containing a standard feature update. The app entered "In Review" promptly, but after 3 days with no communication, it has now been escalated to the board again, likely. This pattern is deeply troubling. What’s particularly alarming is that it appears the current reviewer lacks the necessary context or understanding of the app, and instead of engaging with us or taking ownership of the review, they’ve defaulted to escalating it without providing any rationale or feedback. This repeated hand-off to the board without accountability or explanation is effectively grinding our release process to a halt. Based on past experience, we suspect we are now waiting for another board meeting early next week—which means yet another week lost to silence and uncertainty. This is not a scalable or sustainable process. This is one of the top performing apps on visionOS, and yet every iteration—regardless of how minor—is delayed by escalations and inaction. These delays are damaging to our business, destabilizing to our user experience, and increasingly eroding our trust in the App Review process. We urgently request: Immediate clarity on the current review status A direct line of communication with someone accountable for the review An explanation as to why nearly every update requires board involvement We’ve complied fully with all App Store guidelines. All standard support channels have already been exhausted without resolution. This cycle must change. We are ready and willing to work collaboratively, but we need responsiveness and consistency from Apple in return. App ID: 6737148404

Hey All! I keep receiving an email from Apple stating "You have a missing purpose string in your Info.plist" for the key "NSLocationAlwaysAndWhenInUseUsageDescription". The thing is, though, that we are setting that value within our build Info.plist. The data in that value is even reflected into the application after build, with the correct purpose string showing up when requesting location services. We currently do our builds via Azure Devops CI/CD, where we use xcodebuild for this process. The archive also generates an Info.plist without the location key, so I tried manually inserting it before deployment. Also no luck. Anyone else had this issue or know how to resolve it? Snippet to show how the location key is currently set during build: <?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>NSLocationWhenInUseUsageDescription</key> <string>Application uses location data for accurate maps display</string> </dict> </plist> Thanks!

I am just developing an app,I just config the In App Purchase module in App Store Connect.And I have deployed the related code in flutter, and the Xcode have done the configuration about this. The fetching products is successful, and buyNonconsumable/buyConsumble api could be called successfully ,but whatever install methods I have tried, could not receive the receipt after call the buyNonconsumable/buyConsumbl api.So could you help to solve this problem,I just have stucked for a few weeks , please help. Btw ,my friends have told me that if I want to integrated the In App Purchase function,I need to upload a version to apple store and make it pass the review process.Please help me to confirm these question ,very thankful.

Dear App Store Review Team, I am writing to express my concern regarding the lack of response concerning the review of my application, which has been under review since June 2nd with no updates or further communication. This delay is negatively impacting my business negotiations, as my clients already have access to the Android version and are now waiting for the iOS version. My professional credibility is being affected, as I cannot provide them with a clear response or estimated availability date. I have made a significant investment in developing this iPhone version, purchasing the required hardware, licenses, and tools, trusting that I would receive professional and fair treatment from Apple. I kindly request an update on the status of the review and a prompt resolution, as this situation is causing me considerable harm. Sincerely,

Hi everyone, I’m relatively new to the App Store and currently facing a frustrating review situation. I’d appreciate any advice or insight. Here’s the timeline: June 6: I submitted version 1.0 of my app. It was approved the same day. June 10: I submitted version 1.1 with a few important bug fixes. The app quickly moved from “Waiting for Review” to “In Review”, and stayed in that status for 6 full days, with no activity or feedback. I submitted an expedited review request and contacted support. They replied that the review “started on June 12,” although App Store Connect shows In Review since June 10. Based on advice from other developers, I assumed the app was stuck due to a rare issue. So, on June 16, I removed the submission and resubmitted the exact same version 1.1 — hoping this would reset the process. Unfortunately, the app then stayed in “Waiting for Review” for more than 48 hours. I wasn’t planning to cancel again, but I discovered a critical gameplay bug that had to be fixed. On June 18, I submitted a new build as version 1.2. It’s currently in “Waiting for Review”. ❓My questions: Is there anything I might be doing wrong that’s causing these delays? Could I be missing some required metadata or review notes? Or is this normal behavior for new developer accounts? I’d really appreciate any guidance — I just want to ensure I’m not overlooking something important. Thanks in advance! App ID: 6746811958

How would one interpret guideline 5.4 VPN? It states: "Apps offering VPN services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy" Does that mean you cannot integrate Ad SDKs inside apps offering VPN functionality? Or does this only apply VPN Traffic? So using third party Ad SDKs like Admob is fine, as long you don't share any VPN traffic data? (e.g. Admob runs inside the App Process/UI, but doesn't run inside NEPacketTunnel) We have a similar case (and couldn't get clarification from App Review so far)

Hi everyone, I'm stuck in Apple's account migration process and could use some advice from those who've been through this. My situation: Submitted individual → organization migration request Got initial response from Apple on June 15 (case #102620626191) Confirmed to proceed immediately Radio silence for 4+ days since then Key details: No existing apps or certificates to preserve Have a finished app ready to publish under business name ASAP Already have D-U-N-S number and LLC setup My question: Should I start a fresh organization account application in parallel, or will that cause conflicts since it's the same LLC/D-U-N-S number? Has anyone been in a similar situation? Did creating a new org account end up being faster than waiting for the migration to complete? Any insights on typical timelines for both processes would be greatly appreciated! Thanks!

Hi, We currently have an app in the app store for about 10 years now. It can show aviation instrument panels. Technically, each instrument is a folder that holds assets like PNG's etc, and a lua script. Since this is a script, I understand that apple needs to verify it before it can enter the app store. That is why we have always packaged all instruments with the app. We already have an online server that hosts these instruments, used on Android and Desktop. My first question is, is there a way could still use our own server, and let apple verify them another way? Regards Corjan

Hi there, Recently, a change was made to the App Store Connect API, which removed the unofficially supported templateName parameter when creating provisioning profiles. This broke fastlane as it was using the templateName parameter. Could that change be reverted or official support added for templateName? I believe this change was first rolled out around March 18th and then reverted shortly after, before being rolled out again around May 6th. The fastlane issue can be seen here: https://github.com/fastlane/fastlane/issues/29498 Official AppStoreConnect API docs for the endpoint are here: https://developer.apple.com/documentation/appstoreconnectapi/profilecreaterequest/data-data.dictionary/attributes-data.dictionary

Dear Apple Review, I submitted my app for review on June 11th, and it has remained in “Waiting for Review” status for the past 8 days without any updates or communication. As this is my first app submission, I was expecting the review process to follow the usual 24–48 hour timeframe, as publicly stated. I’ve noticed that other apps are being reviewed and even updated multiple times in the meantime, which makes this prolonged delay particularly concerning. I would greatly appreciate it if you could look into the status of my submission and provide any updates or guidance regarding the next steps. Thank you for your time and support. Best regards,

We are preparing to submit a new app that shares some functionality and with an app we have previously distributed on the App Store. The Codebase will be different (the existing one was developped using React JS and the Second one usinf SWIFT). While the new app includes updated features, a redesigned interface, and is intended for a different user audience, we would like to confirm in advance whether submitting it as a separate app (with a new Bundle ID) is acceptable under current App Store Review Guidelines. In particular, we would appreciate clarification regarding Guideline 4.3 (Spam), to ensure that the submission will not be considered a duplicate or unnecessarily repetitive version of our existing app. Could you please advise on this matter?

Since I donwloaded Testflight, an error message appears indicating that "Testflight is temporarily unavailable. Try again." And some of my colleagues encounter the same problem. Do you know what the issue can be?

Hello Apple Support Team, We are developing a macOS application that allows users to import and view PST files (Microsoft Outlook archives). These files contain a complex, proprietary format that requires specialized parsing libraries. To achieve this, we are using Aspose Email for Java, which is currently one of the few reliable libraries that support complete PST parsing across platforms. Why we are using Java & Aspose The Aspose Email Java library provides a comprehensive API to extract mail data (including metadata, attachments, and folder structure) from .pst files. A native Swift or Objective-C alternative with full .pst parsing capability does not exist, which is why we opted for a Java-based helper module that runs in the background and communicates with the macOS app over a Unix domain socket. How we bundle it We package the AsposeEmail.jar and a custom JRE (Java Runtime Environment) created using jlink, tailored to run only our jar. This entire setup (JAR + JRE) is bundled within the Contents/Resources directory of the macOS app, and we invoke the Java runtime using standard process launch APIs from Swift. Problem during App Store Submission When we archive the app and submit it to the App Store, the validation step raises an error: ITMS-90284: Invalid Code Signing - The executable 'com.app.sample.appstore.pkg/Payload/Sample.app/Contents/Resources/custom-jre-universal/lib/cli ent/libjsig.dylib' must be signed with the certificate that is contained in the provisioning profile. ITMS-90284: Invalid Code Signing - The executable 'com.app.aample.appstore.pkg/Payload/Sample.app/Contents/Resources/custom-jre-universal/lib/cli ent/libjvm.dylib' must be signed with the certificate that is contained in the provisioning profile. When we attempt to code sign the custom JRE, especially the .dylib files inside, the runtime breaks. Java is unable to launch correctly and throws permission errors and execution failures. Alternative we thought of (On-Demand Download) To avoid the code signing issue, we decided to remove the JRE from the bundle and instead download it on demand when the user performs an action like "Import PST". However, we realized this may violate the App Store Review Guideline 2.5.2: Our use case, while not dynamically modifying features, does download and execute a Java runtime, which could be interpreted as executing new code post-installation. How can we proceed? We are looking for Apple’s guidance on the correct and compliant path forward: Is there a recommended way to bundle and codesign a custom JRE so it is accepted by the App Store? Is on-demand download of a custom runtime for a very specific parsing task permitted, assuming it doesn't modify app features but simply supports user-initiated operations? We would greatly appreciate any guidance or best practices on how to handle this situation, particularly with respect to App Store compliance. Regards, Maaz Hussain

Hi, ASC API call rejects DEVELOPER_ID_APPLICATION_G2 and does not recognize it, even though it is listed as a valid certificateType in the docs: https://developer.apple.com/documentation/appstoreconnectapi/get-v1-certificates. If it was removed from the certificate list, then why Apple forces to choose the G2 type when creating a DEVELOPER_ID_APPLICATION certificate manually in the Apple Developer account. Can someone from Apple support please check it as it is a contradictory behavior and is a blocker.

I just started with App Clips so quite new to it. One of our dependencies is very big in size (85+ MB) which is making the app size almost 87MB's uncompressed and 40MB's compressed with just this dependency and no other app clip related code in it. I created a App Thinning size report for the app clip and even with bigger app clip size, I decided to upload the beta build to App Store Connect for testing purposes. On App Store Connect, app clip size is 70+ MB and to my surprise it passed the App Store Connect review and I was able to install this app clip on my device from Test Flight. If I add functionality to the app clip with this bigger dependency SDK, then the app clip size is going to increase further and am worried that it could get rejected when I push it to app store. Minimum iOS version of the app is 16.4, so my understanding is that the maximum app clip size allowed is 15MB. Am trying to figure out, how the app clip build was approved on app store connect and if dependency sizes in app clips are ignored? Attaching screenshot of App Thinning report and screenshot of App Store Connect build with this App Clip.

Hi everyone, We're working on a fitness and wellness app that offers subscription-based content like workout videos, nutrition plans, and personal coaching. We've read the updated documentation on the External Link Account Entitlement (ELAE), which allows certain apps to include a link to an external website for account management and payments. However, based on what Apple describes as eligible “reader apps” (video streaming, books, audio, etc.), it's unclear whether fitness apps can apply for and use this entitlement. Our questions: Can a fitness app use the External Link Account Entitlement to link out to a web-based subscription page? If not currently supported, is there any plan to expand this to other categories like health & fitness? We are fully compliant with App Store IAP rules today, but we're exploring all legitimate options as we aim to provide a smooth and transparent experience across platforms (iOS, Android, and web). Any insights from the community or Apple team would be appreciated! Thanks, Onur Hazar

I haven't much published new apps to AppStore for a period. But as I have built myself a MacOS app and have used it over a year, so I decided to hire professional designed that maybe there will be others that would like to use it as it was unique tool for professionals. But after a flustrating week with AppSTore Reviewers, seems that I'm paying each year for a service that has no value to anyone. AppStore Reviewrs never read or ignored my messages; Even I had uploded several corrected builds (and obviously changed that build in AppStore Connect, they have ignored it and are still testing the first version uploaded; Even I have provided the webpage, which decsribes app features and how to use those, they have never visited that page and as I later created Youtube video showing show I use it, that video was never playd. Complaining to App Review Board has no effect anymore. They just ignore complaints. At least during my last iOS app submissions, Reviewer constantly comlianed that "Like" button is unresponsive, even I have explained that you can't Like your own posts, especially before those are published. Then Revew Board intervened and I finally got my app published. But this situation now seems to be absurd? Why we are paying this "Developers Fee" to get insulted by Apple Corporation?

Hi everyone, I’m reaching out because I’m really struggling to understand what’s happening with my app’s review status. My app was successfully approved and published with: Version 1.0 on May 12, 2025 Then updated to 1.1 on May 18, 2025 Everything was going smoothly — users were engaging, and within the last 20 days alone, in-app purchases totaled $2,100. However, when I submitted a new summer update (with fresh features and an in-app event), both: Version 1.2 and Version 2.1 ...were rejected under guideline 4.3(A) – Spam. This is incredibly confusing because: My app has a completely original design and functionality It provides distinctive value and content There is real user activity and sales I tried everything — submitted explanations, requested a manual review, even scheduled a Webex meeting with Apple. But the meeting was vague, and I still haven't received any concrete details on what exactly violates 4.3(A). Everything just refers back to "not complying with Apple's guidelines" without specifying how. 🆘 App ID: 6744330283 Has anyone faced something similar? Does anyone have insight on how to move forward or how to escalate this issue for a proper manual review? Any advice or help would be greatly appreciated. Thanks in advance, Bao Duy

Hi, A few hours ago I enrolled myself in the Apple Developer Program and paid the yearly dues (995 SEK for Sweden). I enrolled via the Developer program on my Mac. When I visit the website (developer.apple.com) now I see an option to "To continue your enrollment, complete your purchase now" and it seems like it's asking me to pay again? I'm not sure if it's an issue of waiting or something went wrong during sign up. I've checked my bank and I have been charged already so I wonder if it's an issue of time/approval, how long would it take to finish enrollment? Thanks!