I'm making a Multiplayer game using Google Play Game Service for connection. I'm at the point where I need to test connection between devices and it seem like I need a different account for each device.
I tried create new Google Account, but Google force me to verify account with a phone number that had not been used to verify another account. I only have one phone number.
The question is: How developer test their apps in this situation ? Do they have multiple phone number just for verify account ? (need to afford multiple phone bills just to keep them active ?)
Some developer are using Android Emulator. Just download the emulator system image that includes the Google Play Services, under Android 4.2.2, from the SDK Manager. However, it is highly recommended to run your game on your physical test device.
Must verify that you have set up the test account that you are using to log in to the app. You don't need to have multiple account, just export an APK and sign it with the same 'certificate' that you used to set up the project in Google Play Developer Console. Then, install the signed APK on the physical test device by using the adb tool.
For more information, use this as your reference: https://developers.google.com/games/services/android/quickstart#top_of_page
Related
I am developing an app for WearOS using Google Fit. In order to use Google Fit, you need to be connected to an Android phone. So, I connected a WearOS emulator on Android Studio to my Android phone (Samsung Galaxy S9+). I am having trouble getting Google Fit code to run. In the Log console on Studio, it tells me that Google Play services is out of date. So, I have been trying to update Google Play services and it is much harder than I thought. I am trying to sign into Google through the emulator itself, that way I can just update Google Play through the Play store (the other methods didn't work). But I can't get my Google account signed in. When I go to sign in on the emulator, it asks me to look at my phone and select an account to be copied over to the emulator. I select my account and it tries to copy the files over. After a few seconds, it fails and all it says is "We couldn't copy your accounts. Make sure your phone has a network connection and is connected to your watch." My phone has a network connection and it is connected to the watch. Has anyone else had this problem? I have tried the other methods that people suggest in order to update Google Play services and none of them work. Thank you.
Here is the Android official site about In App Purchase testing:
https://developer.android.com/google/play/billing/billing_testing#test-purchases-sandbox
Does this mean I have to buy 2 separate Android phones if I want to test my own In app purchases myself? Is it possible for me to personally do it with just one phone.
I am buying an Android phone today. So if I need to do anything special with that phone in setting it up, please let me know.
As I get from description you can setup new test account and use it for testing purposes. To be sure that app will be installed from your test account you can remove your personal account from the device. As for me, I just check the account in Google Play before making purchase.
So you just need to:
Setup test account in the Developer Console.
Add test account to your device
In Google Play choose your test account
Make a test purchase
There is no need in second separate device
Before publishing my app on Google play store, i testing my app on Micromax A63(Android 4.2) it works accurate but after Publishing when i tried to download my app from Google play store it show "device is not compatible "...whats the reason..I'm confused
The possible errors are:
You had another phone on this account (just check it and make login google play with the correct account)
You haven't set correctly something when uploading the apk. Go to the App tab on Google developer console and check if you made available your app for your:
Phone Device
County
Carrier (the mobile network you are paying for your phone service).
In iOS, we have provisional profiles to setup device UDIDs. So, our app will install on devices only which UDIDs are added to provisional profile at development stage. We generally added only customer device. So only customer can install the app. The build will not install any other device.
Is there any feature like above in Android?
NOTE: I knew we have feature in Google Play. But, I need this feature while development.
You can filter which users (not devices) can install your app.
In order to do that, use Google Play Developer Console to publish beta application APK - it can be installed only once user joins specific Google+ community or Google group.
So you have to create such a group or community and make it private - this will allow you to filter out which users can join.
After those users join, you will send them test URL and app will be installed on their devices.
Have a look at this Google Play Help article for more details.
The Play Store's method of doing this is via the new beta-testing feature. You add your testers to a Google+ community, and they get access to your application via the Play Store.
If you don't want to use the Play Store, you can implement a restriction within the app itself to accomplish this. The Identifying App Installations Android Blog post has some great information on how to uniquely identify devices. You can use one of these methods to check the device's identifier against a list of "approved" devices in your Activity's onStart(), and simply call finish() if the user is not "approved."
I uploaded my signed app to the android market, I made some in app contents that I've published (but not the app).
Now I trying to purchase my own products on a real device: do I need to test with the same signed .apk I uploaded to the market? Or a "normal" one I can launch with Eclipse?
Cause when I launch my app with Eclipse and send a requestPurchase(), a pop up tells me that this app version is not ready for market purchase...
You do not need to publish your application to perform end-to-end testing with real product IDs; you only need to upload your application as a draft application. However, you must sign your application with your release key before you upload it as a draft application. Also, the version number of the uploaded application must match the version number of the application you load to your device for testing.
And as it's write on google's doc, the version number of the app on the market and of the app on the device are the same :/
You need to use a signed APK, the same one you uploaded to the app market.
You also need to use a different gmail account to your developer account to access the market.
There's a good tutorial here: Simple In App Billing with some alternative explanations
The testing developer guide is pretty thorough: Testing Billing Statically
You just need to sign the apk (in Eclipse : Android Tools -> Export Signed Application Package...) and reinstall it on the device (with the device attached to USB : adb install _YOUR_APK_).
There's also a way to test your app on the emulator with your own products before going to the real money : android test billing library.
This library is the In-App billing implementation for the emulator, which was tested in the application Horer horaires de RER.