publish_to_appstore
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| publish_to_appstore [2024/08/14 11:03] – admin | publish_to_appstore [2024/08/17 20:06] (current) – admin | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| https:// | https:// | ||
| + | |||
| + | |||
| # In App Purchase | # In App Purchase | ||
| - | 1. Follow Overall Guidance: [[https:// | + | 1. Use StoreKit 2 to implement purchasing features in you app. [[https:// |
| - | | + | |
| - | {{: | + | 2. Test locally (StoreKit configuration). [[https:// |
| - | 1. Generate In-App-Purchase key | + | |
| + | 3. Configure App Store Connect: [[https:// | ||
| + | |||
| + | | ||
| + | |||
| + | 2. Generate In-App-Purchase key [[https:// | ||
| + | |||
| + | 3. Add Capability to my app: [[https:// | ||
| + | |||
| + | 4. Test with App Store Connect (using Sandbox in Test Flight): [[https:// | ||
| + | |||
| + | < | ||
| + | Guidelines for Choosing a Product ID | ||
| + | 1. Uniqueness: The Product ID must be unique across all of your in-app purchases for that app. No two in-app purchase items within the same app can have the same Product ID. | ||
| + | 2. Structure: Product IDs are typically structured in a way that makes them easy to identify and manage. A common practice is to use reverse domain name notation, similar to your app’s bundle identifier, but with additional detail to differentiate between different products. For example, if your app’s bundle identifier is com.example.myapp, | ||
| + | - com.example.myapp.premium_upgrade | ||
| + | - com.example.myapp.remove_ads | ||
| + | - com.example.myapp.gold_coins_100 | ||
| + | </ | ||
publish_to_appstore.1723604586.txt.gz · Last modified: (external edit)
