For testing build a safari extension, just run it in Xcode. It will auto build the app and load it into Safari.

• For the first time: ref: https://instabug.com/blog/how-to-submit-app-to-app-store/
• Routine update: https://help.apple.com/xcode/mac/current/#/dev442d7f2ca

Change the version number and build number before upload it to app store

https://www.youtube.com/watch?v=DLvdZtTAJrE&t=1208s

1. Use StoreKit 2 to implement purchasing features in you app. WWDC tutorial and code
2. Test locally (StoreKit configuration). StoreKit Testing Setup
3. Configure App Store Connect: Overview for configuring in-app purchases
   1. Create In-App-Purchase from App Store Connect page Ref
   2. Generate In-App-Purchase key Ref
   3. Add Capability to my app: Ref
4. Test with App Store Connect (using Sandbox in Test Flight): Ref

  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, you might structure your Product IDs like this:
     - com.example.myapp.premium_upgrade
     - com.example.myapp.remove_ads
     - com.example.myapp.gold_coins_100