@forvibe/cli 1.1.1 → 2.0.0

package/dist/review/rag-data/design.json

@@ -1,212 +0,0 @@
-[
-  {
-    "id": "webview-wrapper-app-no-native",
-    "guidelineNumber": "4.2",
-    "guidelineName": "Minimum Functionality",
-    "category": "design",
-    "rejectionReason": "Your app is primarily a repackaged website using a web view, without sufficient native iOS functionality.",
-    "whatDeveloperDid": "Submitted an app that was essentially a WKWebView loading the company's responsive website. The app had no native UI elements, no offline functionality, no push notifications, and no device-specific features. It was indistinguishable from visiting the website in Safari.",
-    "whatAppleSaid": "Guideline 4.2 - Design - Minimum Functionality: Your app is essentially a repackaged version of your website. We encourage you to review your app concept and incorporate native iOS features and functionality. Apps that are simply web views of a website are not appropriate for the App Store. Consider using Safari or creating a Home Screen bookmark instead.",
-    "fix": "Added native iOS features: push notifications for order updates, Face ID authentication, native navigation with tab bar, offline caching of key content, Haptic feedback on interactions, widgets for quick access, and Shortcuts integration. Converted critical screens (login, checkout, profile) to native SwiftUI views.",
-    "outcome": "approved-after-fix",
-    "keywords": ["webview", "wrapper", "wkwebview", "website", "minimum-functionality", "native-features"],
-    "behavioralSignals": ["entire app is a web view", "no native UI elements", "identical to mobile website", "no offline capability", "no device-specific features"],
-    "year": 2024
-  },
-  {
-    "id": "church-info-app-static-content",
-    "guidelineNumber": "4.2",
-    "guidelineName": "Minimum Functionality",
-    "category": "design",
-    "rejectionReason": "Your app provides only static information that would be better suited as a website.",
-    "whatDeveloperDid": "Created a church information app that displayed static content: service times, address, staff directory, and a few pages of text about the church. No dynamic features, no community interaction, no event calendar updates, and no push notifications.",
-    "whatAppleSaid": "Guideline 4.2 - Design - Minimum Functionality: Your app provides limited functionality that could be accomplished with a website. The static information displayed (service times, address, staff bios) does not provide a compelling native app experience. We encourage you to add features that take advantage of the device's capabilities.",
-    "fix": "Added dynamic features: live-updating event calendar with push notification reminders, sermon audio/video streaming with offline downloads, community prayer request board (with UGC moderation), in-app giving via IAP, location-based check-in, and an interactive Bible study feature with notes.",
-    "outcome": "approved-after-fix",
-    "keywords": ["minimum-functionality", "static-content", "church-app", "information-only", "limited-features"],
-    "behavioralSignals": ["only static text pages", "no dynamic content", "information-only app", "no interactive features", "could be a website"],
-    "year": 2023
-  },
-  {
-    "id": "ionic-react-native-too-web-like",
-    "guidelineNumber": "4.2",
-    "guidelineName": "Minimum Functionality",
-    "category": "design",
-    "rejectionReason": "Your app's user interface appears to be a web-based experience that does not follow iOS design conventions.",
-    "whatDeveloperDid": "Built an app using Ionic/React Native that retained many web-like UI patterns: browser-style back buttons, web-style dropdown selects, non-native scrolling behavior, text inputs without iOS keyboard accessories, and hamburger menu instead of tab bar navigation.",
-    "whatAppleSaid": "Guideline 4.2 - Design - Minimum Functionality: Your app's user interface does not provide an experience that is consistent with the quality and design expectations of the App Store. The app appears to use web-based UI components that do not conform to iOS Human Interface Guidelines. Please review the iOS Human Interface Guidelines and ensure your app provides a native-quality experience.",
-    "fix": "Replaced web-style components with native-looking equivalents: used bottom tab navigation instead of hamburger menu, native-style action sheets instead of web dropdowns, proper iOS navigation bar with back chevron, native scrolling with rubber-banding, and iOS-style form inputs with proper keyboard handling.",
-    "outcome": "approved-after-fix",
-    "keywords": ["hybrid-app", "ionic", "react-native", "web-like", "ui-quality", "native-experience"],
-    "behavioralSignals": ["web-style UI components", "hamburger menu navigation", "non-native scrolling", "browser-style controls", "web dropdown selects"],
-    "year": 2023
-  },
-  {
-    "id": "spam-duplicate-app-rxmarbles",
-    "guidelineNumber": "4.3",
-    "guidelineName": "Spam",
-    "category": "design",
-    "rejectionReason": "Your app is a duplicate of another app and does not provide a unique experience.",
-    "whatDeveloperDid": "Submitted an app that was a fork of the open-source RxMarbles app with the same binary, same functionality, and only cosmetic changes (icon color). The app was submitted from a different developer account than the original.",
-    "whatAppleSaid": "Guideline 4.3 - Design - Spam: Your app duplicates the content and functionality of another app already on the App Store (RxMarbles). Submitting multiple similar apps or copycat versions of popular apps is considered spam. Please ensure your app provides a unique, innovative experience.",
-    "fix": "This rejection is not easily fixable since the app was fundamentally a duplicate. The developer would need to create a genuinely unique app with different functionality and value proposition. Simply changing the skin or branding of an existing app is insufficient.",
-    "outcome": "rejected-permanently",
-    "keywords": ["spam", "duplicate", "copycat", "fork", "clone", "same-binary"],
-    "behavioralSignals": ["identical functionality to existing app", "same binary different account", "fork of open-source app", "only cosmetic differences"],
-    "year": 2020
-  },
-  {
-    "id": "sora-copycat-clones-removed",
-    "guidelineNumber": "4.3",
-    "guidelineName": "Spam",
-    "category": "design",
-    "rejectionReason": "Your app impersonates or copies another developer's app or service.",
-    "whatDeveloperDid": "After OpenAI announced Sora (AI video generation), dozens of copycat apps appeared on the App Store with names like 'Sora 2 AI Video', 'Sora Video Generator Pro', and similar variations. These apps used the Sora name and branding to mislead users, often charging subscriptions for unrelated or non-functional AI services.",
-    "whatAppleSaid": "Guideline 4.3 - Design - Spam: Your app appears to impersonate or misleadingly suggest an affiliation with another developer's product (Sora/OpenAI). Apps that copy the name, branding, or concept of another product to mislead users are not permitted on the App Store.",
-    "fix": "These apps were removed from the App Store. Apple conducted a mass removal of Sora copycat apps. Developers of legitimate AI video tools need to use original branding that does not suggest affiliation with OpenAI or Sora.",
-    "outcome": "rejected-permanently",
-    "keywords": ["copycat", "impersonation", "sora", "clone", "misleading", "brand-infringement"],
-    "behavioralSignals": ["uses another product's name", "misleading branding", "suggests false affiliation", "copies popular product"],
-    "year": 2024
-  },
-  {
-    "id": "android-style-buttons-ui",
-    "guidelineNumber": "4.1",
-    "guidelineName": "Copycats",
-    "category": "design",
-    "rejectionReason": "Your app's UI elements are inconsistent with iOS design patterns and appear to follow Android design conventions.",
-    "whatDeveloperDid": "Ported an Android app to iOS but kept Android-style Material Design UI elements: floating action buttons (FAB), Android-style bottom sheets, Material Design text fields with floating labels, three-dot overflow menus, and Android-style toggle switches.",
-    "whatAppleSaid": "Guideline 4.0 - Design: Your app's user interface does not follow iOS design conventions. Several UI elements appear to be designed for another platform. Please review the iOS Human Interface Guidelines and update your app's interface to provide an experience consistent with the iOS platform.",
-    "fix": "Replaced Android-style UI elements with iOS equivalents: FAB became a navigation bar '+' button, Material bottom sheets became iOS sheet presentations, floating label text fields became standard iOS text fields, three-dot menus became iOS ellipsis menus or swipe actions, and toggle switches were replaced with UISwitch.",
-    "outcome": "approved-after-fix",
-    "keywords": ["android-ui", "material-design", "platform-consistency", "ios-guidelines", "ui-elements"],
-    "behavioralSignals": ["floating action button", "Material Design components", "Android-style navigation", "non-iOS toggle switches", "three-dot overflow menu"],
-    "year": 2022
-  },
-  {
-    "id": "sign-in-with-apple-missing",
-    "guidelineNumber": "4.8",
-    "guidelineName": "Sign in with Apple",
-    "category": "design",
-    "rejectionReason": "Your app uses third-party social login but does not offer Sign in with Apple as an option.",
-    "whatDeveloperDid": "Implemented Google Sign-In and Facebook Login as authentication options but did not include Sign in with Apple. Since June 2020, apps that offer third-party social login must also offer Sign in with Apple as an equivalent option.",
-    "whatAppleSaid": "Guideline 4.8 - Design - Sign in with Apple: Your app uses third-party login services (Google, Facebook) but does not offer Sign in with Apple. Apps that use a third-party or social login service to set up or authenticate the user's primary account must also offer Sign in with Apple as an equivalent option.",
-    "fix": "Added Sign in with Apple as a login option alongside Google and Facebook. Implemented the AuthenticationServices framework with ASAuthorizationAppleIDProvider. Ensured the Sign in with Apple button is displayed with equal prominence to other login options.",
-    "outcome": "approved-after-fix",
-    "keywords": ["sign-in-with-apple", "social-login", "authentication", "google-login", "facebook-login"],
-    "behavioralSignals": ["Google/Facebook login without Apple login", "third-party login without SIWA", "missing Sign in with Apple button", "social login options incomplete"],
-    "year": 2023
-  },
-  {
-    "id": "sign-in-with-apple-wrong-style",
-    "guidelineNumber": "4.8",
-    "guidelineName": "Sign in with Apple",
-    "category": "design",
-    "rejectionReason": "Your Sign in with Apple button does not follow Apple's Human Interface Guidelines for button styling.",
-    "whatDeveloperDid": "Implemented Sign in with Apple but used a custom-styled button that didn't match Apple's required design specifications. The button was too small, used a custom font, had rounded corners that didn't match the spec, and was placed below other login options in a smaller size.",
-    "whatAppleSaid": "Guideline 4.8 - Design - Sign in with Apple: Your Sign in with Apple button does not conform to the required design specifications. The button must use Apple's provided styles (ASAuthorizationAppleIDButton), be at least the same size as other login buttons, and follow the Human Interface Guidelines for Sign in with Apple button design.",
-    "fix": "Replaced the custom button with Apple's native ASAuthorizationAppleIDButton, which automatically handles correct styling, sizing, and localization. Ensured the button is the same size or larger than other login buttons and is positioned with equal prominence on the login screen.",
-    "outcome": "approved-after-fix",
-    "keywords": ["sign-in-with-apple", "button-style", "hig", "design-guidelines", "authentication"],
-    "behavioralSignals": ["custom SIWA button", "undersized Apple login button", "non-standard button styling", "Apple login less prominent than others"],
-    "year": 2022
-  },
-  {
-    "id": "apple-ip-springboard-image",
-    "guidelineNumber": "4.5.3",
-    "guidelineName": "Apple Trademarks and IP",
-    "category": "design",
-    "rejectionReason": "Your app uses Apple's copyrighted imagery without authorization.",
-    "whatDeveloperDid": "Used a screenshot of the iOS home screen (SpringBoard) as a background image in the app's onboarding tutorial. The screenshot included Apple's copyrighted wallpaper, app icons, and the dock design.",
-    "whatAppleSaid": "Guideline 4.5.3 - Design - Apple Trademarks: Your app uses Apple's copyrighted material (iOS home screen screenshot including SpringBoard interface and Apple app icons). You may not use Apple-owned images, icons, or screenshots of Apple software in your app without explicit permission.",
-    "fix": "Replaced the iOS home screen screenshot with a custom-designed illustration that conveys the same tutorial concept without using Apple's copyrighted imagery. Used generic device mockups from Apple's official marketing resources (which are permitted for certain uses) or created original artwork.",
-    "outcome": "approved-after-fix",
-    "keywords": ["apple-ip", "trademark", "copyright", "springboard", "home-screen", "apple-images"],
-    "behavioralSignals": ["iOS home screen screenshot in app", "Apple wallpaper used", "Apple app icons displayed", "copyrighted Apple UI elements"],
-    "year": 2022
-  },
-  {
-    "id": "app-too-similar-built-in-app",
-    "guidelineNumber": "4.2",
-    "guidelineName": "Minimum Functionality",
-    "category": "design",
-    "rejectionReason": "Your app provides functionality that is too similar to built-in iOS apps without providing additional unique value.",
-    "whatDeveloperDid": "Created a simple calculator app and a flashlight app that replicated the exact functionality of iOS built-in apps without any additional features, customization options, or unique value proposition.",
-    "whatAppleSaid": "Guideline 4.2 - Design - Minimum Functionality: Your app replicates the functionality of a built-in iOS app (Calculator/Flashlight) without providing additional unique value. Simple utility apps that duplicate built-in capabilities are not appropriate for the App Store unless they offer significant additional functionality.",
-    "fix": "For the calculator: added scientific calculator mode, unit conversion, calculation history, custom themes, and a widget. For the flashlight: added SOS mode, color filters, strobe patterns, screen color options, and an ambient light meter. The apps now offer meaningful functionality beyond the built-in equivalents.",
-    "outcome": "approved-after-fix",
-    "keywords": ["built-in-app", "calculator", "flashlight", "duplicate-functionality", "minimum-value"],
-    "behavioralSignals": ["replicates built-in app", "no features beyond system app", "basic utility clone", "no unique value proposition"],
-    "year": 2021
-  },
-  {
-    "id": "simple-app-not-unique",
-    "guidelineNumber": "4.2",
-    "guidelineName": "Minimum Functionality",
-    "category": "design",
-    "rejectionReason": "Your app does not provide a unique or innovative experience and lacks sufficient functionality.",
-    "whatDeveloperDid": "Submitted a very simple app with a single screen that performed one basic function (e.g., a tip calculator with just a percentage slider and total display) without any additional features, customization, or polish.",
-    "whatAppleSaid": "Guideline 4.2 - Design - Minimum Functionality: Your app does not include sufficient content or functionality to provide a compelling App Store experience. We encourage you to review your app concept and add more features and content to provide value to users.",
-    "fix": "Expanded the app with multiple features: bill splitting, custom tip presets, receipt scanning, expense history, group dining calculations, Apple Watch companion, and widgets. The app evolved from a single-function utility to a comprehensive dining expense tool.",
-    "outcome": "approved-after-fix",
-    "keywords": ["minimum-functionality", "simple-app", "insufficient-features", "single-function", "not-unique"],
-    "behavioralSignals": ["single-screen app", "one basic function", "no settings or customization", "minimal feature set"],
-    "year": 2023
-  },
-  {
-    "id": "ui-elements-too-small",
-    "guidelineNumber": "4.0",
-    "guidelineName": "Design",
-    "category": "design",
-    "rejectionReason": "Your app's interactive elements are too small for comfortable touch interaction.",
-    "whatDeveloperDid": "Designed an app with very small buttons (less than 44x44 points), tiny text (below 11pt), and densely packed interactive elements that were difficult to tap accurately on iPhone screens.",
-    "whatAppleSaid": "Guideline 4.0 - Design: Your app includes interactive elements that are too small for reliable touch interaction. Per Human Interface Guidelines, tappable elements should have a minimum target size of 44x44 points. Several buttons and links in your app are significantly below this minimum.",
-    "fix": "Increased all tappable elements to at least 44x44 points. Increased body text to at least 13pt and added Dynamic Type support. Added proper spacing between interactive elements. Tested on the smallest supported iPhone screen size to ensure all elements are comfortably tappable.",
-    "outcome": "approved-after-fix",
-    "keywords": ["touch-targets", "small-buttons", "accessibility", "ui-size", "hig", "readability"],
-    "behavioralSignals": ["tiny buttons", "small text", "densely packed UI", "hard to tap elements", "poor readability"],
-    "year": 2023
-  },
-  {
-    "id": "missing-localization-launch-images",
-    "guidelineNumber": "4.0",
-    "guidelineName": "Design",
-    "category": "design",
-    "rejectionReason": "Your app's launch screen displays content in a different language than the app's primary localization.",
-    "whatDeveloperDid": "Created a Japanese-language app but the LaunchScreen.storyboard contained English text ('Loading...', company name in English). The launch screen language didn't match the app's primary language, creating an inconsistent first impression.",
-    "whatAppleSaid": "Guideline 4.0 - Design: Your app's launch screen contains text in English, but the app's primary language is Japanese. The launch screen should be consistent with the app's primary language and localization.",
-    "fix": "Localized the LaunchScreen.storyboard to display Japanese text. Best practice: use a minimal launch screen with just the app logo/icon without text to avoid localization issues entirely, matching Apple's own app launch screens.",
-    "outcome": "approved-after-fix",
-    "keywords": ["localization", "launch-screen", "language-mismatch", "internationalization", "storyboard"],
-    "behavioralSignals": ["launch screen in wrong language", "English text in localized app", "language inconsistency on launch"],
-    "year": 2022
-  },
-  {
-    "id": "macos-window-management-no-reopen",
-    "guidelineNumber": "4.0",
-    "guidelineName": "Design",
-    "category": "design",
-    "rejectionReason": "Your macOS app does not properly handle window management. Closing all windows provides no way to create a new window.",
-    "whatDeveloperDid": "Built a macOS Catalyst or native macOS app that, when the user closed all windows, had no File > New Window menu item and no dock icon click handler to reopen the main window. The app was running but had no visible UI and no way to get back to it.",
-    "whatAppleSaid": "Guideline 4.0 - Design: Your macOS app does not properly handle window management. After closing the app's window, there is no menu option to reopen or create a new window. Users expect to be able to click the dock icon or use the File menu to access the app again.",
-    "fix": "Implemented applicationShouldHandleReopen(_:hasVisibleWindows:) delegate method to show the main window when the dock icon is clicked. Added File > New Window menu item. Ensured the app activates and shows the main window when launched via Spotlight or dock.",
-    "outcome": "approved-after-fix",
-    "keywords": ["macos", "window-management", "dock", "menu-bar", "catalyst", "reopen"],
-    "behavioralSignals": ["no way to reopen window", "closing window loses app", "missing File menu items", "dock click does nothing"],
-    "year": 2023
-  },
-  {
-    "id": "clunky-ui-spelling-grammar-errors",
-    "guidelineNumber": "4.0",
-    "guidelineName": "Design",
-    "category": "design",
-    "rejectionReason": "Your app's interface has significant quality issues including spelling errors, grammar mistakes, and unpolished UI elements.",
-    "whatDeveloperDid": "Submitted an app with multiple spelling errors in button labels and navigation titles, grammatically incorrect alert messages, inconsistent font sizes, misaligned UI elements, and truncated text that made the app feel unfinished and unprofessional.",
-    "whatAppleSaid": "Guideline 4.0 - Design: Your app's user interface has quality issues that affect the user experience. We found multiple spelling errors ('Settigns', 'Purchse'), grammatically incorrect messages, truncated labels, and misaligned elements. Please polish your app's interface before resubmitting.",
-    "fix": "Conducted a thorough UI review: fixed all spelling and grammar errors, ensured consistent typography, fixed all layout and alignment issues, tested on all screen sizes to prevent truncation, and had a native speaker review all user-facing text.",
-    "outcome": "approved-after-fix",
-    "keywords": ["ui-quality", "spelling-errors", "grammar", "polish", "unfinished", "typography"],
-    "behavioralSignals": ["spelling errors in buttons", "grammar mistakes in alerts", "truncated text", "misaligned elements", "inconsistent fonts"],
-    "year": 2023
-  }
-]

package/dist/review/rag-data/legal.json

@@ -1,212 +0,0 @@
-[
-  {
-    "id": "missing-privacy-info-xcprivacy",
-    "guidelineNumber": "5.1.2",
-    "guidelineName": "Data Use and Sharing - Required Reason APIs",
-    "category": "legal",
-    "rejectionReason": "Your app does not include the required PrivacyInfo.xcprivacy manifest file.",
-    "whatDeveloperDid": "Submitted an app without the PrivacyInfo.xcprivacy file, which became mandatory for all apps submitted after February 2025. The app used Required Reason APIs (UserDefaults, file timestamp access, disk space) without declaring the reasons in a privacy manifest.",
-    "whatAppleSaid": "ITMS-91053: Missing API declaration - Your app's code in the binary references one or more APIs that require reasons. Starting February 2025, all apps must include a PrivacyInfo.xcprivacy file that declares the reasons for using Required Reason APIs. Please add the privacy manifest to your app.",
-    "fix": "Created a PrivacyInfo.xcprivacy file and added it to the app target's Build Phases > Copy Bundle Resources. Declared all Required Reason API usages with their approved reasons (e.g., NSPrivacyAccessedAPICategoryUserDefaults with reason 'CA92.1' for app functionality). Also ensured all third-party SDKs included their own privacy manifests.",
-    "outcome": "approved-after-fix",
-    "keywords": ["privacy-manifest", "xcprivacy", "required-reason-api", "privacy-info", "itms-91053"],
-    "behavioralSignals": ["missing PrivacyInfo.xcprivacy", "Required Reason API usage without manifest", "ITMS-91053 error on upload", "no privacy declarations"],
-    "year": 2025
-  },
-  {
-    "id": "privacy-manifest-not-in-build-phases",
-    "guidelineNumber": "5.1.2",
-    "guidelineName": "Data Use and Sharing - Required Reason APIs",
-    "category": "legal",
-    "rejectionReason": "Your PrivacyInfo.xcprivacy file exists in the project but is not included in the app bundle.",
-    "whatDeveloperDid": "Created the PrivacyInfo.xcprivacy file and added it to the Xcode project, but forgot to add it to the target's Build Phases > Copy Bundle Resources. The file existed in the project navigator but was not included in the compiled app bundle.",
-    "whatAppleSaid": "ITMS-91053: Missing API declaration - Your app references Required Reason APIs but the privacy manifest was not found in the app bundle. Please ensure the PrivacyInfo.xcprivacy file is included in your app's Copy Bundle Resources build phase.",
-    "fix": "Added the PrivacyInfo.xcprivacy file to the correct target's Build Phases > Copy Bundle Resources. Verified it was included in the bundle by inspecting the .ipa contents. For frameworks and Swift packages, ensured each target has its own privacy manifest included in the correct location.",
-    "outcome": "approved-after-fix",
-    "keywords": ["privacy-manifest", "build-phases", "bundle-resources", "xcprivacy", "copy-resources"],
-    "behavioralSignals": ["PrivacyInfo.xcprivacy in project but not bundle", "file not in Copy Bundle Resources", "manifest exists but not bundled", "ITMS-91053 despite having file"],
-    "year": 2025
-  },
-  {
-    "id": "account-deletion-missing",
-    "guidelineNumber": "5.1.1",
-    "guidelineName": "Data Collection and Storage - Account Deletion",
-    "category": "legal",
-    "rejectionReason": "Your app supports account creation but does not offer account deletion.",
-    "whatDeveloperDid": "Built an app with user registration and login but did not provide any way for users to delete their account and associated data from within the app. Users had to email support to request account deletion.",
-    "whatAppleSaid": "Guideline 5.1.1(v) - Legal - Privacy - Data Collection and Storage: Apps that support account creation must also offer account deletion. Your app allows users to create an account but does not provide the ability to delete the account within the app. The account deletion option must be easy to find and must initiate deletion of the account and all associated personal data.",
-    "fix": "Added an 'Delete Account' option in Settings > Account. The deletion flow includes a confirmation dialog explaining what data will be deleted, a re-authentication step for security, and an optional reason selector. Account and all associated data are deleted within 14 days as per Apple's requirements. Also added the AccountDeletionURL in App Store Connect.",
-    "outcome": "approved-after-fix",
-    "keywords": ["account-deletion", "privacy", "data-deletion", "user-account", "gdpr", "5.1.1"],
-    "behavioralSignals": ["no delete account option", "account creation without deletion", "must email support to delete", "no in-app account removal"],
-    "year": 2023
-  },
-  {
-    "id": "att-permission-not-appearing-ipad",
-    "guidelineNumber": "5.1.2",
-    "guidelineName": "Data Use and Sharing",
-    "category": "legal",
-    "rejectionReason": "The App Tracking Transparency prompt does not appear on iPad during review.",
-    "whatDeveloperDid": "Implemented ATT (App Tracking Transparency) permission request, but it only appeared on iPhone. On iPad, the ATT prompt never showed because the app was checking for IDFA availability using an older API that returned different results on iPad, or the prompt was being called before the app was in the active state on iPad.",
-    "whatAppleSaid": "Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing: We noticed that your app does not display the App Tracking Transparency permission prompt on iPad. The app appears to collect tracking data without requesting user permission. Please ensure the ATT prompt appears on all supported device types.",
-    "fix": "Ensured the ATT prompt is called after the app reaches the active state using applicationDidBecomeActive or sceneDidBecomeActive. Added a delay to ensure the UI is fully loaded before presenting the prompt. Tested on both iPhone and iPad to verify the prompt appears correctly on all devices.",
-    "outcome": "approved-after-fix",
-    "keywords": ["att", "tracking-transparency", "ipad", "idfa", "permission-prompt", "tracking"],
-    "behavioralSignals": ["ATT prompt missing on iPad", "tracking without permission on iPad", "IDFA access without consent", "prompt only shows on iPhone"],
-    "year": 2023
-  },
-  {
-    "id": "att-timing-must-be-active",
-    "guidelineNumber": "5.1.2",
-    "guidelineName": "Data Use and Sharing",
-    "category": "legal",
-    "rejectionReason": "The App Tracking Transparency prompt is called at an inappropriate time and does not display.",
-    "whatDeveloperDid": "Called requestTrackingAuthorization() in application(_:didFinishLaunchingWithOptions:) or during a scene transition, before the app was fully in the foreground active state. The system silently dropped the ATT prompt because the app wasn't yet active.",
-    "whatAppleSaid": "Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing: The App Tracking Transparency prompt does not appear when your app is launched. The ATT prompt must be displayed while the app is in the active state. Please ensure you request tracking authorization at an appropriate time after the app has become active.",
-    "fix": "Moved the ATT permission request to trigger after the app is fully active and visible. Used a slight delay (e.g., DispatchQueue.main.asyncAfter(deadline: .now() + 1.0)) after applicationDidBecomeActive to ensure the app is ready. Showed the prompt on a meaningful screen (e.g., after onboarding) rather than immediately on launch.",
-    "outcome": "approved-after-fix",
-    "keywords": ["att", "tracking-transparency", "timing", "app-active", "permission-prompt", "idfa"],
-    "behavioralSignals": ["ATT prompt not showing", "permission requested too early", "prompt called before app active", "tracking authorization fails silently"],
-    "year": 2022
-  },
-  {
-    "id": "multiple-permissions-blocking-att",
-    "guidelineNumber": "5.1.2",
-    "guidelineName": "Data Use and Sharing",
-    "category": "legal",
-    "rejectionReason": "The App Tracking Transparency prompt is blocked by other permission dialogs.",
-    "whatDeveloperDid": "Requested multiple permissions simultaneously on app launch: notifications, location, camera, and ATT. The system queued these permission dialogs, and on some devices/OS versions the ATT prompt was blocked or dismissed by other permission alerts appearing over it.",
-    "whatAppleSaid": "Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing: We were unable to see the App Tracking Transparency prompt during our review. It appears that other permission requests may be interfering with the ATT prompt display. Please ensure the ATT prompt is displayed without interference from other system dialogs.",
-    "fix": "Implemented a sequential permission request flow that spaces out permission prompts. Request permissions one at a time with appropriate delays between each. Show the ATT prompt on its own screen without other system dialogs. Used a permission queue manager to ensure only one system alert is presented at a time.",
-    "outcome": "approved-after-fix",
-    "keywords": ["att", "permission-conflicts", "multiple-permissions", "dialog-blocking", "permission-queue"],
-    "behavioralSignals": ["multiple permission popups at once", "ATT blocked by other alerts", "permission dialogs overlapping", "simultaneous permission requests"],
-    "year": 2023
-  },
-  {
-    "id": "adjust-sdk-fingerprinting-rejection",
-    "guidelineNumber": "5.1.2",
-    "guidelineName": "Data Use and Sharing",
-    "category": "legal",
-    "rejectionReason": "Your app uses a third-party SDK (Adjust) that performs device fingerprinting for tracking purposes.",
-    "whatDeveloperDid": "Used the Adjust SDK for attribution tracking. An older version of the SDK performed device fingerprinting (collecting device model, OS version, IP address, locale, and other signals to create a unique identifier) as a fallback when IDFA was unavailable, violating Apple's anti-tracking policies.",
-    "whatAppleSaid": "Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing: Your app includes a third-party SDK (Adjust) that collects device and usage data to create a unique identifier for tracking purposes (fingerprinting). Fingerprinting is not permitted regardless of whether the user has granted tracking permission. Over 50,000 apps were affected by this enforcement action.",
-    "fix": "Updated the Adjust SDK to the latest version that complies with Apple's anti-fingerprinting requirements. The updated SDK removes fingerprinting fallback mechanisms and relies solely on ATT-consented IDFA or Apple's SKAdNetwork for attribution. Verified with Adjust's compliance documentation.",
-    "outcome": "approved-after-fix",
-    "keywords": ["adjust", "fingerprinting", "attribution", "tracking", "sdk", "device-fingerprint"],
-    "behavioralSignals": ["Adjust SDK fingerprinting", "device identification without consent", "attribution tracking via fingerprint", "outdated tracking SDK"],
-    "year": 2024
-  },
-  {
-    "id": "vague-photo-permission-description",
-    "guidelineNumber": "5.1.1",
-    "guidelineName": "Data Collection and Storage",
-    "category": "legal",
-    "rejectionReason": "Your app's photo library permission description does not adequately explain why the app needs access.",
-    "whatDeveloperDid": "Set the NSPhotoLibraryUsageDescription to a vague message like 'App requires photo access to function' or 'This app needs your photos' without explaining specifically why the app needs photo library access and how the photos would be used.",
-    "whatAppleSaid": "Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage: Your app's permission request descriptions are not sufficiently descriptive. The purpose string for photo library access ('App requires photo access to function') does not clearly explain to users why the app needs this access. Please provide a specific, clear description of how the app uses the photo library.",
-    "fix": "Updated NSPhotoLibraryUsageDescription to a specific, clear description: 'YourApp needs access to your photo library to let you select photos for your profile picture and share images in chat conversations.' The description now explains exactly what the photos are used for.",
-    "outcome": "approved-after-fix",
-    "keywords": ["permission-description", "photo-library", "purpose-string", "privacy", "usage-description"],
-    "behavioralSignals": ["vague permission popup text", "generic photo access reason", "unclear usage description", "non-descriptive purpose string"],
-    "year": 2023
-  },
-  {
-    "id": "missing-photo-permission-third-party-sdk",
-    "guidelineNumber": "5.1.1",
-    "guidelineName": "Data Collection and Storage",
-    "category": "legal",
-    "rejectionReason": "Your app accesses the photo library without including the required NSPhotoLibraryUsageDescription.",
-    "whatDeveloperDid": "The app's own code didn't access the photo library, but a third-party SDK (e.g., an image picker library, chat SDK, or analytics SDK with screenshot detection) included photo library access APIs. The developer didn't add NSPhotoLibraryUsageDescription to Info.plist because they were unaware the SDK accessed photos.",
-    "whatAppleSaid": "ITMS-90683: Missing Purpose String in Info.plist - Your app's code references the photo library API but the corresponding purpose string (NSPhotoLibraryUsageDescription) is not present in the Info.plist. All apps that access the photo library must include a purpose string explaining the use.",
-    "fix": "Added NSPhotoLibraryUsageDescription to Info.plist with a clear description of how the third-party SDK uses photo access. Audited all third-party SDKs for permission requirements and ensured all required usage descriptions are present. Alternatively, if the photo access was unnecessary, configured the SDK to disable that feature or switched to an SDK that doesn't require photo access.",
-    "outcome": "approved-after-fix",
-    "keywords": ["photo-permission", "third-party-sdk", "info-plist", "usage-description", "missing-permission"],
-    "behavioralSignals": ["ITMS-90683 error", "SDK requires photo access", "missing Info.plist key", "unknown permission requirement from SDK"],
-    "year": 2023
-  },
-  {
-    "id": "vpn-app-content-blocking-rejection",
-    "guidelineNumber": "5.4",
-    "guidelineName": "VPN Apps",
-    "category": "legal",
-    "rejectionReason": "Your VPN app uses the VPN capability primarily for content blocking or ad blocking rather than providing a VPN service.",
-    "whatDeveloperDid": "Created an app that used the Network Extension VPN entitlement primarily to block ads, trackers, and specific website content by routing traffic through a local VPN tunnel with DNS-level filtering. The app was marketed as an ad blocker rather than a VPN service.",
-    "whatAppleSaid": "Guideline 5.4 - Legal - VPN Apps: Your app uses the VPN capability for purposes other than providing a virtual private network service. Using the VPN entitlement primarily for content blocking, ad blocking, or traffic manipulation is not permitted. VPN apps must provide VPN service as their primary function.",
-    "fix": "Restructured the app to use Safari Content Blocker extension (Content Blocker API) for ad blocking instead of VPN-based filtering. For DNS-level filtering, used the DNSSettings configuration profile approach. Removed the VPN entitlement since the app's primary purpose was content blocking, not VPN.",
-    "outcome": "approved-after-fix",
-    "keywords": ["vpn", "ad-blocking", "content-blocking", "network-extension", "dns-filtering"],
-    "behavioralSignals": ["VPN used for ad blocking", "local VPN tunnel for filtering", "ad blocker using VPN entitlement", "content blocking via VPN"],
-    "year": 2023
-  },
-  {
-    "id": "privacy-policy-url-broken",
-    "guidelineNumber": "5.1.1",
-    "guidelineName": "Data Collection and Storage",
-    "category": "legal",
-    "rejectionReason": "Your app's privacy policy URL leads to a broken page or placeholder content.",
-    "whatDeveloperDid": "Provided a privacy policy URL in App Store Connect that returned a 404 error, was a placeholder page ('Coming Soon'), or redirected to the app's homepage without any privacy policy content.",
-    "whatAppleSaid": "Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage: The privacy policy URL provided for your app does not lead to a valid privacy policy. The URL returns a 404 error. All apps must provide a working privacy policy URL that is accessible to users.",
-    "fix": "Created a proper privacy policy page and hosted it at a stable, permanent URL. Ensured the URL is accessible, loads quickly, and contains a complete privacy policy. Updated the privacy policy URL in App Store Connect and within the app settings.",
-    "outcome": "approved-after-fix",
-    "keywords": ["privacy-policy", "broken-url", "404", "placeholder", "legal-requirement"],
-    "behavioralSignals": ["privacy policy URL returns 404", "placeholder privacy page", "broken link in App Store Connect", "privacy policy not accessible"],
-    "year": 2024
-  },
-  {
-    "id": "privacy-policy-missing-details",
-    "guidelineNumber": "5.1.1",
-    "guidelineName": "Data Collection and Storage",
-    "category": "legal",
-    "rejectionReason": "Your privacy policy does not adequately describe the data your app collects and how it is used.",
-    "whatDeveloperDid": "Provided a generic one-paragraph privacy policy that did not specify what data the app collects, how it's used, whether it's shared with third parties, data retention periods, or user rights regarding their data.",
-    "whatAppleSaid": "Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage: Your privacy policy does not adequately describe your app's data collection and usage practices. The privacy policy must clearly identify what data is collected, how it is used, when it is shared, and the data retention policy. Please update your privacy policy to include these details.",
-    "fix": "Rewrote the privacy policy to include: specific types of data collected (personal info, usage data, device info), purposes of data collection, third-party services and SDKs that receive data, data retention and deletion policies, user rights (access, correction, deletion), contact information for privacy inquiries, and effective date.",
-    "outcome": "approved-after-fix",
-    "keywords": ["privacy-policy", "data-collection", "disclosure", "transparency", "legal-compliance"],
-    "behavioralSignals": ["generic privacy policy", "missing data collection details", "no third-party disclosure", "vague privacy terms"],
-    "year": 2023
-  },
-  {
-    "id": "background-location-for-analytics",
-    "guidelineNumber": "5.1.2",
-    "guidelineName": "Data Use and Sharing",
-    "category": "legal",
-    "rejectionReason": "Your app accesses location data in the background for analytics purposes rather than a user-facing feature.",
-    "whatDeveloperDid": "Requested 'Always' location permission and tracked the user's location in the background to feed location data into an analytics platform for market research, without providing any user-facing feature that required background location.",
-    "whatAppleSaid": "Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing: Your app collects location data in the background for analytics and advertising purposes rather than providing a user-facing feature. Background location access must be tied to a feature that directly benefits the user. Using location for analytics or advertising is not a valid use of background location.",
-    "fix": "Removed background location tracking entirely. Downgraded to 'While Using' location permission. Location data is now only used for the app's core map feature while the user is actively using the app. Removed location data from the analytics pipeline.",
-    "outcome": "approved-after-fix",
-    "keywords": ["background-location", "analytics", "tracking", "location-permission", "privacy-violation"],
-    "behavioralSignals": ["background location for analytics", "Always location without user feature", "location tracking for market research", "no user-facing location feature"],
-    "year": 2023
-  },
-  {
-    "id": "clipboard-reading-without-user-intent",
-    "guidelineNumber": "5.1.1",
-    "guidelineName": "Data Collection and Storage",
-    "category": "legal",
-    "rejectionReason": "Your app reads clipboard contents without clear user intent or action.",
-    "whatDeveloperDid": "The app read the clipboard contents (UIPasteboard.general.string) on every app launch or foreground event to detect URLs, referral codes, or other content. Starting with iOS 16, users see a paste notification banner and starting with iOS 14, a paste indicator appears, making this behavior highly visible.",
-    "whatAppleSaid": "Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage: Your app reads the clipboard contents on launch without a clear user action or intent. Reading clipboard data should only occur in response to an explicit user action (e.g., tapping a paste button). Automatically reading the clipboard on app launch is not permitted.",
-    "fix": "Removed automatic clipboard reading on launch. Implemented a 'Paste' button that users can tap to voluntarily share clipboard contents. Used the new UIPasteboard.DetectionPattern API (iOS 14+) to detect if the clipboard contains relevant content (like URLs) without actually reading it, then show a prompt for the user to paste.",
-    "outcome": "approved-after-fix",
-    "keywords": ["clipboard", "pasteboard", "privacy", "user-intent", "paste-detection"],
-    "behavioralSignals": ["clipboard read on launch", "paste notification appearing", "automatic clipboard access", "UIPasteboard access without user action"],
-    "year": 2023
-  },
-  {
-    "id": "third-party-sdk-data-sharing-undisclosed",
-    "guidelineNumber": "5.1.2",
-    "guidelineName": "Data Use and Sharing",
-    "category": "legal",
-    "rejectionReason": "Your app shares user data with third-party SDKs that are not disclosed in your privacy nutrition labels.",
-    "whatDeveloperDid": "Integrated multiple third-party SDKs (analytics, advertising, crash reporting) that collected and shared user data, but did not disclose this data sharing in the App Privacy (nutrition label) section of App Store Connect. The privacy labels showed 'Data Not Collected' while SDKs were actively collecting and transmitting user data.",
-    "whatAppleSaid": "Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing: Your app's privacy information on the App Store does not accurately reflect your app's data collection and sharing practices. We identified third-party SDKs in your app that collect data not disclosed in your privacy nutrition labels. Please update your App Privacy information to accurately reflect all data collection.",
-    "fix": "Audited all third-party SDKs for data collection practices using each SDK's privacy documentation. Updated the App Privacy nutrition labels in App Store Connect to accurately reflect all data collected by the app and its SDKs, including the purpose of collection and whether it's linked to the user's identity.",
-    "outcome": "approved-after-fix",
-    "keywords": ["privacy-labels", "nutrition-label", "data-sharing", "third-party-sdk", "disclosure", "app-privacy"],
-    "behavioralSignals": ["privacy labels don't match SDK data collection", "undisclosed data sharing", "Data Not Collected but SDKs present", "inaccurate privacy nutrition labels"],
-    "year": 2024
-  }
-]