Hello everyone, I would really appreciate some advice regarding an App Review rejection under Guideline 1.2 because I’m unsure what the best next step is. The review notes included the following statement: “Since this app’s primary functionality is not permitted on the App Store, it would be appropriate to submit a new app with functionality that follows the App Review Guidelines. Resubmitting the app will result in the same or additional App Review Guideline violations.” This wording makes me unsure whether I should submit a new build with the changes I have made or continue discussing the issue through the Resolution Center. The app was rejected because App Review considered its primary purpose to be random or anonymous chat. However, I believe there may have been a misunderstanding about how the application actually works. The application is not a private messaging app, nor is it designed to let people freely chat with strangers. The concept is closer to a discussion that takes place on a user’s profile, similar to two people having a conversation in the comments section of a social media platform. Other authorized users can read those conversations and react to individual messages, so the conversation itself becomes the content rather than functioning as a traditional direct message. Users are never anonymous. Every account has a persistent identity, including a username, profile picture, verified email address, and profile information. The application also includes reporting, blocking, restricting, and moderation features. Communication is intentionally very limited. Users cannot simply message another user whenever they want. Even after all other requirements are met, a user can send only one initial message. The recipient then has 24 hours to decide whether to reply. If the recipient chooses not to reply, the conversation never begins, the thread is automatically moved to the archive after 24 hours, and the sender cannot continue contacting that user. They cannot send another initial message or repeatedly attempt to start a conversation. A conversation can only continue if the recipient voluntarily chooses to reply. Originally, every account was private by default, although users could choose to make their profile public. During App Review, I temporarily made the review accounts public because I wanted the reviewer to be able to explore the application more easily without needing multiple test accounts. Looking back, I now believe this may have unintentionally made the application appear much closer to a stranger chat experience than it was actually designed to be. Another detail that may not have been visible during review is that the reviewer reached the message composition screen but did not actually submit a message. (I saw it on screenshots they attached) If they had submitted it, they would have seen that the initial message does not immediately become an active conversation. Instead, it first enters a pending state where the recipient decides whether to accept it by replying. Without the recipient’s voluntary participation, no conversation is created. After receiving the rejection, I decided to redesign this part of the application to make the communication model even more restrictive. I completely removed the ability for users to have public profiles. Every account is now permanently private. Before any interaction is possible, a user must first send a follow request, and the recipient must explicitly accept that request. Without an accepted follow request, it is impossible to send the initial message. I also removed the discovery feature that could resemble random user discovery and replaced it with standard user recommendation cards similar to those used by many social networking applications. In addition, I implemented follow request rate limiting so users cannot rapidly send large numbers of follow requests. As a result, users can now interact only after mutual consent has already been established through an accepted follow request, and even then, communication is still limited to a single initial message that requires the recipient’s voluntary reply before any conversation can exist. My question is this: Given these changes, would you recommend submitting a new build for review despite the statement that “Resubmitting the app will result in the same or additional App Review Guideline violations,” or would it be better to continue discussing the issue through the Resolution Center first? (Some why they don't reply me at all) If anyone has dealt with a similar Guideline 1.2 situation, I would sincerely appreciate your advice on how you would proceed. Thank you very much for your time

How can Apple deny my appeal and not approve my app for tobacco when multiple apps like these are on the store?

Guideline 1.4.3 rejection for a cigar journal app — multiple apps with identical functionality are live on the App Store Hi all, My first submission (a cigar humidor/tasting journal app) was just rejected under Guideline 1.4.3 (Safety – Physical Harm) for "content or features related to the use of tobacco... products." The rejection states the app's concept is "not appropriate because it is focused on these products or activities." The issue: my app doesn't sell tobacco, doesn't facilitate purchasing it, and doesn't encourage consumption any more than a whiskey-tasting log encourages drinking. It's a personal tracking/journal tool — users log cigars they already own, rate them, track humidor inventory, etc. There is no e-commerce, no social sharing of consumption, no promotional content. There are currently multiple apps live on the App Store with functionally identical (in some cases nearly indistinguishable) feature sets: My Humidor – Cigar Journal — https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700 Humidor Journal Pro — https://apps.apple.com/us/app/humidor-journal-pro/id6751737114 Ember: AI Cigar Companion — https://apps.apple.com/us/app/ember-ai-cigar-companion/id6761503587 Whiskey and Cigar Pairing — https://apps.apple.com/us/app/whiskey-and-cigar-pairing/id6762530184 Cigarbase: AI Cigar & Humidor — https://apps.apple.com/us/app/cigarbase-ai-cigar-humidor/id6761301449 Leaf Enthusiasts — https://apps.apple.com/us/app/-/id6757314729 Cigar Journal & Tracker: Puro — https://apps.apple.com/us/app/cigar-journal-tracker-puro/id6760948482 ASHD – Cigar Social — https://apps.apple.com/ca/app/ashd-cigar-social/id6759581213 All of these are humidor/cigar journaling or social apps built around cataloging and tracking tobacco products — the exact category my app was rejected for. Several even use AI companion/recommendation features, which is a superset of what my app does. Full rejection text for reference: Guideline 1.4.3 - Safety - Physical Harm Issue Description: The app includes content or features related to the use of tobacco, nicotine-related, or vaping products, including but not limited to cigarettes, pipes, hookahs, or e-cigarettes. Apps with content or features related to consuming tobacco are considered to encourage the consumption of tobacco. Since these products pose a risk of physical harm to users, it is not appropriate to encourage their use. Next Steps: Your app's current concept is not appropriate because it is focused on these products or activities. It would be appropriate to revise the app or submit a new app that is not focused on these products or activities. My questions for the community: Has anyone successfully appealed a 1.4.3 rejection for a tobacco tracking/journal app (as opposed to a marketplace or vaping-hardware app) by citing comparable live apps? Is there a meaningful distinction reviewers are drawing between "journal/inventory" apps and something else, and if so, what specific wording or framing helped get it approved? Is the right move to reply in App Store Connect citing these examples, or file a separate appeal with the App Review Board? Any input from developers who've navigated this — especially in adjacent categories like whiskey, wine, or other regulated-but-legal-consumable tracking apps — would be hugely appreciated. This is my first submission, so I want to handle the response the right way rather than burning an appeal on the wrong approach. Thanks in advance.

Hello, I recently received a Pending Account Termination Notice for my Apple Developer Program account. The notice refers to section 3.2(f) of the Apple Developer Program License Agreement and says the account may have been involved in dishonest or fraudulent activity, including possible concept or feature switching after review. I have already submitted an appeal to the App Review Board. The difficult part is that the notice does not mention a specific app, bundle ID, version, or behavior. I have multiple apps under the account, so I am trying to identify what may have caused the issue. During my review, I found one possible area: one app uses different API server endpoints depending on the user’s IP region or network location. This was only done to improve connection speed and reliability. For example, overseas users may connect to an overseas server because access to Mainland China servers can be slow or unstable. The app is not intended to show different features, menus, content, or user flows across those servers. The server routing only changes the API endpoint for performance reasons. It is not used to detect App Review users or hide any functionality. I also have several other apps under the same developer account. These apps were previously reviewed and approved through the normal App Review process, and I did not intentionally implement any mechanism to mislead App Review, hide features, or change the app concept after approval. Because the notice applies at the account level but does not identify a specific app, bundle ID, version, or behavior, I am having difficulty understanding what exactly triggered this enforcement action. I am willing to review and correct any issue, but I need to understand whether the concern is related to regional server routing, a specific app implementation, App Store metadata, server-side configuration, or something else. My questions are: Can regional API routing based on IP or network location be misunderstood as dynamic content or feature switching after review? What kind of documentation or evidence is most helpful to provide in an appeal to show that different server endpoints provide the same app experience? Should I provide side-by-side API responses, backend configuration screenshots, and screen recordings from different regions? If the termination notice does not identify a specific app, is there any way to request clarification about the app, bundle ID, version, or behavior that caused the concern? Is there any recommended way to document multiple apps in an appeal when the notice is account-level rather than app-specific? I understand that nobody here can make a decision on my account. I am only looking for general advice on how to clearly explain this type of server routing, how to review multiple apps under the account, and what evidence is usually useful. Thank you.

Hi everyone, I want to start by saying that I genuinely appreciate the work Apple’s reviewers, support teams, engineers, and testers do. The volume and variety of apps they have to evaluate must be enormous, and I understand why Apple has to be careful about protecting users and the App Store from deceptive or unsafe apps. I’m posting because I’m looking for guidance from anyone who has navigated a Pending Account Termination appeal. This is for my first iOS app submission. The app is a location-based social planning app for adults to create and join nearby plans. It is a real product, not a template/spam app, and I have been trying to make review as straightforward as possible. Timeline: Submitted / Ready for Review: June 10, 2026 In Review: June 15, 2026 I also had a TestFlight external testing review delayed for about a week I submitted support requests and an expedited review request, but did not receive any responses 19 days after submission, I received a Pending Account Termination notice alleging dishonest or fraudulent activity under the Developer Program License Agreement I have submitted an appeal to the App Review Board. The web page confirmed receipt, but I did not receive a separate email or appeal case ID. I also opened a Developer Support case just to confirm the appeal is in the queue. I want to be very clear: the app is honest and there was no intent to evade App Review. Because the app depends on nearby user-generated plans, I had created demo/test data and a review account so reviewers would not see an empty app in a location with no users. After TestFlight external testing was approved and before sharing the public link with real testers, I removed the synthetic test/demo data so production would contain real user activity only. I have already taken corrective steps: Removed automatic review/demo reseeding behavior from the backend Removed synthetic demo users and content related to them from production Current production data is real user data only I understand Apple has to protect users and the App Store from deceptive apps, spam, and fraud, and I appreciate how difficult that job must be at scale. I’m trying to handle this carefully and respectfully. For anyone who has been through a Pending Account Termination appeal: Is it normal not to receive an appeal case ID by email? How long did the App Review Board take to respond? Is there any appropriate way to provide clarifying information after submitting the appeal, or should I wait for Apple to reply? Thank you for any guidance.

Hello, Our app, Cloudkeep Rivals, was rejected under Guideline 4.3(a) - Design - Spam. The App Review message says that the app appears to share a similar binary, metadata, and/or concept with apps previously submitted by a terminated Apple Developer Program account. The reviewed version was 1.0 (202606172035), with review date June 25, 2026, and Submission ID a03a3146-51b2-4440-967b-2326018fb06b. We are trying to understand what exactly triggered this rejection. We have asked App Review several times whether the issue is related to the build/binary, metadata, the game concept, similar heroes/characters, or a possible association with a terminated account. Unfortunately, the replies we receive appear to be mostly the same copy-pasted message, without any specific clarification about which part of the app is considered problematic or what exactly we need to change. We also tried to use the Contact Us / support channels, but we have not received a meaningful response to our support messages or emails. We have now been waiting for about one month without a clear answer. Has anyone experienced a similar Guideline 4.3(a) rejection and managed to resolve it? Is there any effective way to get a more specific explanation from App Review or reach the correct escalation path? We are not trying to flood support or dispute blindly. We simply want to understand the exact issue so we can either fix the problematic part or provide the correct explanation/evidence. Thank you.

Hi, I'm having a problem because my app stuck in "waiting for review" status since Friday (June 26th). Today is the fifth day we've been waiting for Apple to review the app. We had an app lunch scheduled for today and are stuck with no information. We contacted Apple via the standard contact form and requested expedited app review, but unfortunately, nothing has changed; we haven't received a response to our messages. The app is still "waiting for review." What should I do? Is there another way to contact Apple to expedite the review, or at least get information about the review date? App Name: Genie Vault App ID: 678469924

Hello everyone. I hope the Apple team sees my message. I submitted my app for review on June 15th. It's been in the "Waiting for Review" status since then. The app doesn't have any complex structures. No authorization (except for GameCenter), no encryption, etc. It's written in Swift, the native language, and is iOS-exclusive. I've contacted support three times, submitted a request for expedited review, and responded to the emails that arrived confirming my request, but there's been no response, even though the messages indicated a response within 24-48 hours. Apps are successfully submitted to the testing environment. I feel like I'm being ignored. Please help, I'm really looking forward to the App Store release due to the planned events. If anyone has had a similar situation, please share what helped and how long it took for your app to be reviewed, so I can understand how much longer I need to wait.

We get a message that says that our software submission has been approved. Some 10 minutes later, I go there and then find out that it has been deliberately removed by somebody at Apple, Inc again. Right, again... I don't know who is doing it. This is the 4th sabotage incident this year. I have sent a message by clicking on Contact Us. Every time I make an inquiry, a lady replies and says that she will have somebody contact us. But we never receive a followup. I don't know who is doing it. We definitely don't appreciate this type of harassment or sabotage by Apple, Inc. because we have to go there every time they approve our submission. This is a total waste of time. And it's nothing but stupid. They do it whether it's a new software submission or an update. They do it whether the development platform is iOS or macOS. No, we never use manual release.

Hi everyone, I'm encountering an issue with App Store Connect when using a beta version of Xcode and macos. Environment macOS: macOS Golden Gate Beta 27.0 Xcode: Version 27.0 beta 2 (27A5209h) Flutter: 3.41.9 App Store Connect: Production Issue I built my Flutter iOS application using the latest Xcode beta. The archive completed successfully. The build uploaded to App Store Connect without any errors. The build finished processing successfully. The build was available in TestFlight. However, when I tried to add the build to an App Store version and clicked "Submit for Review", App Store Connect displayed an error indicating that builds created with a beta version of Xcode cannot be submitted for review.

Hi Apple Developer Team / Community, I am seeking guidance regarding a difficult distribution issue for our company’s internal iOS application. Our app, FORTIS HRM, is an internal Human Resource Management application used exclusively by employees of FORTIS GARMENTS LTD. It handles attendance, leave requests, approvals, employee directory access, and other HR-related operations. The app is not intended for general public use. Background We initially submitted the app as a public app on the App Store. The app was rejected by App Review for public distribution, since it is intended only for internal employee use and is not suitable for general public users. Based on that, we switched to Apple Business Manager (ABM) / Custom App distribution as a more appropriate solution. The app was reviewed and approved under the custom app distribution path and marked ready for distribution. Unfortunately, our Apple Business Manager enrollment failed repeatedly due to organization verification issues, and our organization was eventually removed from ABM. Since ABM became unavailable, we applied for Unlisted App Distribution. Apple Developer Support informed us that custom apps cannot be converted to unlisted distribution and instructed us to create a new public app record and submit a new unlisted request using a new Apple ID. Following that guidance, we created a new public app record: App Name: FORTIS HRM Apple ID: 6785417374 We have submitted a new unlisted app distribution request and are currently waiting for review. Current Issue We feel stuck between all available distribution methods: Public distribution → rejected because app is internal-only ABM / Custom App → blocked due to organization verification failure Unlisted distribution → currently under review This has created a situation where no clear distribution path is available for our employee-only app. Request for Guidance We would appreciate guidance on the following: Has anyone experienced repeated ABM verification failures, and how was it resolved? Is there any recommended path for internal business apps when ABM is unavailable? Is there any way to ensure the App Review team understands the full context of this case? Request to App Review Team We respectfully request attention from the App Review team. This application has already been reviewed multiple times under different distribution paths. The app’s functionality remains essentially the same; only the distribution method has changed due to Apple’s requirements. This app was previously reviewed and approved by Apple under the custom app distribution path and marked ready for distribution. Since the core functionality remains unchanged, we kindly request consideration of this prior review history during the current review process. We would greatly appreciate any assistance in completing this review as efficiently as possible. Thank you for your time and support.

My app (RunWeather) is live on the App Store, but its two auto-renewable subscriptions have never reached Approved, so the StoreKit paywall returns no products and users can't subscribe. Subscriptions: com.iustinn.runweather.pro.monthly com.iustinn.runweather.pro.annual Both show "Pending Binary Approval". The English (U.S.) localization on each is stuck in "Rejected", and App Store Connect won't let me edit or delete that localization (the fields are locked), so I can't correct the copy and resubmit. I never received a clear reason for the localization rejection. History: each time I submitted a build with these subscriptions, the build was rejected for an unrelated reason; I resubmitted, the build was eventually approved, but the subscriptions stayed behind in this stuck state. I also created duplicate subscription products (…monthly2/3/4, …annual2/3/4) as a workaround; those just sit in "In Review" indefinitely. What I've tried: Editing / deleting the Rejected U.S. localization -> blocked, fields locked. Re-submitting builds -> app approved, subscriptions not. Questions: How do you unstick a subscription whose Rejected localization can't be edited or deleted? Is an App Review support ticket the only path to reset it? For "Pending Binary Approval" subscriptions, does attaching them to a NEW app version (reusing the existing build, no new binary) and submitting force them back through review? Has anyone cleared this exact locked-localization state another way? I've also opened an App Review case. Posting here in case someone hit the same locked-localization state. Thanks.

Hello, Our app has been in "Waiting for Review" status for more than a week, and our previous submission also took over a week to be reviewed. This delay is affecting our planned release schedule. App details: App name: Nhật Luân Kiếm App ID: 6777269196 We'd really appreciate any guidance on the current review timeline, or whether there is anything on our side we can do to help move the review forward. We're happy to provide any additional information if needed. Thank you very much for your time and support. Best regards.

I would like to start up by saying how much I appreciate all the Apple employees, developers, reviewers, and testers for the incredible job they do. The number of apps that come through on a daily basis is probably astronomical. All that said, I am a bit curious as to why I was able to put three different apps into review in the last 24 hours, and as of now, they have all 3 been processed and released. In the meantime, I have an app that is still in Waiting for Review. This app has some core functionality involved as well as some more simple text changes. I’d to hear from Apple at the least, what is the hold up. If there is a code issue, tell me. If there is a behavior or UI issue, tell me. One of these changes was time critical for releasing in June. Thanks for letting me vent. I just hope the App Review folks look into it.

Hello everyone, I’m looking for advice from developers who have been through a Guideline 4.3(a) (Design – Spam) rejection. Our game was rejected under Guideline 4.3(a). We genuinely believe it is an original Unity project that we developed from scratch. Instead of immediately submitting a new build, we replied through the Resolution Center with extensive supporting documentation, including: Figma design history Unity project structure Development timeline Original UI/UX workflow Comparisons explaining how our game differs from similar titles We also submitted a formal appeal to the App Review Board and later sent a polite follow-up message. It has now been 12 days since our last message, and we still haven’t received any response from Apple. I’m not asking whether our rejection was correct or incorrect. I’m simply trying to understand the review process. For developers who have experienced this: Is waiting 10–14+ days after submitting evidence normal? Did Apple eventually respond? Did they continue the conversation in the Resolution Center, or did they ask for a new build? Is there anything else we should do besides waiting? Any experiences or advice would be greatly appreciated. Thank you!

Hello Apple App Review Team, I’m an independent developer and I’m hoping someone can point me in the right direction or let me know if this is simply an unusually long review. My app, PM Quest Prep, has already been approved and is currently available on the App Store. The only thing preventing my full launch is that every subscription-related item has remained in “Waiting for Review” for over two weeks. At this point I’m not sure if everything is simply waiting in the normal review queue or if something may have become stuck. App Information App Name: PM Quest Prep App Apple ID: 6772685314 Bundle ID: com.questforge.pmquestprep SKU: PQP-IOS-001 ⸻ Subscription Group PM Quest Prep Pro Subscription Group ID: 22130056 Status: Waiting for Review ⸻ Subscriptions PM Quest Prep Pro Monthly Apple ID: 6776040575 Product ID: pm_quest_prep_monthly Status: Waiting for Review PM Quest Prep Pro Quarterly Apple ID: 6776043289 Product ID: pm_quest_prep_quarterly Status: Waiting for Review PM Quest Prep Pro Yearly Apple ID: 6776060042 Product ID: pm_quest_prep_yearly Status: Waiting for Review ⸻ Additional Items Waiting for Review Along with the subscriptions themselves, the following items are also still waiting: Subscription Group Subscription Localizations Subscription Display Information Subscription Promotional Images Promotional Image Assets Everything associated with the subscription group appears to be waiting together. ⸻ What I’ve Already Verified Before posting here, I wanted to make sure I wasn’t overlooking something. I’ve confirmed the following: The app itself has already been approved and is live on the App Store. Banking information has been completed. Tax information has been completed. The Paid Applications Agreement has been accepted. Pricing has been configured. Availability has been configured. Subscription metadata has been completed. Localizations have been completed. Promotional images have been uploaded. StoreKit implementation has been tested. App Store Connect is not showing any warnings, errors, or requests for additional information. From everything I can see, there isn’t anything left for me to complete. ⸻ Apple Developer Support I also opened a support case before posting here. Developer Support Case ID: 102919993053 Support emails were sent on: June 19, 2026 June 26, 2026 I’m still waiting for the subscriptions and all related assets to move beyond Waiting for Review. ⸻ Why I’m Asking I’ve spent the last several months building PM Quest Prep, and it’s exciting to finally have the app available on the App Store. Unfortunately, users can’t subscribe to the Pro features until these subscription reviews are completed, so the app can’t fully launch as intended. I’m completely understanding if review times are simply longer right now—I just want to make sure there isn’t an issue on my account or something I’ve unintentionally missed. If an Apple App Review engineer happens to see this post, would someone be willing to verify whether everything is still progressing normally or if there’s anything preventing these subscriptions from being reviewed? If you need any additional information from me, I’ll be happy to provide it immediately. Thank you very much for your time, and thank you to the App Review team for everything you do. Best regards, Dustin Harris Developer of PM Quest Prep

Hi everyone, and hopefully Apple Staff, I am looking for some advice or assistance regarding an unusually long App Review delay for our game. On June 23 (Tuesday), we submitted a comprehensive appeal and build (v1.0.5). It has been 7 days and our app is still not in the "In Review" state. This unexpected delay is severely impacting our marketing schedule in Turkey. We have pre-launch campaigns, offline events, and schedules with about 30 local KOLs that are being continuously delayed, causing significant financial and operational impact. I have already submitted an Expedited Review Request, but I haven't received any updates yet. Has anyone else experienced similar delays recently after an appeal? Are there any Apple representatives here who could kindly take a look at our Submission ID? Any advice on how to proceed would be greatly appreciated. Here are the details of our submission: App Name: Era Online: Şeref Savaşı App ID: 6773240689 Bundle ID: com.ark.xhmzxqteq.ios Submission ID: d19cb33a-b179-4f82-85e7-4acc77f46968 Thank you so much for your time.

Hi everyone, and hopefully Apple Staff, I am looking for some advice or assistance regarding an unusually long App Review delay for our game. Here are the details of our submission: App Name: Era Online: Şeref Savaşı App ID: 6773240689 Bundle ID: com.ark.xhmzxqteq.ios Submission ID: d19cb33a-b179-4f82-85e7-4acc77f46968 Background: Our app was previously rejected under guidelines 2.1(a) - App Completeness and 4.3(a) - Spam. On June 23 (Tuesday), we submitted a comprehensive appeal and a new build (v1.0.5): For 2.1(a): We completely fixed the occasional iPad crash issue and thoroughly tested the new build. For 4.3(a): We provided extensive legal documentation proving we hold the exclusive publishing rights for this game in Turkey. We also demonstrated that our app is a highly customized, exclusive version for the Turkish market, featuring a 300,000-word localization, local voice acting, unique IAPs priced in Turkish Lira, dedicated servers in Ankara, and exclusive in-game classes. The Issue: It has been a week, and our app is still not in the "Waiting For Review" state. This unexpected delay is severely impacting our marketing schedule in Turkey. We have pre-launch campaigns, offline events, and schedules with about 30 local KOLs that are being continuously delayed, causing significant financial and operational impact. I have already submitted an Expedited Review Request, but I haven't received any updates yet. Has anyone else experienced similar delays recently after an appeal? Are there any Apple representatives here who could kindly take a look at our Submission ID? Any advice on how to proceed would be greatly appreciated. Thank you so much for your time.

Repeated "Invalid Binary" rejections with no error code or explanation — 9 builds, no guidance I'm building a simple React Native/Expo app — essentially a link hub pointing to pages on our website (booking, events, Facebook group, etc.). Nothing exotic: no special entitlements, no background processes, no third-party SDKs beyond standard Expo modules. I'm now on build 1.0.0 (9) and every single submission has come back as "Invalid Binary" with zero explanation — no ITMS error code in App Store Connect, and no rejection email ever arrives (confirmed by checking spam and verifying my Apple ID email is correct and monitored). What I've already ruled out / fixed along the way: Upgraded Expo SDK to match the latest patch version Fixed a corrupted splash screen asset (was a JPG mislabeled as PNG) Populated the submit section in eas.json with correct Apple ID, ASC App ID, and bundle identifier Confirmed Apple ID email matches across Apple Developer account and EAS config Accepted the most recent Developer Program License Agreement update Excluded visionOS support explicitly in app.json Verified app icon is a proper 1024x1024 square PNG with no transparency I opened a support case (#102916564146) and was told it would be escalated to App Review. That was over two weeks ago with no follow-up. Has anyone dealt with a persistent silent "Invalid Binary" loop like this? Specifically interested in whether there's a way to request the actual ITMS error code when App Store Connect and email both come up empty.

Our Flutter app has been rejected by App Review 4 times with this description: "Login screen cleared the email and password fields when we attempted to enter the demo account details, preventing us from logging in." Review environment: Device: iPad Air 11-inch (M3) OS: iPadOS 26.4.2 Flutter version: 3.41.4 State management: GetX We cannot reproduce this on: Real iPhone (iOS 18.x) — works fine iPad simulator (iPadOS 26.3.1) — works fine Our TextEditingControllers are created inside a GetX controller, not inside build(), so they survive widget rebuilds. Questions: Has anyone seen text fields clearing or not retaining input specifically on iPad with iPadOS 26? Are there any known Flutter issues with text input on iPadOS 26 that could cause this? Is there anything different about how iPad handles text input vs iPhone that we should be aware of? Any help appreciated — this is blocking our App Store approval.