I have a free app on Google Play, which works normally. I decided to add some features and user needs to pay to unlock them. So I added In app billing to my app. I want to know: what is the best way to test in app billing in my situation.
I tried this way: create new application (in the same google play console as existing app) => upload new apk (which includes in app billing) as Alpha version of new Application.
The first time my new app is suspended by Google (because I use the same logo, screenshots as existing app).
I think if I replace them with other pictures, everything will work.
But I'm not sure that 's right way to test IAB.
Can anybody give me some advices? Thanks a lot
You don't need to create separate app under different package name. Just increment the version number of the current app and publish it under the same package ID as an alpha version. The in-app billing works fine in both beta and alpha releases.
Related
I'm developing an application which uses in app purchases with version 3.
And I have added the app as alpha release and published the app on store.
So what I want's to know is after the app is published if I modify some code to test do i have to upload and republish the app to check for results.
Thanks
No you need not republish app unless you want to distribute it to your testers using alpha testing link. You can directly install the apk with modified code on your device to test. Just ensure that the version code and name remains the same as the one installed on the alpha tab.
I am new to the inappbilling integration for android.I am using the develop the following link
http://developer.android.com/training/in-app-billing/preparing-iab-app.html#GetSample
and also TrivialDrive import my eclipse and generate to the apk and export apk in googleplaystoreconsole of drafts not in published and also created to the product item and put in product id to my activity and
add to the String base64EncodedPublicKey="RSA public key". finally run the code showing following screen
also ways showing this screen .i didn't understand what is going on rightnow.please help me anyone known and idea about this advance thaks to all.
Had the same problem. I contacted as well and got this response from Google
Thank you for contacting Google Play Developer Support and reporting the behavior you're seeing with in-app billing.
We recently made some changes to our systems and we are now requiring an app to be published before testing. We are currently recommending to publish your APK to the Alpha channel in order to test licensing, in-app billing, and expansion files. There is no need to create a special testing group in the Alpha channel to test these features, however the app must be published and not in draft mode.
We apologize for the inconvenience and are working to update our documentation to reflect these changes.
After publishing my APK to Alpha (as I haven't launched yet) and waiting an hour or so, my IAP test purchases started working again.
I want to send the application to the beta testing Google Play. My question is: how to do in the application so that at the end of testing people could update the app and enjoy working version. How to organize it will be in the API and in the application? Share your experiences, links or something else. thank you
There's nothing to do within the application or over some API. Right in the Developer console you're given the ability to promote your uploaded version to the Beta or Production stage. See the following screenshot:
So as soon as your app is ready for the masses, just push it to Prod and everyone will be able to download and/or update it.
I developed and publish some apps to google play using "old" interface. Now I published an app using new interface and seems that all were successful because my app appears as "published". However, previous apps were active in 1h, but now, after 2 days, I am unable to find it in google play and also unable to find any link on any option inside developer console. Is my app published? How could I then know google play link?
How could I then know google play link?
The links for Apps in the Playstore are always built with the same pattern, it looks like this:
https://play.google.com/store/apps/details?id=YOUR.PACKAGE.NAME
so you can use that link to see if your App is published or not, just replace YOUR.PACKAGE.NAME with the actual name of the package like com.google.android.music
In the new interface you can publish three versions of the app: alpha, beta, release. Check if you published the release version.
So you'll get the link to the app: https://play.google.com/store/apps/details?id=COM.PACKAGE.NAME
Check your publish area
Check your Android version
Check your Android device
I have just created a developer account at Google Play. Now I got to upload the application but I have a few doubts:
Can I add more then one android APKs for different applications?
Is it possible to upload an application for a testing and after that set the price of the app?
Is it possible to set such criteria where first 500 users get a free download and then the app will be paid?
Is it possible to delete an app and re-upload it if something gets wrong while uploading?
Multiple APKs for one application:
Multiple APK support is a feature on Google Play that allows you to
publish different APKs for your application that are each targeted to
different device configurations. Each APK is a complete and
independent version of your application, but they share the same
application listing on Google Play and must share the same package
name and be signed with the same release key.
Besides that, with your developer account you can create multiple application projects and provide your APKs for them of course.
No. After you have released an application for free you can not introduce a price for it. You'd have to create a new app project with a different package name.
This is not naturally supported by the Google Play Store. But you could implement this by writing a counter function that synchronizes over the web. You could also crawl/scrape your app page in the Google Play Store to get the install number. There are various ways.
After you upload your APK, there is some kind of sanity check integrated in the Play Store routine. This should prevent that anything goes wrong during the upload. Anyway, you can also upload a new APK, replacing the previous. That's how app updates work.
Your case overall sounds like you could use In-App-Billing to let your users access most functionality in your app for free, and after a certain time period has passed, offer them the full functionality after a payment.
Keep in mind that it is not a good practice to promote your app for free in the Play Store but then hide everything behind a payment wall inside the app.
Updated answer:
You need to have different package names (i.e. different app projects in your developer account) if you want to offer a free and a paid APK. It's actually a common practice and you'll find many apps in the Play Store that have a "free" and a paid "premium" version.
Very often, it would be easier for you to maintain and to update your app if the premium version only functions as a key (i.e. without actual functionality) that unlocks certain features of the free version. Therefore, you can check in your code if the user has installed the premium version.
Still, it would be more elegant to not "pollute" the Play Store with a dummy premium app and by implementing this with an In-App-Purchase of your premium functionality. Here is a good tutorial (besides the Android guide that I have linked above).
1)Yes, your account can have multiple applications. Or did you mean for the same app multiple apks?
2)No, once an app is free it can't have a price added to it later. If it has a price you can change what it cost though
3)No
4)You can always upload a new version, which seems to be what you want here.