Once you have your signed AAB file, you’ll need to go back to the Google Play Developer Console to upload it to the store. You will also need to check ‘ Google‘ under In-App Purchases in the Service Configuration section near the bottom of the page. This cannot be changed once you upload it to Google Play without making a new application and you will not be able to use a previous package name. On the Android publishing target page, make sure to use the Package Name you plan on using once it goes live. Simply copy and paste it into the field and click outside the field to allow it to save. This is where you put your License Key from the Google Play Developer Console. Expand that dropdown and select ‘Google’. Servicesįrom your GameSalad portfolio page (accessible from ), there’s a Services dropdown on the left hand side of the page. Once your project is ready, publish it to your GameSalad portfolio using the publish button across the top of the GameSalad interface. In App Purchase – Restore Items: This behavior sends a request to the store to restore any non-consumable purchases made in the app, and is typically put in a button on the store or main menu of your app.Ī sample project for IAP logic can be downloaded from this Dropbox URL:.In App Purchase – Consume Item: This behavior is for repeatable IAP’s, and should be used after rewarding a successful purchase of a consumable item so that it can be purchased again.Column 5 of the Purchase Table updates with the purchase state, and can be referenced to tell if the purchase is successful, pending, failed, etc. In App Purchase – Buy Item: This behavior sends a purchase request to the store for the ID specified in the behavior.This needs to run before any of the other IAP behaviors can work properly. In App Purchase – Request Purchase Data: This behavior sends a request to the store to get the purchase data for each of the ID’s you have set up.There are 4 in app purchase behaviors in GameSalad that you will use to create the purchase functionality in your project: One difference between Google and the other IAP providers (iOS and Amazon) with regards to setting up in-app purchases is that the Product IDs for Google IAP can’t use capital letters.Īlso, Product IDs are not case-friendly (meaning “bowlboyconsumable” is not the same as “BowlBo圜onsumable”) so you will need to keep this in mind if you plan on making a multiplatform app. The rest of the table is filled in from the IAP Request Purchase Data behavior after the app is linked to the store later. In the PurchaseTable you only fill in information for the first two columns, the id of each purchase you want to have in the app and the toggle for whether or not that purchase is consumable. This is done through the PurchaseTable and the IAP behaviors. Setting Up IAP In Creatorīefore publishing your game, you’ll need to set up your in-app purchases in Creator. You’ll be coming back to the Developer Console after making the APK in Web Publishing. Once you have the License Key, you need to set up your IAPs in Creator. This is what validates your app to use these services. From the ‘ Monetization setup‘ page, copy the License Key.The list of forms to fill out can be found under the Dashboard tab, in the Set up your app section (you may need to click on a dropdown to expand the list of tasks). Fill out the required details for your app.If you don’t have one, you will need to set one up. Log into the Google Play Developer Console from the Google account you use to publish apps to the Google Play store.The purpose of this section is to get as much done in the Developer Console as possible before publishing to remove the need to re-upload your APK for testing purposes. However, if you are updating an existing app that’s already on Google Play, you can skip to step 5. This section assumes you will be uploading a new application to Google.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |