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.
Related
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
I've scoured the internet for the past 4 hours, but can't find any reliable information. I want to allow the user to download and install an APK via QR Code only - WITHOUT opening Google Play Store. Reasons behind it are 100% legit, as the devices will only be a showcase devices, without any additional features or any use by private or corporate entities.
I hoped to solve this problem by putting a download APK link, but some sources say it will not work that way. Thank you for all your help and I am sorry if my searches didn't turn a result that's already out there, I hope you'll forgive me lol
Best,
Luke
At my company we use Google Play's internal app sharing links to provide builds to QA. As of an hour or so ago, opening any link now fails, showing this error inside Google Play:
To view this content, install and set up a web browsing app.
This happens on every device & OS tested, all of which previously handled links perfectly.
We are not using opt-in testing, only 1 google account is whitelisted for the builds.
The links are in the format https://play.google.com/apps/test/xxxxx/xxxx-xxxx_xxxx.
Since it happened on all devices at the same time, I suspect it's a remote config switch.
Is there any known workaround?
Note: None of these suggested solutions work, as they just let you open the URL in the browser. That doesn't help, as the URL just provides a link to open it in the Play Store.
Try directly this if link is originated from an app for Android to handle:
market://details?id=<package_name>
Note: There's no domain and host.
It was caused by a temporary outage on Google's end. It resolved itself a few hours later.
While working on a feature for my app with AppLinks for Android. I have realized that it actually works without using the assetlinks.json file.
At first, I thought that this was because my app was an app for debug purpose, which wasn't signed and published through the store and that for testing purposed, Google decided to give us some space to work.
The day I released my app arrived, I put my app through Beta, installed my app from the store and tapped on a https://example.com and I was very surprised to see that I got asked which app I wanted to open this URL even though I had not make the assetlinks.json available from https://example.com/.well-known/assetlink.json.
Is there an explanation to that ?
Maybe the check is totally asynchronous and if at some point Google makes the check and find out you don't have this file, they shut it down until you fix it and ou have to wait until the next time they check you out ?
By the way, i have implemented the same functionality with iOS and in a very Apple-ish way, you really can't get around putting you apple-app-site-association file to the right spot and make it available from the right endpoint.
Thanks for the explanation :)
Guillaume.
Is there an explanation to that ?
What you describe has been the behavior since API Level 1 in 2008.
I was very surprised to see that I got asked which app I wanted to open this URL
This is called a "chooser". The point behind assetlinks.json is to avoid the chooser and drive straight to your app.
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.