You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 20, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,14 +113,17 @@ In order to do this send in `null` as parameter, along with your Activity-instan
113
113
## Testing with your own In-app products
114
114
Testing with static responses is limited, because you are only able to test the purchase-method. Therefore, testing with real In-app products is recommended. But before that is possible, you need to do the following:
115
115
* I will assume you've already created your Google Play Developer account and an application there.
116
-
* Now you need to create In-app Products under your application at PlayDeveloperConsole and activate it (pressthebuttonatthetopright).
116
+
* Now you need to create an In-app product under your application at the GooglePlayDeveloperConsole and activate it (pressthebuttonatthetopright).
117
117
* Assuming you have installed this module (InAppBilling), you can write the JS code as explained in the Javascript API section. I suggest you to use `getProductDetails` function to see if it's the product is retrieved.
118
-
* When you're ready to test, you'll need to properly create a signed APK. You can follow this [guide](https://facebook.github.io/react-native/docs/signed-apk-android.html).
119
-
* When you have the APK, you need to upload it to Play Developer Console, either the Alpha or the Beta channel will be OK.
120
-
* After uploading, you will have to publish it to the market. Don't worry, when publishing the APK to the Alpha or Beta channel the APK will not be available for general public. (**ImportantÆ*: It might take several hours for Google to process the APK).
121
-
* The final part is, you'll need to create an add testers for the channel you've published to. The web page will give you a signup URL (opt-in) after you've approved open testing. Visit this URL in the browser of your **testing device** (it must be a physical device, not a emulator) signup from the URL and download the app where it redirected.
118
+
* When you're ready to test, you'll need to properly create a signed APK. You can follow this [guide](https://facebook.github.io/react-native/docs/signed-apk-android.html). (**Important**: You'll have to install the APK as described in the guide. Not in the way you'd normally debug an React Native app on Android).
119
+
* When you have the APK, you need to upload it to Play Developer Console, either the Alpha or the Beta channel will be fine. Remember your app will need to have a proper `applicationId` (normally your package name) and `versionCode` set in `android/app/build.gradle`.
120
+
* After uploading, you will have to publish it to the market. Don't worry, when publishing the APK to the Alpha or Beta channel the APK will not be available for general public. (**Important**: It might take several hours for Google to process the APK).
121
+
* The final part is, you'll need to add testers for the channel you've published to. The web page will give you a signup URL (opt-in) after you've approved open testing. Visit this URL in the browser of your **testing device** (it must be a physical device, not a emulator) and signup, and download the app where it redirected.
122
122
* Try to buy something with the device. The purchase will eventually be cancelled, but you can also do this manually through your Google Merchant wallet.
123
123
124
+
**Important**: You can only test on a physical Android device, not from an emulator.
0 commit comments