苹果应用因内购及性能完整性问题遭拒求助

Alright, let's break down each rejection reason and walk through actionable, technical fixes to get your app approved:

1. Resolve 2.1 Performance - App Integrity Bugs & IPv6 Network Unresponsiveness #

Your app was flagged for bugs on iPads/iPhones and unresponsive behavior on iOS 11.3.1 with IPv6 Wi-Fi. Here's how to fix this:

• Reproduce the issue first:
  • Set up a test environment with iOS 11.3.1 (use a physical device or Xcode simulator running this iOS version).
  • Simulate an IPv6-only network: On your Mac, go to System Preferences > Sharing, enable Wi-Fi sharing, and configure the network to use IPv6. Alternatively, use Xcode's simulator network conditions to switch to IPv6.
  • Walk through all core app flows (login, content loading, user interactions) to pinpoint exactly where the app freezes or crashes.
• Fix IPv6 compatibility:
  • Audit all network code: Remove any hardcoded IPv4 addresses (always use domain names instead). Ensure your network library (like NSURLSession or Alamofire) supports IPv6.
  • Test DNS resolution: Make sure your backend servers have IPv6 records configured, and that your app doesn't rely on IPv4-specific network calls.
• Fix unresponsive operations:
  • Use Xcode's Instruments > Time Profiler to detect main thread blocking. Any long-running tasks (like API calls, database operations, or heavy computations) should be offloaded to background queues using DispatchQueue.global().async.
  • Check for deadlocks: Review your async code to ensure there are no circular dependencies or incorrect queue management that could freeze the UI.
• Fix iPad/iPhone compatibility bugs:
  • Use Xcode's View Debugger to inspect layout issues on both device types. Ensure Auto Layout constraints are correctly set to avoid overlapping or unclickable UI elements.
  • Test split-view and slide-over modes on iPad to ensure your app handles multitasking without crashing or freezing.

2. Fix 3.1.1 Business - In-App Purchase Violations #

Apple requires all digital goods/subscriptions in your app to use their In-App Purchase (IAP) system. Here's how to resolve this:

• Audit all paid content:
  • Identify any features, virtual goods, or subscriptions that are being paid for via third-party services (like PayPal, WeChat Pay) or external websites. These must be migrated to Apple IAP.
• Verify IAP configuration:
  • In App Store Connect, ensure all IAP products are correctly created with matching product IDs (they must exactly match the IDs used in your code).
  • Check that IAP products are set to "Ready for Submission" or "Approved" status (draft products won't work).
• Fix IAP implementation:
  • Ensure your code correctly handles the full IAP flow:
    1. Fetch product information using SKProductsRequest
    2. Process payment with SKPaymentQueue
    3. Validate purchase receipts (both locally and with Apple's server)
    4. Unlock content/subscriptions only after successful validation
• Remove external payment links:
  • Delete any in-app references or buttons that direct users to external websites to pay for digital goods. This includes text, images, or hidden prompts.

Final Submission Tips #

After fixing all issues, when you resubmit your app:

• Add detailed notes in the App Store Connect submission explaining exactly what you fixed for each rejection reason. This helps Apple's review team quickly verify your changes.
• Re-test all fixes thoroughly on the same devices and network conditions mentioned in the rejection notice to avoid rejections.

内容的提问来源于stack exchange，提问作者Chandni