UnityIAP
Unity IAP
Section titled “Unity IAP”These are notes covering the process up to purchase testing.
Android
Section titled “Android”Prerequisite: the keystore used for the build
A keystore is required to publish an AAB file to Google Play Console.
Create the keystore in Project Settings, then follow the steps below.
Also, never lose the generated keystore.
- Make sure a test project has been created in Google Play Console.
- Upload an AAB file to Google Play Console. (The test stage itself is not important.)
- Register the product to test under
Monetization / Products / In-app products. - Promote it to a closed test and release it.
- Install the app on the device through
Testers / Join on Androidfor the released closed testing track, launch it once, and then test purchases.- If you encounter the following after this process:
🔧 If you get a
Product not founderror
- Check whether the test account is registered under
Google Play Console / Setup / License testing.- Make sure steps 4 and 5 have already been completed.
- Make sure a test project has been created in App Store Connect.
- Register the product to test under
Monetization / In-App Purchases.- It can still be in draft.
- It does not need to be approved.
- You can still test even if it says
Missing Metadata.
- Create a sandbox test account in App Store Connect -> Users and Access -> Sandbox.
- Sign in with the sandbox account on the test iOS device.
- [Settings -> App Store -> Sandbox Account]
- You can skip the two-factor authentication-related prompts when signing in.
- Wait a little after registering the product for the first time, then test.
- The documentation says anywhere from
a few minutes to a few hours, up to 24 hours, so it is hard to pin down an exact time.- In my case, it was updated when I tried again after 5 minutes.
- The documentation says anywhere from
Once everything above is configured, you can proceed with purchase testing.