What I need to do is to create an application in which few of the segments should be invisible for user in published version.However when user checkouts In App billing purchase module he would be able to access these segments(Which is basically a number of Screens).
As of Now I am able to integrate the Standard In-App billing demo application in my application.But I am still confused how to make these Segments available for the purchaser as soon as he successfully checkout through In-App billing module. I am afraid of publishing app as it is recommended as per Android Developer Guide. I've a perception in my mind that how it would be working but want to take live experience.
Can anybody tell me the proper procedure and guidance for testing the Application apparently before it to be delivered to client.
Any help would be highly appretiated.
Go through with this link :
Implementing In-app Billing (IAB Version 3)
It is having good explanation with good piece of example code.
You can set up test accounts also to test in-app before delivered to client.
Setting Up Test Accounts
Thanks.
You are allowed to enter demo users for In app billing. You can enter the email ids with testing privileges there.
Go to Settings tab in Developer Console where you'll find "Gmail accounts with testing access", which is defined as:
License Testing - In addition to the owner of this console the following users will get the License test response from the application. They can also make in-app purchases from APKs that have been uploaded but not been published yet.
Related
I have read lot of documentation and blogs but could not find a concrete answer.
So I have an app where I need to integrate in-app weekly subscription and also have a backend server that stores user data so when the purchase is made I send data to the server that user is subscribed and update database and give the user access to the app.
I wanted to know how to handle the cases when a subscription is cancelled or ended. How to check that in the app?
What is the best architecture look like for In-app billing and Server?
Google Play doesn't have important documentation and even the lastest documentation for Billing 3.0 has some bugs, but if you are just looking for process and can figure out the code for yourself here is the in-app subscription architecture described by google on their official Android Developers channel on youtube. https://www.youtube.com/playlist?list=PLWz5rJ2EKKc9J8ylTbNo1mnwciEyMbxZG
I have to integrate In-app subscription in my android application. For that, I have followed all the instructions as per this URL. I also getting my subscription product information with price but I can not getting dialog for testing account.For example, It always ask me to use Payment methods for real transactions as per below image:.When I have added my credit card information, It have done real transaction and debited my money. I want to get test subscription instead of real transactions. I also refer this reference link. Please give me any suggestion for where I am doing wrong.
Finally, I resolved the issue.I have to remove permissions for test accounts, which I refer from this link
Test accounts have three limitations:
Test account users can make purchase requests only within apps that
are already uploaded to your publisher account (although the app
doesn't need to be published).
Test accounts can only be used to purchase items that are listed
(and published) in an app's product list
Test account users do not have access to your publisher account and
cannot upload apps to your publisher account.
I'm a beginner learning android app development.
I have a requirement for a user to be able to Read messages (just the body content - text only) from a Gmail account (Read-only mail extraction?) and save the email content within the app.
I don't need to retrieve messages when the user is not actively using the app.
The app and SQLite database I am building sits on the phones internal local storage. I do not have a backend server.
I have looked at the Gmail API tutorial here: https://developers.google.com/gmail/api/guides/
As I understand, I need to use the Gmail API and ensure that a user of my app can authenticate as a Gmail user.
Is anyone able to advise:
1) if this is feasible to do without a back end server?
2) any tutorials as to how to approach this, or would you recommend just working through the material I listed above?
3) (I understand this is highly subjective) how substantial a task this is to undertake for a learner (This is an educational project, so I am limited by time - if it takes me more than 3-4 days I will run out of time!) An idea as to how long it might take someone who is experienced would help me to grasp the scale of the task.
Google uses Oauth2 to authenticate and track applications connected with a user's account. You will need to get a security key for app from google. Because you do not have server, you will want to get a client only key and not the service key. You can get the client key by going to the Google API Console. For help about how to let the user sign-in to their account you can look at this Android tutorials here. After you get the google sign-in working you can continue on to getting the Gmail messages.
It may seem like a complicated process, but you should be able to have in working in a short amount of time if you go through the tutorials on Google's developer's site. I got a similar app working in only about an hour. To add a nice user interface will take longer, but thats up to you.
I have used AccountManager to handle user login with Google account. Because this software is in development, I need to test it again and again. I'd like to know, how do I remove these rights from an app to reauthenticate it for test purposes?
I've done the authentication as showed in this Google developers document. It produces an authentication screen like this
Go to https://security.google.com/settings/security and click on "review permissions" next to "Connected sites and applications."
Here you can revoke access to your Google account for third-party sites and apps. You should then be able to re-request access via your app.
The most reliable method that I've found is to remove the Google account from the device and add it again. The next time your app is run, it will show the "This app would like to..." screen again.
I have two Google accounts on each of my test devices and can quickly delete/add the second (less frequently used) one when I'm testing authentication workflows.
I'm working on connecting an android app in Java with google app engine. This is my first time doing it. I watched and did the same thing that it was done in this video:
http://www.youtube.com/watch?v=M7SxNNC429U
I have been working and I'm getting the same problem. When creating the project and running it, it runs but it shows me a message that I have to create/add an account, I already register it when creating the project. When I enter my gmail account info it shows me a message saying: "Can not connect with the server". I'm not sure what it is happening, please a ed help on it, thanks for you time and patience.
Careful C2DM is deprecated in favor of Google Cloud Messaging and the latest Google plugin doesn't have the wizard for creating a App engine connected android project
That video is awesome, but there's some useful documentation for AppEngine Connected Android apps too. Specifically in the Creating A New Project section, it explicitly states,
Important: You must sign up for a C2DM account using the same Google account that you use for the Android application you are developing and for the GPE plugin.
You can go back and edit things later so that the account you're logging into the app with is separate from the role account being used for C2DM. But for the code generated by the plugin, they have to be the same account. Also, don't forget you actually have to sign up for C2DM, as it isn't enabled in all accounts by default.