I am trying to publish my game services using Play developer's console.
I am getting the "Ready to publish" button, and all lights are green but when I click the button I get a "An unexpected error occurred. Please try again later." red message on the top of the screen.
I have tried logging out, switching browsers and updating some details but nothing helps.
Here is a screen shot of the situation:
Anyone have an idea what I might try to do in order to resolve this?
So I have managed to solve this, and here is what I have done if anyone encounters the same problem. I have read and tried many solutions that were suggested in other posts and contacted Google but nothing worked.
The solution was to remove the linked apps, and add both of them again. I have 2 linked apps, one with the production certificate and one with the debug certificate.
This solution does not make any sense to me, and I guess it is some internal error on Google's side.
Related
My app publish rejected due to this error but I can not find the source probably I am looking in wrong section.I am not native can anyone explain what this error does and how I fix it ?
Screenshot
EDİT:
Sorry I didnt realize there is attachment , I belive I have to add contact info(my gmail) to main screen I probably add with info button or something , gladly accepting ideas.
Attachment
look at the final of the page (the page where you took the screenshot) there is an attached button where google play shows you the exact problem.
Also go to console -> all my apps -> developer account and check that you fill all the information
I've updated the icon for my bot in the Azure portal about 35 hours ago, but it's still showing the old one for new messages sent from the bot. Surely it should have changed by now? Is there any issue with this currently?
It's correct in the Azure portal in the "Test in Web Chat", but Teams is still showing the old icon, even for new messages.
Update:
It's been a few days now, and the image finally changed, but now it's totally corrupted. Is there a way to see what's wrong with my PNG? Is there an issue with the bot framework/Teams of some sort? See images below:
Error:
Original Icon (I don't know if SO changes the file in any way, but presumably not)
Update: I've now modified my bot in the Azure portal to use the exact same icon as another bot which is working fine, and it's still broken, so I'm thinking there is an issue with the bot framework/Teams in some way at the moment.
What I've encountered from experience is that when updating the bot's info in "Bot App Registration" such as icon and display name.
You can either wait a couple days and see if it fixes itself.
I've consistently been able to get it to update sooner by logging in and out of Teams as well as closing it.
I have a feeling that it's related to the cache since Teams is built with Electron. Some other post mentioned this and there's no "official" surefire way to do this. Playing with the manifest also does not seem to affect it to update sooner.
TL;DR
Log in and out of Teams, close it. If using web version, clear the cache. Log back in.
Good luck!
Try reinstalling the application on Teams, sometimes it takes time.
I'm trying to upload an app to Google Play-Store but I'm getting the error message below without any further comments:
Couldn't upload. Try again.
I have uploaded numerous apps to Play-Store in the past. I'm not exactly sure why this one isn't going through. The apk in question is a signed-release apk. I'd appreciate some help on this. Kindly find below a screenshot from the Play Store page.
This was a very weird fix but I eventually did it by switching to the old console. The apk file uploaded successfully immediately I did. The link to the old console can be found on the navigation drawer to the left.
Drawer > Use classic Play Console
Sadly, Google is killing the old console as from November 2, 2020.
Using the Incognito Mode worked for me as per this Answer
I was able to fix it, here are steps you need to perform
Switch to old console
Remove any old pending releases
Switch back to new console
It should work now!
When I try to publish a release in the Google Play Console, I constantly get this error:
Your app cannot be published yet. Complete the steps listed on the Dashboard.
And yes, I have indeed completed all the steps listed in the dashboard. I am using the new Play Console Beta, this is possibly related. What do I need to do before I can publish a release? Is there a hidden step?
After some searching, I found the button 'Use classic Play Console'. Apparently there are some steps to be finished that are simply not visible in the Beta:
Click on Use classic Play Console
Go to Pricing & distribution
Check the Content guidelines checkmark
Check the US export laws checkmark
Press Save draft
And you're good to go!
I had that problem and fix it. the problem caused by google console because they added one additional task in the app content about wither your app is consider a news app or not. so go to the inbox in your app and you will find that message from google click and you will be leaded to the content that you should fill. I hope that help any one having that issue.
I also had this problem. It was regarding setting your app as free from the App Pricing section as my application was free. So after setting that, I released my app.
I am running into a recurring issue with the Marketplace Listing/SDK.
Anytime something minor is changed, the Contextual gadget disappears from the clients Gmail.
When we look at the Marketplace App in the clients Google Apps Admin everything is fine.
However if we go to "Data Access" and revoke permission and re-grant it, fairly soon the gadget will reappear.
This has to be done for any customer that has the App installed.
An example is fixing the issue described in the following link where we have to "check off" Enable individual Install.
"Integrate with Google" button disappeared
Google has made a change that means we need to adjust our settings and this whole "regrant" process is initiated.
Is this a bug or an undocumented feature? has anybody else encountered this???
Thanks for your input,
Paul C
This is caused by a known bug. We hope to have the fix in production next week.