I'm hoping someone from Apple engineering can help, as support tickets and callbacks have not resolved this issue. The problem: My app "Brutal Time - Typographic Clock" does not appear in App Store search results at all — not even when searching for its exact name "Brutal Time." This has been ongoing for over six weeks. Additionally, the app does not appear in Apple Search Ads when I try to set up a campaign — suggesting this is a backend indexing issue, not a ranking issue. Timeline: Dec 17, 2025: App launched, initially searchable Dec 31, 2025: Transitioned to freemium model, became invisible in search. Jan 5, 2026: Fixed the issue, submitted update (v2.02), approved same day Jan 14, 2026: Submitted metadata update (v2.03) to improve discoverability, approved same day Feb 8, 2026: Tried removing from sale and re-adding to force re-index — no effect Feb 10, 2026: Still not appearing in any search results What I've tried: Submitted multiple support tickets (most recent: Case #102797235758) Each ticket generates an automated reply stating Apple will respond within 2 business days — they never have Requested and received callbacks multiple times, was told it would be escalated to US engineering team. But no follow-up, no resolution, no explanation Removed from sale and re-added to attempt to force re-indexing — didn't work App shows "Ready for Distribution" in App Store Connect Direct link works fine: https://apps.apple.com/us/app/brutal-time-typographic-clock/id6756289461 Response from Apple Support: "The behavior you observed is expected. App Store charts and search results change regularly and we don't guarantee app placement." This response misses the point entirely. I'm not asking about rankings — I'm asking why the app is completely invisible in search, including for its own branded name. This is not an isolated issue. Other developers have reported the same problem with the same non-response from Apple: https://developer.apple.com/forums/thread/803937 https://developer.apple.com/forums/thread/73981 https://developer.apple.com/forums/thread/74110 Has anyone found a resolution? Is there any way to trigger a proper re-index, or escalate to someone who can actually investigate?

A newly released iOS app has been available for approximately three weeks, but I still cannot find it by searching its exact name in the U.S. App Store. Several U.S.-based people whom I asked to independently test the same search were also unable to find it using their own devices and accounts. The same issue occurs on Apple’s public U.S. App Store website. The app’s direct link works normally, and searching for the developer name returns the app, but searching for the exact app name only returns unrelated apps. I submitted Developer Support case 20000142933730 approximately one week after the app became available, so the issue was already well beyond the normal 24-hour post-approval period. Apple Support reproduced and documented the issue before the case was escalated. After multiple phone calls and emails, the case has been assigned to three different Advisors. The current Senior Advisor says the app appears in her search environment and asked me to provide a screen recording. I sent the requested screen recording and screenshot, but was subsequently asked to provide the same evidence again. My questions have not been answered. Her response also referenced an unrelated case number. I do not intend to criticize any individual Advisor. However, I am increasingly concerned that the complete case history and submitted evidence have not been reviewed, and that the case may be stuck in a Support loop rather than reaching the team that can investigate App Store search behavior. This issue is significantly delaying the app’s launch and preventing users from discovering it through normal App Store search. Could an Apple staff member please help confirm whether case 20000142933730—including Apple’s previous reproduction and the screen recording and screenshot I submitted—has been forwarded to the Engineering team responsible for App Store search? If any other developers have experienced inconsistent exact-name search results across different App Store user environments, I would also appreciate hearing how the issue was resolved.

Hi everyone, I’m looking for guidance regarding an unusually long App Review delay. My first iOS app, EmpowerFI, has been in “Waiting for Review” for almost 30 days. In two days, it will reach a full month without moving to “In Review.” During this period, I have contacted Apple Developer Support several times. After my initial contact, Apple submitted an expedited review request as a one-time exception for my app. However, the status did not change. I contacted support again and received the following response: “We have confirmed that your app review is proceeding normally, and there is no further action you need to take.” I have followed up multiple times since then, explaining that I am not asking Apple to guarantee a review or approval date. I am simply trying to understand why this particular submission has remained in “Waiting for Review” for almost a month. Unfortunately, I continue to receive essentially the same standard response. There are no pending actions visible in App Store Connect, and Apple Support has explicitly confirmed that there is nothing further required from me. I fully understand that review times vary and that some apps may require additional scrutiny. However, almost 30 days without even moving from “Waiting for Review” to “In Review” seems exceptionally long, particularly after an expedited review request was submitted. I also know developers who submitted apps during this period and received a review response within approximately two days, so I am trying to understand whether there could be something specific affecting my submission. Has anyone recently experienced a similar delay with a first app submission? More importantly, is there any other appropriate escalation path when Developer Support confirms that everything is normal but the app remains in “Waiting for Review” for almost a month? I am not looking to bypass App Review or request guaranteed approval. I would simply like someone to investigate whether there is an issue affecting this submission or explain why it has remained in the queue for such an exceptional amount of time. Any guidance from Apple staff or developers who have experienced this recently would be greatly appreciated. Thank you,

Apple 团队及各位开发者，你们好： 我是一名独立开发者，希望就开发者会员资格终止后的沟通渠道和恢复申请流程获得指引。 我的账号下共有九款 App，其中八款此前已在 App Store 上架。近期发生的情况如下： 2026 年 9 月 11 日： App Store Connect 显示依据《Apple Developer Program 许可协议》第 3.2(f) 条发出的待终止通知，账号下此前上架的 App 被下架。 2026 年 9 月 12 日： 我通过指定的 App Review Board 表单提交申诉。该表单当时最多允许添加五款 App，提交完成页面确认已收到这五款 App 的申诉请求。 2026 年 9 月 14 日： 我陆续在这五款 App 的通讯页面收到回复。每份回复都有不同的申诉编号，但实质内容相同，均表示调查已完成，并维持终止开发者会员资格的决定。 我理解，这些回复涉及的是账户级决定，而不只是某一款 App 的普通审核拒绝。回复同时告知，会员资格正式终止后，可以申请恢复。 目前最困难的是：通知列举了可能涉及的违规行为类别，但没有指出本次认定所依据的具体事例。 例如，我仍不清楚相关认定对应的是哪款 App、哪个版本或 Build、哪项功能、哪段元数据、哪次沟通回复，或哪项账号相关活动。 我对这一结论有异议。我没有故意隐藏功能，也没有设置以规避审核为目的的机制。我愿意提供相关记录，解释可能存在的事实理解偏差，并纠正确认存在的问题。但在缺少具体事例的情况下，很难准备有针对性、可验证的说明和改进计划。 我理解开发者论坛不能代替 App Review Board 处理账户申诉。我不是要求论坛参与者直接撤销决定，也不要求披露内部检测方法、审核人员身份或第三方保密信息。 希望获得以下流程方面的指引： 申诉已有结论后，应通过哪个官方私密渠道请求具体说明？ 我已有 Developer Support 案例，希望了解如何请求足以供我核实、回应和采取改进措施的信息。 在通知没有提供具体事例的情况下，应如何组织恢复申请？ 哪些材料最有助于区分事实澄清、已经完成的改进，以及尚待实施的计划，避免依靠猜测作出不准确的陈述？ 应如何确认正式终止的生效状态，以及何时可以提交恢复申请？ 对于涉及同一账户、分别关联五款 App 的申诉编号，后续请求应如何引用和关联？ 我可以通过 Apple 官方私密支持渠道提供申诉编号、支持案例编号及相关材料，因此没有在公开帖子中列出这些信息。 这件事对我的开发工作影响很大。我希望准确理解实际问题，通过合适的程序提供有针对性的证据，并争取恢复会员资格的机会。 感谢任何关于正确渠道和后续步骤的指引。 Hello Apple team and fellow developers, I am an independent developer seeking guidance on the appropriate communication channel and process for preparing a membership reinstatement request. My account contains nine apps, eight of which had previously been available on the App Store. The timeline is as follows: September 11, 2026: App Store Connect displayed a Pending Termination Notice citing Section 3.2(f) of the Apple Developer Program License Agreement. My previously available apps were removed from the App Store. September 12, 2026: I submitted an appeal through the designated App Review Board form. The form allowed me to add a maximum of five apps at that time, and the confirmation page acknowledged receipt of the appeal request for those five apps. September 14, 2026: I received responses in the communication pages for all five apps. Each response has a different appeal ticket number, but the substantive wording is identical. The responses state that the investigation is complete and maintain the decision to terminate my developer membership. I understand that these responses concern an account-level decision, rather than an ordinary review rejection for an individual app. They also state that I may request reinstatement once the membership is formally terminated. My main difficulty is that the notifications list categories of potentially prohibited conduct without identifying a specific example underlying the finding in my case. I do not know which app, version or build, feature, metadata, communication, or account-related activity led to the decision. I disagree with the conclusion. I have not deliberately hidden functionality or implemented a mechanism intended to evade App Review. I am willing to provide relevant records, address possible factual misunderstandings, and correct any confirmed deficiencies. However, without a specific example, it is difficult to prepare a targeted, verifiable explanation and improvement plan. I understand that the Developer Forums cannot replace the App Review Board’s account appeal process. I am not asking forum participants to overturn the decision or disclose internal detection methods, reviewer identities, or third-party confidential information. I would appreciate guidance on these procedural questions: After an appeal has been decided, which official private channel should I use to request actionable clarification? I already have a Developer Support case and would like to understand how to request enough information to investigate, respond, and take appropriate corrective action. How should a reinstatement petition be organized when the notification does not identify a specific example? What evidence would best distinguish factual clarification, completed improvements, and proposed changes, without relying on speculation or making inaccurate statements? How should I confirm the effective status of formal termination and when I may submit a reinstatement request? How should I reference and associate the five app-specific appeal ticket numbers in a follow-up concerning the same membership? I can provide the appeal references, Developer Support case number, and relevant materials through an official private support channel, so I have not included those details publicly. This decision has significantly affected my development work. My goal is to understand the actual concerns, provide focused evidence through the appropriate process, and seek an opportunity to restore my membership. Thank you for any guidance on the correct channel and next steps.

My game was submitted for app review for few round, every time they rejected and i resolve the issue, but latest they reject as Guideline 4.3(a) - Design - Spam and dont have response more than 1 week, I am confusing, early stage was Code of developer (showing what my game have with recording),later follow by some bug fix, then design copy-cat ( the game is totally written by me), but then i asked many round please pin point which part. End up they reject with "Guideline 4.3(a) - Design - Spam" and i replied with full list of unique feature my game have and explaination on some feature where mostly every game have it such as stamina regen, ranking, gacha. Please help, my game was on google play for 1 week plus, some players of follower was asking for ios. google play link : https://play.google.com/store/apps/details?id=com.bubluestudio.beyondgod

Hi, I'm still new to this. I need advice on this. What should I do? Do I need to test my product only on the website domain first before I can publish it in the App Store, or can I just fill in all the information they need?

Since our 1.3.20 update reached users on Sept 11, 2026, a handful of devices terminate at launch right after the App Store auto-update. Restarting the device does not help; deleting the app and reinstalling it from the App Store does. Filed as FB24755993 with 9 crash reports, the delivered package's SC_Info/Manifest.plist and a per-binary fingerprint. What the crash reports say (all identical) Exception Type: EXC_CRASH (SIGABRT) Termination: namespace DYLD, code 1, "Library missing" (terminated at launch; ignore backtrace) Library not loaded: @rpath/FBSDKCoreKit.framework/FBSDKCoreKit Referenced from: <DDB434B7-...> /Volumes/VOLUME/*/Runner.app/Runner Reason: tried: '/private/var/containers/Bundle/Application/<UUID>/Runner.app/Frameworks/FBSDKCoreKit.framework/FBSDKCoreKit' (could not register fairplay decryption, mremap_encrypted() => -1) Backtrace: dyld4::prepare -> dyld4::halt -> abort_with_payload Devices so far: iPhone XR / iOS 18.7.10 (22H374), iPhone 16 / iOS 26.6, iPhone 16 / iOS 18.7.7, plus one more not yet identified. The same package launches normally on the large majority of the ~12,000 devices that updated that day. Delivered Info.plist: DTAppStoreToolsBuild 27A261, DTXcodeBuild 17F113, MinimumOSVersion 15.0. What we established The main executable decrypts fine (dyld reaches dyld4::prepare); the failure is on the first @rpath framework in the load order, which is also the first FairPlay-encrypted embedded binary. It is not specific to the Facebook SDK. The package Apple delivers (pulled with Apple Configurator) is structurally consistent: every binary with LC_ENCRYPTION_INFO_64 has cryptid 1 and SC_Info/<name>.supp/.supf/.supx/.v4.supp/.v5.supf (main executable, App, Flutter, FBSDKCoreKit, FBAEMKit, FBSDKCoreKit_Basics, objective_c, sqlite3, the widget appex); the Firebase/Google frameworks are cryptid 0. SC_Info/Manifest.plist has SinfPaths = [SC_Info/Runner.sinf] and SinfReplicationPaths for all 12 binaries. Only the main Runner.sinf ships; the framework-level .sinf files have to be produced at install time from SinfReplicationPaths. The symptom looks like that replication not being applied to the frameworks after the delta update on the affected devices, while a fresh full install performs it. Nothing in our bundle changed between 1.3.19 and 1.3.20 except Dart code (App.framework): same Xcode 26.6 (17F113), same Flutter engine, byte-identical Facebook SDK 18.1.1 binaries (the only fat arm64+arm64e binaries in the bundle), same Firebase SDK. Both versions run normally from TestFlight and Xcode. The 1.3.20 encrypted variant carries SC_Info timestamps about 18 h after Ready for Sale, coinciding with the start of the auto-update wave. We could not obtain the delivered 1.3.19 package for comparison. Questions Has anyone seen this class of failure since early September, or with packages processed by DTAppStoreToolsBuild 27A261? Is there anything about a bundle (fat arm64+arm64e embedded frameworks? many encrypted frameworks?) that makes the framework .sinf replication on the delta-update path fragile? Is there any developer-side mitigation other than telling users to delete and reinstall? The closest earlier report I found is thread 718950 (2022, iOS 15.7–16.1, ~1 in 200 installs, "reinstall fixes it"); this looks like the same failure but concentrated on one update. fingerprint-1.3.20.json

I’m looking for advice on App Store positioning for a slightly unusual developer-tool workflow. I have: Reality Prep Pro — macOS Prepares, validates and optimizes spatial assets. Reality Prep Preview — visionOS Verifies the resulting USDZ on Vision Pro and returns device evidence to the Mac workflow. The value is primarily in using them together: prepare on Mac → verify on Vision Pro → return evidence → detect when the asset changes and needs re-testing. Both apps can stand alone, but they were designed as complementary tools. For anyone who has marketed companion apps across Apple platforms: would you position the App Store pages primarily around each individual app, or make the cross-platform workflow the central story? I’m especially interested in approaches that remain clear to users without making either product page dependent on the other app.

Initially, I had some issues enrolling in the individual Apple developer program. Then, I contacted support via email, and they finally requested that I verify my identity. I submitted my national ID for verification and then received an email stating that my identity was verified. After that, I tried to enroll in the Apple developer program, but the issue persisted even after they instructed me to proceed. Subsequently, I received an email stating that my identity was not verified. Here is the exact wording from the email: "We can’t verify your identity with the Apple Developer app or provide further assistance with the Apple Account for Apple developer programs." After that, I tried to reach support several times, but there has been no response from them.

An update to our 10-year-old passport photo app for macOS was rejected under “Guideline 1.1.6 - Safety - Objectionable Content.” We have neither changed any of the app's existing features nor added new ones. This update only included minor changes to the user interface and an update to the age rating questionnaire in App Store Connect. This is the reason for rejection provided to us by the reviewer: Guideline 1.1.6 - Safety - Objectionable Content Issue Description The app contains content or features that are misleading, intended to deceive users, or are otherwise fraudulent. Specifically, the app provides services for editing photos for government documents. Note that adding a disclaimer to the app description is not sufficient if the rest of the metadata and the app are misleading. Next Steps It would be appropriate to remove any content or features from the app that could be misleading or enable fraudulent activity before resubmitting for review. We are having difficulty understanding how Guideline 1.1.6 applies to our app. The app is simply a tool for creating passport photos. Users select their own portrait photo and manually position and crop it to the required photo dimensions. The app does not manipulate the content of the photo, change facial features, or alter a person's appearance. The app has been available for approximately 10 years and is also used as a professional tool by photographers around the world to prepare and print passport and ID photos for their customers. It does not edit passports, ID cards, visas, or any other government documents. The output is simply a portrait photo in the selected dimensions that can be saved or printed. The country-specific presets provide the required photo dimensions as well as a visual mask for head size and positioning, based on publicly available specifications published by the relevant authorities in each country. These presets are used only to help the user manually align and crop the portrait photo according to those published requirements. They are not templates for government documents. We have submitted an appeal, as we believe there may be a misunderstanding about what the app actually does. Has anyone else encountered a rejection under Guideline 1.1.6 for a passport photo or similar photo-formatting app? We would particularly appreciate any insight into the statement that providing services for “editing photos for government documents” falls under Guideline 1.1.6. Is there a specific App Review policy regarding passport photo apps that we may have overlooked? For additional context, this particular app does not include background replacement or automatic cropping. However, even if an app did offer such features, passport-style photos are not used exclusively for passports or government-issued identity documents. They can also be used for driver's licenses, student IDs, fishing licenses, membership cards, employee IDs, and many other purposes. For some of these use cases, background replacement may be perfectly acceptable. Requirements also vary depending on the country, authority, and intended use of the photo. It would therefore seem reasonable for users to decide how to prepare their photos based on the requirements applicable to their particular use case. We would be very interested to hear how other developers interpret this guideline and whether anyone has encountered a similar situation. Any experiences or advice would be greatly appreciated.

Hi Apple Team and Developer Community, We are looking for guidance on how to best escalate / resolve an ongoing App Review issue. Our app has been going through multiple App Review cycles for nearly three months. Each time, we address the specific concern raised, provide clarification or documentation, and resubmit. However, after one issue appears to be addressed, a new or related issue is raised in the next round. This has resulted in a prolonged review cycle despite repeated responses and supporting documentation. The current issue relates to Guideline 3.2.1(viii) for an India financial-services app. We have provided detailed clarifications and supporting documents through App Review, including partner documentation, entity-structure documents, and explanations of the relevant user flows. We have also: submitted an appeal; requested expedited review; raised a Developer Support case; and requested an App Review appointment / call. The expedited review has been accepted, but we are still waiting for closure. The earliest available App Review appointment is much later, and the delay is causing material business impact. We are not looking to debate the guideline publicly or disclose confidential review materials here. We would appreciate guidance on the correct process to have the App Review team review all open issues together, or to arrange a call/escalation so that remaining concerns can be clarified in one discussion rather than through repeated review iterations. Thanks in advance for any guidance.

Hi. On my iOS app, both the app store and the device are making changes to my app icon to make it look more Liquid-Glass. See attached image showing my original icon, and then how it appears on the app store and on devices. There is an added bevel/3d effect. I'd like to not have this happen. Did anybody figure out how to turn this off? So that the icon appears as submitted. I've played around with Icon Composer a bit but haven't managed to turn this off there. And would prefer to just submit the png's. Thank you!

I'm an iOS developer in India, not yet enrolled, and I want to confirm my distribution architecture before I incorporate and pick an account type. What I'm building: patient-facing appointment and clinic-management apps for independent single-doctor clinics. One shared codebase; branding, clinic details, and backend configuration differ per clinic. The clinics will not enrol in their own Apple Developer Program accounts. I would register a company and enrol as an Organization, that company provides the software platform, while the medical services are provided by the individual clinics. Under 4.2.6 and 4.3(a), is a separately branded app per clinic viable from a single Organization account? My reading is no, and that the aggregated or "picker" model, one app where patients select their clinic, is the intended path. Is that correct? Under 5.1.1(ix), for that aggregated app, is my company an acceptable seller given that the medical services themselves are delivered by the clinics? Or does Apple expect each clinic to be the seller? If separately branded per-clinic apps are only possible when each clinic enrols in its own account, can I be added to their teams and submit on their behalf, or must the clinic itself submit? Are there additional review requirements for apps tied to medical practices, clinic licensure documentation, proof of authorisation to publish on their behalf, or a regulated medical device declaration, where the app only handles appointments, records, and clinic administration rather than diagnosis or measurement? Developer Support case 20000147392668 (they directed me here for the guideline questions).

Hello, Apple! I accidentally uploaded a version with a critical bug. Apple, please accept my new version—it’s urgent. Thank you very much.

Hello Everyone, I have published my app few months back . The app does not show up in search when I search with the app name . It's a social media app and i provided the right key words . FYI- But when I search the app with combining the company name and app name it shows up. I am in contact with apple support for last 1 month and all the time , i get the an answer that the engineers are woking on it. They even suggested me to include the app name in the Key words, which I did , but no results. Today the supervisor suggests that support team might not be able to do much and I have to revisit my settings. I don't know what else to change other than the key words. . He also highlighted that since Language EN was chosen and the my app name is not an english word, could be also the reason for it not showing up in the search. Can someone please help to provide a solution to this.

My Apple Developer account was recently terminated, and I received an email stating that the reason was section 3.2(f) of the Apple Developer Program License Agreement. However, I have not changed anything recently in our apps, business model, or developer activity, and I genuinely do not understand the reason behind this termination. I have always tried to follow Apple’s guidelines carefully and act in good faith. This termination has severely impacted my work and users, and I am urgently requesting clarification regarding what exactly triggered this action. If someone from Apple or the App Review / Developer Relations team could please contact me or review the case again, I would greatly appreciate it. Thank you.

We are a team of developers, and our company is involved in creating mobile applications. Recently, our developer account was terminated, and all active apps were removed from the App Store. The email mentioned that our app violates section 3.2(f) of the Apple Developer Program License Agreement. We've been trying to identify the issue since then, but we're not involved in any fraudulent activities. Our company is facing a critical situation as it is essential for us to have the apps back on the App Store as soon as possible. We are unsure of how to proceed and would greatly appreciate any assistance or guidance. Thanks. Our app ID com.seriktes.kz App name Seriktes

Hi everyone, I submitted my app for App Store Review almost two weeks ago, and the submission has been stuck in “In Review” status ever since. I understand that review times can vary, but this seems significantly longer than the usual review period. There haven’t been any requests for additional information or clarification from the App Review team, and the status hasn’t changed during this time. Has anyone else experienced an unusually long review period recently? Is there anything I should do at this point, or is it best to continue waiting? I’d appreciate any advice or insight from developers who have experienced a similar situation. Thank you!

I would like to report a serious and repeated pattern of potentially misleading and impersonating applications published on the Mac App Store under the seller/developer name Mihai Graure. This is not a complaint about one isolated app. The same developer has published multiple applications using the names, branding, interfaces, and visual presentation of major services including LinkedIn, Zoom, Google Drive, Twitch, X/Twitter, TikTok, Facebook, Instagram, and Gmail. Reported applications: Desktop App for LinkedIn https://apps.apple.com/us/app/desktop-app-for-linkedin/id6786838795?mt=12 Desktop App for Zoom https://apps.apple.com/us/app/desktop-app-for-zoom/id6796387421?mt=12 App for Google Drive & Docs https://apps.apple.com/us/app/app-for-google-drive-docs/id6792317542?mt=12 App for Twitch https://apps.apple.com/us/app/app-for-twitch/id6797809667?mt=12 Desktop App for X (Twitter) https://apps.apple.com/us/app/desktop-app-for-x-twitter/id6786838258?mt=12 App for TikTok https://apps.apple.com/us/app/app-for-tiktok/id6783051609?mt=12 App for Facebook https://apps.apple.com/us/app/app-for-facebook-%C2%BA/id6770487788?mt=12 Apps for Instagram https://apps.apple.com/us/app/apps-for-instagram/id6778116535?mt=12 Desktop App for Gmail https://apps.apple.com/us/app/desktop-app-for-gmail/id6770216468?mt=12 My main concern is the overall presentation of these apps to customers. The developer uses the names of globally recognized services directly in the app titles. A user searching for Gmail, Instagram, Facebook, LinkedIn, Zoom, TikTok, Twitch, Google Drive, or X could reasonably believe these are official desktop apps or apps authorized by the companies that operate those services. The concern is not limited to the names. The apps also appear to reproduce or closely imitate the official user interfaces, layouts, navigation, branding style, and visual presentation of the services they reference. The App Store screenshots appear identical or extremely similar to the official interfaces users already recognize. This combination can create a very strong impression of legitimacy: the official product name is used in the title, the screenshots closely resemble the real service, the UI looks like the official product, and the app is presented as a dedicated “Desktop App” or “App for” that service. I specifically request that Apple compare the screenshots and the actual installed apps side-by-side with the official websites and applications of the corresponding companies. Apple should verify whether the developer has authorization to use these product names, trademarks, branding, interface elements, screenshots, layouts, graphics, and other protected material. Some listings may contain a non-affiliation statement, but this appears only at the end of the description, after the customer has already seen the app name, icon, screenshots, branding, and official-looking UI. In my view, a statement buried at the end of the description does not remove the misleading impression created by the rest of the listing. Many customers make download decisions from search results, titles, icons, screenshots, and the first part of a description. Apple should therefore review the complete presentation rather than treating an end-of-description disclaimer as sufficient where the rest of the listing may strongly imply official affiliation. This also appears to be a systematic developer-account-level pattern. The same seller has published at least nine apps targeting unrelated major brands operated by different companies, including Microsoft/LinkedIn, Zoom, Google, Amazon/Twitch, X Corp., ByteDance/TikTok, and Meta. The repeated strategy appears very similar across the portfolio: use the established service name, present the product as a dedicated desktop app, and reproduce or closely resemble the official interface and visual identity. Because the same pattern is repeated across many unrelated brands, I ask Apple to investigate the entire developer account rather than reviewing each listing in isolation. I believe these apps warrant investigation under App Review Guideline 4.1 — Copycats, as well as any applicable rules concerning intellectual property, misleading metadata, impersonation, trademark use, spam, and developer conduct. Please investigate whether: the apps impersonate or closely imitate established services; another company’s brand or product name is being used without authorization; the UI substantially reproduces the official product experience; App Store screenshots reproduce or closely imitate official interfaces; users could reasonably mistake these apps for official or authorized products; the developer has permission from each affected company; protected trademarks, graphics, layouts, screenshots, or visual assets are being used without authorization; this represents repeated copycat or misleading behavior across one developer account; the overall presentation is designed to benefit from confusion with established brands. I respectfully request that Apple App Review, Trust & Safety, and the appropriate Developer Program enforcement team conduct a full investigation of this developer account and all associated apps. Please review the actual installed applications, not only the written descriptions. The UI, screenshots, naming, branding, and full customer experience are important when determining whether these apps are misleading or impersonating legitimate services. Apple should also require the developer to demonstrate valid authorization from the companies whose names, products, and visual identities are being used. If Apple determines that these apps involve unauthorized brand use, repeated impersonation, copycat behavior, misleading presentation, intellectual-property misuse, or other Developer Program violations, I request removal of the affected applications and appropriate account-level enforcement, including termination of the Apple Developer Program account if warranted. This appears to be a repeated pattern involving multiple major brands, not an isolated naming mistake. I therefore ask Apple to investigate the complete developer portfolio and take appropriate action to protect Mac App Store users and preserve trust in App Store search results and developer identity.

Hi everyone, I’m a developer maintaining an existing app that has been live on the App Store for many years. We regularly submit updates, and normally our submissions are reviewed and approved within 48 hours without any issues. However, I’m currently experiencing an unusual situation and would appreciate some advice. 19 August: I submitted a new version of the app. It went into review but was rejected under: Guideline 1.1 - Safety - Objectionable Content The app’s marketing includes terms or images that reference objectionable content or services. These references can be found in the app’s metadata, including, but not limited to, the following metadata field(s): description and name. I’m not sure what triggered this rejection because the app name and description have not been changed for years. The app has been live and regularly reviewed during that time without this issue. The rejection also did not identify the specific wording or content in the app name or description that was considered objectionable. I responded to the review team explaining the situation and asked them to identify the specific part of the metadata that caused the issue so that we could review and update it if necessary. However, I did not receive any further response. I also submitted an appeal, but I have not received a response after several days. 21 August: Because we still need to maintain the app and release updates, I cancelled the previous submission and submitted a new version for review. However, this submission has also remained pending and has not moved forward to review. 25 August: I cancelled the submission again and created another submission containing both maintenance updates and a big launch for a new country. This update is important for our business because the new operation is scheduled to launch on 1 September. We need the app update to be reviewed and approved before then. I have also submitted an expedited review request and a new ticket, but it still hasn’t moved forward or been reviewed. My questions Is there anything I can do to get the current submission reviewed, given that the previous submission was rejected and the appeal has not received a response? Could the previous Guideline 1.1 rejection be causing the subsequent submissions to remain pending? Should I continue waiting for the current submission, or is there another recommended process for escalating this situation? The delay is now becoming critical because the new country launch is scheduled for 1 September, and not having the required app update available by then would significantly affect our business operations. Any advice from other developers who have experienced a similar situation would be greatly appreciated. Thank you.