发布含CloudKit新记录通知的应用前，需删除测试订阅吗？

Great question—this is a common point of confusion when prepping CloudKit-powered apps for launch. Let’s break down what you need to know:

1. It depends on which environment your test subscriptions live in #

CloudKit strictly separates Development and Production containers, so the location of your test subscriptions determines whether you need to act:

• Development Container subscriptions: These are completely isolated from your live app’s production environment. Your released app will never interact with this container, so leftover test subscriptions here won’t affect real users or your production setup. You can leave them be if you want (they’ll just sit in your dev environment) or clean them up for tidiness—either way, no harm done.

• Production Container subscriptions: This is where you need to be careful. If you accidentally created test subscriptions in your production container (e.g., using an Ad Hoc build or testing with a production-enabled device), these could cause issues post-launch:

  • Test devices might receive unintended notifications tied to these old subscriptions.
  • They’ll count against your production CloudKit subscription quota, which could limit your ability to create new subscriptions for real users.
  • It’s best practice to delete all test-related subscriptions from the production container before release.

2. How to clean up test subscriptions #

• Use the CloudKit Dashboard to navigate to your container. Switch between Development/Production environments using the dropdown at the top.
• Go to the Subscriptions tab. Look for subscriptions with names or identifiers that mark them as test-only (e.g., com.yourapp.test.subscription).
• Select and delete any subscriptions that don’t belong in the production environment.

3. Pro tips for future releases #

• Add a distinct identifier to test subscriptions (e.g., append _test to their ID) so you can easily filter and bulk-delete them later.
• In your code, conditionally create test subscriptions only for Debug builds, so they never get created in production by accident.
• If you used test user accounts to create subscriptions, deleting those test users will automatically remove their associated subscriptions from CloudKit.

Final Takeaway #

If your test subscriptions are confined to the Development container, you don’t have to delete them. But if any made their way to Production, definitely clean them up to avoid unexpected behavior and resource bloat for your live app.

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