Develop Reference

Google Play Console OnePlatformRpcException

I add a new app and I can't do anything because of the above error on google play console
OnePlatformRpcException: status: code: 13 message: Internal error encountered. , request: RpcRequestz_play.console.apps.api.pricing.PricingService_GetBillableCountries, httpStatus: 500, stackTrace: null
Can anyone come across this problem and solve it? I think this is an error from Google.

GoogleAPI refusing apps Artifact upgrade problem

Until a few days ago i was able to upload new versions of my apps to the app store through the googleAPI with no problem but now I am getting the following error (with no code changes)
com.google.api.client.googleapis.json.GoogleJsonResponseException: 403 Forbidden
{
"code" : 403,
"errors" : [ {
"domain" : "androidpublisher",
"message" : "Artifact upgrade problem with 97.",
"reason" : "apkUpgrade"
} ],
"message" : "Artifact upgrade problem with 97."
}
My app version is not 97, its 66 I have no idea where that number came from. The current app version in the store is below 66. I cannot find anything like this problem on the web
Edit: I forgot to mention that if i manually upload the APK it works fine

I also had the same problem, so I took the APK manually to the Play Store, and was greeted with the following:
Warnings Your app currently targets API level 22 and must target at
least API level 26 to ensure it is built on the latest APIs optimized
for security and performance.
I updated my targetSdkVersion to 26, then all was right with the world.

Android Studio - Signed SDK, task failed 'android:mergeReleaseResources"

As the title says, when I run Build->Generate signed APK (The APK I am going to upload to the google play store) -> Build Type = release, Signature V1 and V2 both checked -> Finish I get the error
org.gradle.api.tasks.TaskExecutionException: Execution failed for task
':android:mergeReleaseResources'
I have googled for quite some time and can't find another person who had the same exact error as me.
I have a correctly generated Keystore, the passwords are correct (I have seen the error the gradle spits out when its an incorrect password, and it's different)
I have the log coppied to a google doc if you want to take a look. I don't understand log language... https://docs.google.com/document/d/10jr5y9bxCPuNsB484k2Gysv4MeMs4pNJK8oBVMuYMLA/edit?usp=sharing
What does this error message mean, and what can I do to fix it?
Thanks in advance

Android Google API Debug App working but not signed App

My Android App seems to be working fine by using code given from: google api webpage
when running in debug mode but once I generated a signed apk, and uploaded the app to the app store, the app will not log in properly. Is there any way of fixing this, or even debugging an installed app as logs will not show up in android studio?
Thanks so much.

I had same issue with Google Map Api... I had solve this.
You have to generate sha-1 key using your keystore (this keystore use/ generate when you generate signed apk).
May be, the SHA1 currently you are using for debugging purpose .
So when you are creating a signed apk u have one kestore file. try to generate new SHA1 key with this new keaystore file.
then using this keystore file create API key for signed apk.
replace debug API key already stored in manifest file and google API console with the new one.
It will work.
thanks

Your app may need to get verified by Google for the signed app to work. They really do a poor job on error messages and making the documentation clear. In fact, the error message that I was receiving was not even listed on their website!
https://developers.google.com/drive/api/v3/handle-errors
403 Forbidden
{
"errors" : [ {
"domain" : "usageLimits",
"reason" : "dailyLimitExceededUnreg",
"message" : "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.",
"extendedHelp" : "https://code.google.com/apis/console"
} ],
"code" : 403,
"message" : "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
}

Android failing to download obb file using unity

I have a unity project for android which is larger than 50MB and so must be split. I have had working apt splitting for a couple months now. Starting a few days ago I mad a couple changes which were purely aesthetic. I uploaded the new build and now(days after the api and obb files were uploaded) I receive an error at the download point on the device "Download failed because the resources could not be found."
I manually added the obb file to the device and it worked, I have tried re uploading the apk and bob files with minor changes and still after a day of waiting see the same errors.
viewing with logcat I see these errors when i try to download
I/LicenseChecker(20270): Binding to licensing service.
W/ContextImpl(20270): Implicit intents with startService are not safe: Intent { act=com.android.vending.licensing.ILicensingService } android.content.ContextWrapper.bindService:517 com.unity3d.plugin.downloader.c.j.a:-1 com.unity3d.plugin.downloader.b.s.run:-1
I/LicenseChecker(20270): Calling checkLicense on service for [my project com]
I/LicenseChecker(20270): Start monitoring timeout.
W/GLSUser (26959): GoogleAccountDataService.getToken()
I/qtaguid (18936): Failed write_ctrl(u 53) res=-1 errno=22
I/qtaguid (18936): Untagging socket 53 failed errno=-22
W/NetworkManagementSocketTagger(18936): untagSocket(53) failed with errno -22
I/ElegantRequestDirector(18936): I/O exception (org.apache.http.NoHttpResponseException) caught when processing request: The target server failed to respond
I/ElegantRequestDirector(18936): Retrying request
I/LicenseChecker(20270): Received response.
I/LicenseChecker(20270): Clearing timeout.
Its not obvious to me what I did to make obb downloading stop working. I don't know enough about the error messages to pick anything out of it.
What can I do to make it download the bob files again?

In case anyone else runs into this here was my solution. It looks like Google made a policy change.
"To test your application's implementation of the manual download procedure, you can publish it to the alpha or beta channel, so it will only be available to authorized testers. If everything works as expected, your application should begin downloading the expansion files as soon as the main activity starts.
Note: Previously you could test an app by uploading an unpublished "draft" version. This functionality is no longer supported; instead, you must publish it to the alpha or beta distribution channel. For more information, see Draft Apps are No Longer Supported."
so now you need to publish your alpha/beta builds before you can download the files.