@forvibe/cli 1.1.0 → 2.0.0

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

@@ -1,282 +0,0 @@
-[
-  {
-    "id": "app-crash-during-review",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "We discovered one or more bugs in your app. Your app crashed during our review.",
-    "whatDeveloperDid": "Submitted an app that had a race condition in the initialization sequence. The app worked fine locally but crashed on first launch when network conditions were slower, which matched Apple's review environment.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: We discovered one or more bugs in your app when reviewed on iPhone 15 Pro running iOS 17.2. Specifically, the app crashed on launch. Please review the crash logs attached in the resolution center.",
-    "fix": "Analyzed the crash log from the resolution center. Found a force-unwrap on an optional that was nil when a network request hadn't completed before the UI tried to access the data. Added proper nil-checking and async/await handling for the initialization sequence. Tested on a clean install with network throttling enabled.",
-    "outcome": "approved-after-fix",
-    "keywords": ["crash", "bug", "launch-crash", "race-condition", "app-completeness"],
-    "behavioralSignals": ["app crashes on launch", "force-unwrap crash", "race condition on initialization", "works locally but crashes in review"],
-    "year": 2024
-  },
-  {
-    "id": "placeholder-lorem-ipsum-content",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app includes placeholder content. Apps should be complete and fully functional when submitted for review.",
-    "whatDeveloperDid": "Submitted an app where some secondary screens still contained 'Lorem ipsum' placeholder text, sample images, and TODO comments visible in the UI. The developer forgot to replace placeholder content before submission.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: Your app includes placeholder content that makes it appear as though the app is not yet complete. Specifically, we found Lorem ipsum text on the About page and placeholder images in the settings screen. Please complete all content before resubmitting.",
-    "fix": "Replaced all Lorem ipsum text with real content. Replaced placeholder images with production assets. Did a full audit of every screen to ensure no remaining placeholder content, TODO labels, or sample data was visible.",
-    "outcome": "approved-after-fix",
-    "keywords": ["placeholder", "lorem-ipsum", "incomplete", "sample-content", "app-completeness"],
-    "behavioralSignals": ["Lorem ipsum text visible", "placeholder images displayed", "TODO text in UI", "sample data on screen"],
-    "year": 2023
-  },
-  {
-    "id": "testflight-references-in-production",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app references TestFlight or beta testing in the production build.",
-    "whatDeveloperDid": "Left a 'Thank you for beta testing!' banner and a 'Report Beta Bug' button visible in the production build. The app also had a settings toggle labeled 'TestFlight Debug Mode' that was visible to all users.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: Your app contains references to TestFlight and beta testing, which is not appropriate for the production version of your app. Specifically, we found a 'Report Beta Bug' button and references to TestFlight in the settings. Please remove all beta-related content.",
-    "fix": "Wrapped all beta/TestFlight-related UI elements in compile-time flags (#if DEBUG) and runtime checks for TestFlight environment. Removed the beta testing banner and debug toggle from the production build configuration.",
-    "outcome": "approved-after-fix",
-    "keywords": ["testflight", "beta", "debug", "production-build", "beta-references"],
-    "behavioralSignals": ["TestFlight text visible", "beta testing UI elements", "debug mode toggle in settings", "Report Beta Bug button"],
-    "year": 2023
-  },
-  {
-    "id": "ipv6-hardcoded-addresses-failure",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app does not work on IPv6-only networks as required.",
-    "whatDeveloperDid": "Hardcoded IPv4 addresses for API server connections instead of using domain names. Apple's review network uses a NAT64/DNS64 environment (IPv6-only), causing all direct IPv4 connections to fail.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: We discovered one or more bugs in your app when reviewed on iPad running iOS 17.1 on an IPv6 network. Specifically, the app was unable to load content. Apps must support IPv6-only networking as many carrier networks are IPv6-only.",
-    "fix": "Replaced all hardcoded IPv4 addresses with domain name-based connections. Used NSURLSession/URLSession which handles IPv6 natively. Tested using Apple's NAT64 test network setup (macOS Internet Sharing with 'Create NAT64 Network' enabled) to verify connectivity.",
-    "outcome": "approved-after-fix",
-    "keywords": ["ipv6", "networking", "hardcoded-ip", "nat64", "connectivity"],
-    "behavioralSignals": ["app fails to load content", "network requests fail on review", "hardcoded IP addresses in code", "works on WiFi but fails in review"],
-    "year": 2023
-  },
-  {
-    "id": "nat64-ipv6-mismatch-local-vs-review",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app failed to connect to its server when tested on Apple's IPv6 review network.",
-    "whatDeveloperDid": "The app used a third-party networking library that had a bug with NAT64 address synthesis. It worked on the developer's local IPv6 test setup but failed on Apple's specific NAT64/DNS64 configuration because the library was manually resolving DNS instead of letting the system handle it.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: Your app was unable to connect to its server during review. The app displayed a 'Connection Error' message when attempting to load the main feed. We tested on an IPv6 network and were unable to use the app's core functionality.",
-    "fix": "Updated the third-party networking library to the latest version which fixed the NAT64 compatibility issue. Switched from manual DNS resolution to system-provided APIs (getaddrinfo) that properly handle IPv6 address synthesis. Verified using Apple's recommended NAT64 testing setup.",
-    "outcome": "approved-after-fix",
-    "keywords": ["nat64", "ipv6", "dns64", "networking", "address-synthesis", "connectivity"],
-    "behavioralSignals": ["connection error on review network", "works locally but fails in review", "third-party networking library", "manual DNS resolution"],
-    "year": 2022
-  },
-  {
-    "id": "background-audio-mode-no-audio",
-    "guidelineNumber": "2.5.4",
-    "guidelineName": "Required Device Capabilities",
-    "category": "performance",
-    "rejectionReason": "Your app declares audio background mode but does not play audio content.",
-    "whatDeveloperDid": "Added the UIBackgroundModes 'audio' capability to keep the app alive in the background for periodic data syncing, even though the app had no audio playback functionality.",
-    "whatAppleSaid": "Guideline 2.5.4 - Performance - Software Requirements: Your app declares the audio background mode in UIBackgroundModes but does not include audio playback functionality. The audio background mode is intended only for apps that provide audible content to the user. Using background modes for purposes other than their intended function is not permitted.",
-    "fix": "Removed the 'audio' UIBackgroundMode. Implemented proper background data syncing using BGTaskScheduler (BGAppRefreshTask and BGProcessingTask) which is the correct API for periodic background work without requiring audio playback.",
-    "outcome": "approved-after-fix",
-    "keywords": ["background-mode", "audio", "UIBackgroundModes", "background-processing", "misuse"],
-    "behavioralSignals": ["audio background mode declared", "no audio playback in app", "app stays alive in background", "background mode abuse"],
-    "year": 2023
-  },
-  {
-    "id": "demo-account-2fa-blocking-reviewer",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "We were unable to sign in to your app with the demo account provided because it required two-factor authentication.",
-    "whatDeveloperDid": "Provided demo account credentials in the App Review notes, but the account had mandatory two-factor authentication enabled which sent an SMS code to the developer's phone. The Apple reviewer had no way to receive the 2FA code.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: We were unable to complete the review of your app because we could not sign in using the demo credentials provided. The account requires two-factor authentication via SMS, and we were unable to receive the verification code. Please provide demo credentials that allow full access without requiring additional verification steps.",
-    "fix": "Created a dedicated demo/review account with 2FA disabled. Added the demo credentials (username, password) in the App Review Information section of App Store Connect. Included a note explaining which features to test and any special instructions for the reviewer.",
-    "outcome": "approved-after-fix",
-    "keywords": ["demo-account", "2fa", "authentication", "login", "reviewer-access", "two-factor"],
-    "behavioralSignals": ["2FA required on demo account", "SMS verification blocking reviewer", "unable to sign in during review", "demo credentials incomplete"],
-    "year": 2024
-  },
-  {
-    "id": "magic-link-email-prefetch-ipad",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "We were unable to sign in using the magic link authentication because the link expired before we could use it.",
-    "whatDeveloperDid": "Implemented passwordless authentication using magic links sent via email. When the Apple reviewer opened the email on iPad, the Mail app's link preview/prefetch feature automatically triggered the magic link URL, consuming it before the reviewer could manually tap it to authenticate.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: We were unable to complete the login process. We received the magic link email, but when we tapped the link it showed 'Link expired or already used.' We attempted this multiple times with the same result.",
-    "fix": "Changed the magic link flow to a two-step process: the link now opens a confirmation page in the browser where the user must tap 'Confirm Sign In' before the token is consumed. This prevents email client prefetching from invalidating the link. Also added a fallback OTP code option as an alternative to magic links.",
-    "outcome": "approved-after-fix",
-    "keywords": ["magic-link", "authentication", "email-prefetch", "login", "link-expiry", "passwordless"],
-    "behavioralSignals": ["magic link expires immediately", "link already used error", "email prefetch consuming link", "login fails on iPad Mail"],
-    "year": 2024
-  },
-  {
-    "id": "passkey-aasa-creation-failure",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Passkey creation failed during our review. The app displayed an error when attempting to create a passkey.",
-    "whatDeveloperDid": "Implemented passkey (WebAuthn) authentication but the Apple App Site Association (AASA) file wasn't being fetched quickly enough by Apple's CDN during the review. The passkey creation requires the AASA file to be available at /.well-known/apple-app-site-association to verify the domain-app association.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: We were unable to create a passkey during review. When attempting to register, the app displayed 'Unable to create passkey. Please try again later.' We attempted multiple times without success.",
-    "fix": "Ensured the AASA file was properly hosted and cached before submission. Added the associated domains entitlement with the webcredentials service. Pre-warmed the AASA cache by making requests to the domain before submission. Also added a fallback email/password registration option so reviewers could complete onboarding even if passkey creation failed.",
-    "outcome": "approved-after-fix",
-    "keywords": ["passkey", "webauthn", "aasa", "authentication", "associated-domains", "fido"],
-    "behavioralSignals": ["passkey creation error", "AASA file not found", "domain association failure", "authentication registration fails"],
-    "year": 2024
-  },
-  {
-    "id": "codepush-hot-code-push-rejection",
-    "guidelineNumber": "2.3.1",
-    "guidelineName": "Hidden or Undocumented Features",
-    "category": "performance",
-    "rejectionReason": "Your app includes the ability to download and execute code after installation, which can be used to introduce features not reviewed by Apple.",
-    "whatDeveloperDid": "Used Microsoft CodePush (or a similar hot-code-push solution) to push JavaScript bundle updates to a React Native app, bypassing the App Store review process. The updates were capable of changing app functionality beyond minor bug fixes.",
-    "whatAppleSaid": "Guideline 2.3.1 - Performance - Accurate Metadata: Your app contains hidden features. Specifically, your app includes functionality that allows for the remote downloading and execution of code that can change the app's behavior or functionality after review. Apps must not provide mechanisms to alter their primary functionality post-review.",
-    "fix": "Configured CodePush to only push minor bug fixes and UI text changes, not functional changes. Added documentation in the review notes explaining that CodePush is used only for critical bug fixes and does not alter app functionality. Some developers choose to remove CodePush entirely and use standard App Store updates instead.",
-    "outcome": "approved-after-fix",
-    "keywords": ["codepush", "hot-code-push", "hidden-features", "remote-code", "javascript-bundle", "react-native"],
-    "behavioralSignals": ["CodePush SDK detected", "remote code execution capability", "JavaScript bundle updates", "app behavior changes post-review"],
-    "year": 2022
-  },
-  {
-    "id": "missing-app-icon",
-    "guidelineNumber": "2.3",
-    "guidelineName": "Accurate Metadata",
-    "category": "performance",
-    "rejectionReason": "Your app is missing the required app icon.",
-    "whatDeveloperDid": "Submitted an app without including the 1024x1024 App Store icon in the asset catalog, or the icon was corrupted/transparent. The app appeared with a blank or default icon in App Store Connect.",
-    "whatAppleSaid": "Guideline 2.3 - Performance - Accurate Metadata: Your app is missing the required 1024x1024 App Store icon. All apps must include a valid app icon that will be displayed on the App Store. Please add the icon to your app's asset catalog.",
-    "fix": "Added the 1024x1024 App Store icon to the Assets.xcassets/AppIcon.appiconset. Verified all required icon sizes were present and none were transparent or contained alpha channels (which App Store Connect rejects).",
-    "outcome": "approved-after-fix",
-    "keywords": ["app-icon", "missing-icon", "metadata", "asset-catalog", "icon-size"],
-    "behavioralSignals": ["blank app icon", "missing icon in asset catalog", "corrupted icon file", "transparent app icon"],
-    "year": 2023
-  },
-  {
-    "id": "ios-release-notes-in-macos-app",
-    "guidelineNumber": "2.3",
-    "guidelineName": "Accurate Metadata",
-    "category": "performance",
-    "rejectionReason": "Your macOS app's release notes reference iOS-specific features and terminology.",
-    "whatDeveloperDid": "Jesse Squires' Taxatio app was a universal app supporting both iOS and macOS. The release notes for a macOS update mentioned iOS-specific features like 'improved iPhone widget' and 'haptic feedback improvements' that don't apply to macOS.",
-    "whatAppleSaid": "Guideline 2.3 - Performance - Accurate Metadata: Your Mac app's release notes reference iOS-specific features ('iPhone widget', 'haptic feedback'). Release notes for macOS apps should be relevant to the macOS version of your app.",
-    "fix": "Created platform-specific release notes. For macOS submissions, wrote release notes that only reference macOS-relevant features and improvements. Used App Store Connect's platform-specific metadata fields to provide different release notes for each platform.",
-    "outcome": "approved-after-fix",
-    "keywords": ["release-notes", "macos", "ios", "metadata", "platform-specific", "universal-app"],
-    "behavioralSignals": ["iOS terms in macOS release notes", "platform-specific features mentioned for wrong platform", "universal app with shared metadata"],
-    "year": 2023
-  },
-  {
-    "id": "screenshots-dont-match-ui",
-    "guidelineNumber": "2.3.7",
-    "guidelineName": "Accurate Metadata - Screenshots",
-    "category": "performance",
-    "rejectionReason": "Your app's screenshots do not accurately reflect the current version of your app.",
-    "whatDeveloperDid": "Submitted an app update with significant UI changes but forgot to update the App Store screenshots. The screenshots showed the old design with a tab bar at the bottom, while the new version used a sidebar navigation pattern.",
-    "whatAppleSaid": "Guideline 2.3.7 - Performance - Accurate Metadata: Your app's screenshots do not reflect the current version of your app. The screenshots show a different navigation pattern and UI layout than what is present in the current build. Please update your screenshots to accurately represent the app.",
-    "fix": "Took new screenshots on all required device sizes reflecting the current UI. Used Xcode's screenshot automation or a tool like fastlane snapshot to generate consistent screenshots across all required device sizes and localizations.",
-    "outcome": "approved-after-fix",
-    "keywords": ["screenshots", "metadata", "ui-mismatch", "app-store-connect", "visual-accuracy"],
-    "behavioralSignals": ["screenshots show old design", "UI changed since screenshots taken", "navigation pattern mismatch", "outdated marketing assets"],
-    "year": 2024
-  },
-  {
-    "id": "free-word-in-preview-poster-frame",
-    "guidelineNumber": "2.3",
-    "guidelineName": "Accurate Metadata",
-    "category": "performance",
-    "rejectionReason": "Your app preview poster frame contains the word 'Free' which references pricing.",
-    "whatDeveloperDid": "Created an app preview video whose poster frame (the still image shown before the video plays) contained text overlay saying 'Try Free for 7 Days'. Apple prohibits pricing references in app preview content.",
-    "whatAppleSaid": "Guideline 2.3 - Performance - Accurate Metadata: Your app preview includes references to your app's price. Specifically, the poster frame contains the text 'Try Free for 7 Days.' App previews and screenshots may not reference pricing information, as pricing can vary by region and may change over time.",
-    "fix": "Removed the 'Try Free for 7 Days' text from the app preview poster frame and video. Replaced it with a value-proposition message like 'Track Your Fitness Goals' that describes app functionality without referencing pricing.",
-    "outcome": "approved-after-fix",
-    "keywords": ["app-preview", "poster-frame", "free", "pricing", "metadata", "screenshots"],
-    "behavioralSignals": ["word 'Free' in preview", "pricing mentioned in screenshots", "poster frame with price reference", "promotional pricing in media"],
-    "year": 2023
-  },
-  {
-    "id": "version-number-suggesting-beta",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app's version number suggests it is a pre-release or beta version.",
-    "whatDeveloperDid": "Submitted the first version of an app with version number '0.1' or '0.9.2-beta', suggesting the app was not yet a complete, finished product ready for the App Store.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: Your app version number (0.1) suggests that the app is still in development or beta stage. Apps submitted to the App Store should be final versions. Please update your version number to reflect a production-ready release (e.g., 1.0).",
-    "fix": "Changed the version number from '0.1' to '1.0.0' in the project settings and App Store Connect. Removed any 'beta' or 'pre-release' suffixes from the version string and marketing version.",
-    "outcome": "approved-after-fix",
-    "keywords": ["version-number", "beta", "pre-release", "app-completeness", "version-string"],
-    "behavioralSignals": ["version number below 1.0", "beta in version string", "pre-release version numbering", "0.x version submitted to App Store"],
-    "year": 2022
-  },
-  {
-    "id": "debug-mode-left-enabled",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app appears to have debug or development mode features visible to users.",
-    "whatDeveloperDid": "Submitted a production build with debug logging visible in a console view, a floating debug menu accessible via a hidden gesture, and network request/response details displayed in an overlay that could be triggered by shaking the device.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: Your app includes development tools and debug information that are visible to users. Specifically, shaking the device reveals a network debugging overlay and there is a hidden debug menu accessible through a multi-tap gesture. Please remove all development/debugging features from the production build.",
-    "fix": "Wrapped all debug UI elements in #if DEBUG preprocessor directives. Removed the shake-to-debug gesture recognizer from the release build. Ensured the debug menu is only accessible in development builds by checking the build configuration at runtime.",
-    "outcome": "approved-after-fix",
-    "keywords": ["debug-mode", "development-tools", "debug-menu", "logging", "production-build"],
-    "behavioralSignals": ["debug overlay visible", "shake to reveal debug tools", "hidden debug menu accessible", "network logging displayed to users"],
-    "year": 2023
-  },
-  {
-    "id": "localhost-development-urls-production",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app attempts to connect to localhost or development server URLs.",
-    "whatDeveloperDid": "Accidentally shipped a production build with the API base URL still pointing to 'http://localhost:3000' or a staging server like 'https://staging-api.example.com'. The app failed to load any content during review because the development server was not accessible.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: Your app was unable to load content during our review. We found that the app is attempting to connect to development/staging server URLs that are not accessible. Please ensure your app connects to production servers.",
-    "fix": "Fixed the build configuration to use the correct production API URL. Implemented environment-based configuration using .xcconfig files or build schemes so that Debug/Staging/Release builds automatically use the correct server URLs. Added a runtime check that warns during development if production URLs are not configured.",
-    "outcome": "approved-after-fix",
-    "keywords": ["localhost", "development-server", "staging", "api-url", "build-configuration"],
-    "behavioralSignals": ["app can't load content", "localhost in network requests", "staging URL in production", "development server reference"],
-    "year": 2023
-  },
-  {
-    "id": "large-asset-download-no-disclosure",
-    "guidelineNumber": "2.3",
-    "guidelineName": "Accurate Metadata",
-    "category": "performance",
-    "rejectionReason": "Your app downloads large amounts of data after installation without informing the user.",
-    "whatDeveloperDid": "Published a game that was 150MB on download but immediately required an additional 2GB asset download on first launch without any disclosure in the App Store listing or a user prompt before downloading.",
-    "whatAppleSaid": "Guideline 2.3 - Performance - Accurate Metadata: Your app downloads a significant amount of additional content (approximately 2GB) after installation without informing the user beforehand. Users should be informed about the total storage requirements. Please disclose the additional download requirement in your app description and provide a prompt before downloading.",
-    "fix": "Added a note in the App Store description about the additional download size. Implemented a pre-download prompt showing the total size and allowing the user to choose when to download. Added a progress indicator showing download status and the option to download over Wi-Fi only.",
-    "outcome": "approved-after-fix",
-    "keywords": ["asset-download", "large-download", "storage", "disclosure", "on-demand-resources"],
-    "behavioralSignals": ["large post-install download", "no size disclosure", "immediate background download", "storage requirement hidden"],
-    "year": 2022
-  },
-  {
-    "id": "incomplete-ui-blank-purchase-page",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app has an incomplete user interface. A purchase/subscription page appears blank.",
-    "whatDeveloperDid": "The app's premium subscription page was blank during review because the StoreKit products hadn't been approved in App Store Connect yet, or the product IDs were misconfigured. The reviewer saw an empty paywall with no pricing or subscription options displayed.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: Your app appears to be incomplete. Specifically, the subscription page does not display any content - it appears as a blank screen with no purchase options. Please ensure all pages in your app are fully functional.",
-    "fix": "Ensured all IAP products were in 'Ready to Submit' or 'Approved' status in App Store Connect before submitting the app for review. Added error handling and a fallback UI for when StoreKit products fail to load, showing a 'Unable to load products. Please try again.' message with a retry button instead of a blank screen.",
-    "outcome": "approved-after-fix",
-    "keywords": ["blank-screen", "iap", "storekit", "purchase-page", "subscription", "incomplete-ui"],
-    "behavioralSignals": ["empty subscription page", "blank paywall screen", "no products displayed", "StoreKit products not loading"],
-    "year": 2024
-  },
-  {
-    "id": "crash-from-apple-framework-bug",
-    "guidelineNumber": "2.1",
-    "guidelineName": "App Completeness",
-    "category": "performance",
-    "rejectionReason": "Your app crashed during review due to a system framework issue, but the rejection still stands.",
-    "whatDeveloperDid": "The app crashed during review due to a known bug in Apple's own UIKit framework (specifically a UICollectionView layout crash on certain iOS versions). The developer filed a Radar/Feedback but the crash still caused a rejection because Apple reviews based on observed behavior, not cause.",
-    "whatAppleSaid": "Guideline 2.1 - Performance - App Completeness: We discovered one or more bugs in your app. The app crashed when navigating to the gallery view. While we understand this may be related to a system framework issue, apps must not crash regardless of the underlying cause.",
-    "fix": "Implemented a workaround for the UIKit framework bug by using a different collection view layout approach. Added a try-catch wrapper around the problematic layout code and a fallback layout in case of failure. Filed a Feedback Assistant report with Apple about the underlying framework bug.",
-    "outcome": "approved-after-fix",
-    "keywords": ["framework-bug", "apple-bug", "crash", "uikit", "workaround", "system-crash"],
-    "behavioralSignals": ["crash in Apple framework", "UIKit layout crash", "system bug causing rejection", "crash not in developer code"],
-    "year": 2024
-  }
-]

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

@@ -1,212 +0,0 @@
-[
-  {
-    "id": "ugc-moderation-missing-fliplearn",
-    "guidelineNumber": "1.2",
-    "guidelineName": "User-Generated Content",
-    "category": "safety",
-    "rejectionReason": "Your app includes user-generated content but does not include the required moderation controls.",
-    "whatDeveloperDid": "Built an education app (FlipLearn) with a social feed where students could post content, but did not include any report, block, or flag buttons on posts or user profiles.",
-    "whatAppleSaid": "Guideline 1.2 - Safety - User-Generated Content: Your app enables the display of user-generated content but does not have the required precautions in place. Specifically, your app is missing the ability to report objectionable content, block abusive users, and a mechanism to flag content for review.",
-    "fix": "Added a flag/report button on every post and user profile, implemented user blocking functionality, added a 24-hour content moderation SLA with a dedicated moderation queue, and included a visible link to community guidelines.",
-    "outcome": "approved-after-fix",
-    "keywords": ["ugc", "moderation", "report", "block", "flag", "user-generated-content"],
-    "behavioralSignals": ["app has social feed", "users can post content", "no report button visible", "no block functionality"],
-    "year": 2023
-  },
-  {
-    "id": "kids-category-firebase-analytics",
-    "guidelineNumber": "1.3",
-    "guidelineName": "Kids Category",
-    "category": "safety",
-    "rejectionReason": "Your Kids Category app includes third-party analytics with the ability to collect identifiable information from minors.",
-    "whatDeveloperDid": "Published a kids educational game in the Kids Category on the App Store while including Firebase Analytics SDK, which can collect device identifiers and behavioral data in violation of COPPA regulations.",
-    "whatAppleSaid": "Guideline 1.3 - Safety - Kids Category: Your app includes third-party analytics software with the ability to collect and transmit identifiable information about children. Specifically, we found your app integrates Firebase Analytics which may collect device identifiers. Apps in the Kids Category must not include third-party analytics or advertising that can collect identifiable information.",
-    "fix": "Removed Firebase Analytics SDK entirely from the app. Replaced with a custom first-party analytics solution that collects only anonymous aggregate event counts stored on the developer's own server, with no device identifiers or user-level tracking.",
-    "outcome": "approved-after-fix",
-    "keywords": ["kids-category", "firebase", "analytics", "coppa", "children", "data-collection"],
-    "behavioralSignals": ["app is in Kids Category", "Firebase SDK detected in binary", "analytics collecting device identifiers"],
-    "year": 2022
-  },
-  {
-    "id": "kids-category-amplitude-sdk",
-    "guidelineNumber": "1.3",
-    "guidelineName": "Kids Category",
-    "category": "safety",
-    "rejectionReason": "Your Kids Category app includes third-party analytics (Amplitude) which may collect identifiable information from children.",
-    "whatDeveloperDid": "Integrated Amplitude analytics SDK in a children's learning app listed in the Kids Category to track user engagement and session metrics.",
-    "whatAppleSaid": "Guideline 1.3 - Safety - Kids Category: We found that your app uses the Amplitude SDK, which has the capability to collect identifiable information. Apps in the Kids Category may not include third-party analytics or third-party advertising. You must remove all such SDKs before resubmitting.",
-    "fix": "Removed Amplitude SDK completely. Built a lightweight custom event tracker that only logs anonymized session durations and feature usage counts without any device fingerprinting, IDFA, or persistent identifiers.",
-    "outcome": "approved-after-fix",
-    "keywords": ["kids-category", "amplitude", "analytics", "coppa", "children", "tracking-sdk"],
-    "behavioralSignals": ["app targets children", "Amplitude SDK in binary scan", "third-party analytics present in Kids Category app"],
-    "year": 2023
-  },
-  {
-    "id": "anonymous-chat-pornography-risk",
-    "guidelineNumber": "1.1.4",
-    "guidelineName": "Objectionable Content - Pornography",
-    "category": "safety",
-    "rejectionReason": "Your app connects users anonymously for video chat, which presents a high risk of pornographic or objectionable content.",
-    "whatDeveloperDid": "Built a Chatroulette-style anonymous video chat app that randomly paired strangers for live video conversations with no content filtering or identity verification.",
-    "whatAppleSaid": "Guideline 1.1.4 - Safety - Objectionable Content: Your app facilitates anonymous video connections between users, which creates significant risk for pornographic content, exploitation, and abuse. Apps that connect strangers for anonymous communication must implement robust safeguards including content moderation and age verification.",
-    "fix": "The developer was unable to adequately address Apple's concerns. Anonymous random video chat apps are effectively banned from the App Store due to the inherent risk of objectionable content. The developer pivoted to a moderated, interest-based matching system with AI-powered nudity detection, mandatory profile verification, and real-time content monitoring.",
-    "outcome": "approved-after-fix",
-    "keywords": ["anonymous-chat", "video-chat", "chatroulette", "pornography", "content-moderation", "age-verification"],
-    "behavioralSignals": ["anonymous video pairing", "no identity verification", "random stranger matching", "no content filtering"],
-    "year": 2021
-  },
-  {
-    "id": "drug-dosage-calculator-unapproved-entity",
-    "guidelineNumber": "1.4.2",
-    "guidelineName": "Medical - Drug Dosage Calculators",
-    "category": "safety",
-    "rejectionReason": "Your app provides drug dosage calculations but is not from a recognized institution such as a drug manufacturer, hospital, or university.",
-    "whatDeveloperDid": "An independent developer built a drug dosage calculator app for healthcare professionals that calculated dosages based on patient weight, age, and renal function without affiliation to any medical institution.",
-    "whatAppleSaid": "Guideline 1.4.2 - Safety - Medical: Your app provides drug dosage calculations. Per App Store Review Guidelines, drug dosage calculators must come from the drug manufacturer, a hospital, university, health insurance company, pharmacy, or other approved entity. We are unable to accept drug dosage calculators from independent developers due to the potential risk to patient safety.",
-    "fix": "The developer partnered with a university hospital's pharmacy department, which agreed to co-publish the app under the hospital's developer account with clinical pharmacist review and validation of all dosage formulas.",
-    "outcome": "approved-after-fix",
-    "keywords": ["medical", "drug-dosage", "calculator", "institution", "healthcare", "patient-safety"],
-    "behavioralSignals": ["app calculates drug dosages", "independent developer account", "no institutional affiliation", "medical calculations without clinical oversight"],
-    "year": 2022
-  },
-  {
-    "id": "missing-age-rating-violence-gambling",
-    "guidelineNumber": "1.1",
-    "guidelineName": "Objectionable Content",
-    "category": "safety",
-    "rejectionReason": "Your app contains content that requires a higher age rating than what is currently set in App Store Connect.",
-    "whatDeveloperDid": "Published a card game app with simulated gambling mechanics (poker chips, betting) and cartoon combat violence, but set the age rating to 4+ in App Store Connect without properly answering the content description questionnaire.",
-    "whatAppleSaid": "Guideline 1.1 - Safety - Objectionable Content: Your app contains simulated gambling and frequent/intense cartoon violence, but the age rating is set to 4+. You must update your age rating in App Store Connect to accurately reflect the content in your app. Please review the content descriptions and adjust accordingly.",
-    "fix": "Updated the App Store Connect age rating questionnaire to accurately reflect simulated gambling (selecting 'Frequent/Intense') and cartoon violence (selecting 'Frequent/Intense'), which raised the age rating to 12+.",
-    "outcome": "approved-after-fix",
-    "keywords": ["age-rating", "violence", "gambling", "content-rating", "app-store-connect"],
-    "behavioralSignals": ["app contains gambling mechanics", "violence present in gameplay", "age rating set too low", "content questionnaire answered incorrectly"],
-    "year": 2023
-  },
-  {
-    "id": "tinyco-kids-email-collection-ftc",
-    "guidelineNumber": "1.3",
-    "guidelineName": "Kids Category",
-    "category": "safety",
-    "rejectionReason": "App collected children's email addresses for in-game rewards without verifiable parental consent.",
-    "whatDeveloperDid": "TinyCo's kids games prompted children to enter their email addresses to receive virtual game items and rewards, collecting personal information from minors without obtaining verifiable parental consent as required by COPPA.",
-    "whatAppleSaid": "This case resulted in an FTC settlement rather than a standard App Review rejection. The FTC found TinyCo violated COPPA by collecting children's email addresses without parental consent. Apple subsequently tightened enforcement of Guideline 1.3 for all Kids Category apps.",
-    "fix": "TinyCo paid a $300,000 FTC settlement and removed all email collection prompts from kids games. Implemented age-gating and parental consent flows for any data collection. This case became a precedent for stricter Kids Category enforcement.",
-    "outcome": "approved-after-fix",
-    "keywords": ["kids-category", "email-collection", "coppa", "ftc", "parental-consent", "children-privacy"],
-    "behavioralSignals": ["email input field in kids game", "rewards requiring personal info", "no parental consent gate", "children's data collection"],
-    "year": 2014
-  },
-  {
-    "id": "ninjawords-dictionary-vulgar-terms",
-    "guidelineNumber": "1.1.1",
-    "guidelineName": "Objectionable Content - Defamatory or Mean-Spirited",
-    "category": "safety",
-    "rejectionReason": "Your app contains objectionable content including vulgar and profane language.",
-    "whatDeveloperDid": "Ninjawords, a dictionary app, was rejected because it contained definitions for vulgar and profane words. The developer had to strip out thousands of dictionary entries that Apple deemed objectionable, even though the app was a reference dictionary.",
-    "whatAppleSaid": "Your application contains content that many audiences would find objectionable. Specifically, the dictionary includes definitions for terms that are vulgar, profane, and sexually explicit in nature. You must remove this content or implement a content filter.",
-    "fix": "The developer removed objectionable word definitions from the dictionary database and submitted a censored version. This case sparked public controversy about Apple's content policies, as critics argued a dictionary should be allowed to define all words. Apple later softened its stance on reference content when properly age-rated.",
-    "outcome": "approved-after-fix",
-    "keywords": ["dictionary", "objectionable-content", "profanity", "censorship", "reference-app"],
-    "behavioralSignals": ["dictionary with vulgar definitions", "no content filter", "unrestricted word lookup", "profane terms displayed"],
-    "year": 2009
-  },
-  {
-    "id": "hot-or-not-voting-objectification",
-    "guidelineNumber": "1.1.1",
-    "guidelineName": "Objectionable Content - Defamatory or Mean-Spirited",
-    "category": "safety",
-    "rejectionReason": "Your app enables users to rate the physical appearance of real people, which is considered mean-spirited and objectionable.",
-    "whatDeveloperDid": "Built a Hot-or-Not style app where users could upload photos of real people and other users would vote on their attractiveness with a rating system.",
-    "whatAppleSaid": "Guideline 1.1.1 - Safety - Objectionable Content: Your app allows users to rate the physical appearance of other people, which Apple considers to be mean-spirited and potentially harmful. This type of content that objectifies real individuals is not appropriate for the App Store.",
-    "fix": "The concept was fundamentally incompatible with Apple's guidelines. The developer pivoted to a photo contest app where users voluntarily submitted their own photos to themed photography challenges judged on artistic merit rather than personal appearance.",
-    "outcome": "approved-after-fix",
-    "keywords": ["objectification", "rating-people", "mean-spirited", "hot-or-not", "appearance-rating"],
-    "behavioralSignals": ["photo rating of real people", "attractiveness voting", "user photos rated by strangers", "appearance-based scoring"],
-    "year": 2019
-  },
-  {
-    "id": "for-kids-description-not-kids-category",
-    "guidelineNumber": "1.3",
-    "guidelineName": "Kids Category",
-    "category": "safety",
-    "rejectionReason": "Your app references being designed for kids in its metadata but is not published in the Kids Category.",
-    "whatDeveloperDid": "Published an app outside the Kids Category but included phrases like 'perfect for kids' and 'designed for children ages 3-8' in the app description and marketing text. The app also did not comply with Kids Category data collection restrictions.",
-    "whatAppleSaid": "Guideline 1.3 - Safety - Kids Category: Your app's metadata indicates it is designed for children, but it is not published in the Kids Category. Apps that are designed specifically for children must be published in the Kids Category and must comply with all Kids Category requirements, including restrictions on data collection, third-party analytics, and advertising.",
-    "fix": "The developer had two choices: either move the app to the Kids Category and comply with all Kids Category requirements (removing third-party analytics, advertising, and external links), or remove all references to children from the app description and metadata. They chose to move to the Kids Category and strip out non-compliant SDKs.",
-    "outcome": "approved-after-fix",
-    "keywords": ["kids-category", "metadata", "children", "app-description", "category-mismatch"],
-    "behavioralSignals": ["app description mentions kids", "not in Kids Category", "child-oriented content outside Kids Category", "metadata references children"],
-    "year": 2022
-  },
-  {
-    "id": "kids-app-third-party-advertising",
-    "guidelineNumber": "1.3",
-    "guidelineName": "Kids Category",
-    "category": "safety",
-    "rejectionReason": "Your Kids Category app includes third-party advertising which is not permitted.",
-    "whatDeveloperDid": "Published a children's coloring book app in the Kids Category that displayed AdMob banner ads and interstitial ads between activities. The ads were not age-appropriate and included tracking.",
-    "whatAppleSaid": "Guideline 1.3 - Safety - Kids Category: Your app includes third-party advertising (Google AdMob) in a Kids Category app. Apps in the Kids Category may not include third-party advertising or analytics. All ads in Kids Category apps must be appropriate for children and must not include behavioral targeting or tracking.",
-    "fix": "Removed Google AdMob SDK entirely. Switched to a premium paid model with no ads. For developers who need ad revenue in Kids Category apps, Apple requires using Apple's own advertising framework (SKAdNetwork) with certified kid-safe ad content from Apple-approved networks.",
-    "outcome": "approved-after-fix",
-    "keywords": ["kids-category", "advertising", "admob", "third-party-ads", "children", "ad-tracking"],
-    "behavioralSignals": ["ads displayed in kids app", "AdMob SDK detected", "interstitial ads between activities", "behavioral ad targeting in children's app"],
-    "year": 2023
-  },
-  {
-    "id": "ugc-app-no-terms-of-service",
-    "guidelineNumber": "1.2",
-    "guidelineName": "User-Generated Content",
-    "category": "safety",
-    "rejectionReason": "Your app with user-generated content does not include terms of service that users must agree to.",
-    "whatDeveloperDid": "Built a community forum app where users could post text and images but did not include any terms of service, community guidelines, or content policy that users were required to accept before participating.",
-    "whatAppleSaid": "Guideline 1.2 - Safety - User-Generated Content: Your app enables users to share content but does not include published terms of service or community guidelines. Apps with user-generated content must include terms that clearly state what content is not acceptable and the consequences of violations.",
-    "fix": "Added a Terms of Service and Community Guidelines document within the app. Implemented a mandatory acceptance flow during onboarding where users must agree to the terms before being able to post content. Added a link to the terms in the app settings.",
-    "outcome": "approved-after-fix",
-    "keywords": ["ugc", "terms-of-service", "community-guidelines", "content-policy", "user-agreement"],
-    "behavioralSignals": ["no terms of service visible", "users can post without accepting rules", "missing content policy", "no community guidelines"],
-    "year": 2023
-  },
-  {
-    "id": "medical-app-no-disclaimers",
-    "guidelineNumber": "1.4.1",
-    "guidelineName": "Medical - Physical Harm",
-    "category": "safety",
-    "rejectionReason": "Your medical app does not include appropriate disclaimers about the limitations of its health-related information.",
-    "whatDeveloperDid": "Created a symptom checker app that provided potential diagnoses based on user-entered symptoms without any medical disclaimers, warnings that the information is not a substitute for professional medical advice, or recommendation to consult a healthcare provider.",
-    "whatAppleSaid": "Guideline 1.4.1 - Safety - Physical Harm: Your app provides medical information and symptom analysis without appropriate disclaimers. Medical apps must clearly indicate that the information provided is not intended to replace professional medical advice, diagnosis, or treatment. You must include prominent disclaimers throughout the app.",
-    "fix": "Added a prominent disclaimer on the app's launch screen and before every symptom analysis result stating 'This app is for informational purposes only and is not a substitute for professional medical advice. Always consult a qualified healthcare provider.' Also added a persistent disclaimer banner on all diagnosis result screens.",
-    "outcome": "approved-after-fix",
-    "keywords": ["medical", "disclaimers", "symptom-checker", "health", "diagnosis", "patient-safety"],
-    "behavioralSignals": ["medical advice without disclaimers", "symptom checker with no warnings", "health app missing liability notice", "diagnosis results without professional consultation reminder"],
-    "year": 2022
-  },
-  {
-    "id": "tobacco-alcohol-no-age-gate",
-    "guidelineNumber": "1.1.5",
-    "guidelineName": "Objectionable Content - Age-Restricted Content",
-    "category": "safety",
-    "rejectionReason": "Your app promotes tobacco and/or alcohol products without implementing an age verification gate.",
-    "whatDeveloperDid": "Built a craft beer discovery app that showcased various alcohol brands, included purchasing links, and featured tobacco-related lifestyle content without any age verification or age gate on app launch.",
-    "whatAppleSaid": "Guideline 1.1.5 - Safety - Objectionable Content: Your app facilitates the sale or promotion of tobacco and alcohol products but does not include an age gate. Apps that promote or sell age-restricted products must include an appropriate age verification mechanism to ensure users meet the minimum legal age requirements.",
-    "fix": "Implemented an age gate on first launch requiring users to confirm they are of legal drinking age (21+ in US). Added date-of-birth verification with persistent storage so users only need to verify once. Also added age-appropriate content warnings on alcohol-related pages.",
-    "outcome": "approved-after-fix",
-    "keywords": ["age-gate", "alcohol", "tobacco", "age-verification", "age-restricted", "legal-age"],
-    "behavioralSignals": ["alcohol content displayed without age check", "no age verification on launch", "tobacco promotion without gate", "purchasing links for age-restricted products"],
-    "year": 2023
-  },
-  {
-    "id": "social-media-no-content-reporting",
-    "guidelineNumber": "1.2",
-    "guidelineName": "User-Generated Content",
-    "category": "safety",
-    "rejectionReason": "Your social media app does not include a mechanism for users to report objectionable content.",
-    "whatDeveloperDid": "Launched a photo-sharing social media app with commenting and messaging features but only included content moderation on the backend. There was no user-facing way to report posts, comments, or other users for objectionable content.",
-    "whatAppleSaid": "Guideline 1.2 - Safety - User-Generated Content: Your app includes user-generated content features such as photo sharing and commenting but does not provide a mechanism for users to report objectionable content and abusive users. You must implement a reporting mechanism that is easily accessible to users.",
-    "fix": "Added a three-dot menu on every post and comment with a 'Report' option. Added a 'Report User' button on user profiles. Implemented a report flow with categories (spam, harassment, inappropriate content, etc.) and confirmation. Also added an in-app content moderation dashboard for the team.",
-    "outcome": "approved-after-fix",
-    "keywords": ["social-media", "content-reporting", "ugc", "moderation", "report-mechanism", "abuse-reporting"],
-    "behavioralSignals": ["no report button on posts", "no way to report users", "content moderation only backend", "missing user-facing reporting"],
-    "year": 2024
-  }
-]