Suddenly from 3 days, I am not able to use Google Internal App sharing. Loading App sharing page fails with error "unexpected error". Is there anyone else who faced this issue? and have some workaround?
Note:
I am aware that I should raise this issue in Google support, but they are taking too much time to respond. Meanwhile, I am just searching for workarounds or possible reasons for it.
I have tried all possible solutions which are already there on the Web, like incognito mode, clearing cache, etc.
In my network those who already have play store accounts are also getting the same issue.
The API gateway still seems to work. I was able to upload a test apk/aab via fastlane.
It's an easy setup. Then use the upload_to_play_store_internal_app_sharing command to upload the apk/aab
Related
I have an android app developed using Kotlin. Two days back I have uploaded a new version of my app in playstore console. After that update, none of my APIs worked. On having extensive research I found that my param names were changed automatically in the uploaded app.
Actual Params I was sending to API were like this (Same are sent to API in deug app): -
{ "key":"My_Secret_Key", "fname":"First_Name", "lname":"Last_Name" }
But after uploading the playstore my params became like this: -
{ "a":"My_Secret_Key", "b":"First_Name", "c":"Last_Name" }
Please anyone help me in this. I became mad from two days searching the internet for possible answers.
Note:- I have tried uploading the app again and again for atleast 4 to 5 times. But same issue. The same is working, When I pack the apk and use in on my mobile.
Thanks in advance.
*I have tried to upload another app to check whether app uploading error exists. but not of use.
I have also tried logging the requests and responses in logcat as well as toasts in the app. The app from playstore is outputting the different format than that one from my local machine.
I have searched Internet for the same from past two days but of no use.
I have also contacted Google PlayStore Support team on this issue. But still now no response from them.*
If you have some library serializing a class, you may need to exempt that class from minification so the property names are not obfuscated by R8. Use #Keep on any class you are serializing to JSON.
I was regularly uploading apk files to google console's internal app sharing page. However today when I open the the same link i.e. https://play.google.com/console/u/0/internal-app-sharing it has gone blank. I have tried opening it from different browsers etc, nothing works. Is this a new bug or perhaps a downtime?
Same here. Browser dev console shows the app sharing tries to load some data, but can not find it. So someone just broke the code or google server are down. Hopefully not for long, but its already over 20 hours.
It works now, seems there was a temporary blip at their end.
I just published a new app to the Google Play. The problem is that I can't install it in any device because whenever I try to download it, I receive a "Package file is invalid" error.
I tried to clean the Google Play cache and data but it didn't work. I also tried to download it in several different devices and wifi networks. Still I get the error.
I was wondering what could be possible reasons for this error.
When I opened the logcat after trying to download the app from Google Play, I see the following error:
Signature check failed, aboring installation.
What could be causing this? Do I have to use a License Key within my app? Because I didn't do that. I just followed the signing tutorial and used the Android Studio to generate the signed APK.
The Google Play web servers are serving corrupted package files for lots of apps, this weekend. (Lots of people on Twitter are grumbling about it.) While many different error conditions can lead to the "Package file is invalid" and "Signature check failed" error messages, your issue is almost certainly this problem at Google that they'll (hopefully) fix in the next day or two.
I did some investigation into this issue, and found that the corruption was present in the data stream when packet sniffing at my router, before it even reached my devices.
After making changes to my project I have uploaded it to Google Play. Some time after I've tried to update it (Google Play has been already refresh application info and I saw new version number) but I've got an error - "Error retrieving data from server RPC:S-5:AEC-0...". Same report appears on my other devices (5pcs) and users began to mail me with same problem.
Searching gives me this support report. After minutes of googling I found solution - reconnect Google account and it works for me. But I have 40k users - what can I do to help them all? I've implemented new fancy features in game and now they available only for new users.
So, question is - does anybody faced already with such problem? What have you done to solve this?
I just developed my first game on Google Android. I'm trying to submit it the store. I paid my 25$ and went through all the steps.
When I'm at the part where I have to upload screenshots, I get this error:
Unable to parse response. If you have a browser extension or add-on
installed which changes the JSON response, please disable and refresh
this page.
I tried this on Chrome, Firefox, and IE. I don't have any extensions that would be doing any of this.
I've seen some other people post on Stackoverflow, but their posts (from what I could see) are from at last year... so is this a bug everyone is experiencing?
This is still a common issue
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/android-market/technical-help/8emO_DadgxI
My solution was to wait until my account was confirmed.
Try uploading the app by Re-Creating the screenshots. Try creating the screenshot using DDMS.