google-play-console

I'm getting a message saying "An opt-in link will be available here when you publish your app", but I don't know what else I need to do publish my alpha test apk. The release status says "full rollout", which indicates to me that everything is done. I know it takes hours for it to appear but I already waited for days. What do I need to do to get this URL? If I sideload the apk that I created, will it be the same as downloading from the store (in terms of IAP authorisation)? For many developers, it's just a matter of time. Rolling out merely gets you to the Pending publication stage. After some

Can anyone is facing issue in Manage release in Google play store? When I try to upload an app in production track. It's not opening. I am getting this error. An unexpected error occurred. Please try again later. (3200000) I had this about 5-6 hours ago then just gave up after seeing no answers. Tried it just now & it works. I guess something was going wrong internally & I just had to wait it out. I too am having this problem. It seems like a fairly new error code as Google Search only shows a different error code but with the same error message. I've had this happen intermittently for the

From my Google Play console I linked a project. Then I created a service account. Still, when refreshing the console, it still says "There are no service accounts associated with your project." Waited over 24 hours already. The purpose of all that is receipts validation. Picture 1: a linked project: Picture 2: service-account created: I had the same problem, I fixed it this way: When you create a service account in step 2, you need to select a role to grant this service account some permissions, although it shows the step is optional, but for some cases, it's not. If you skip this step, the

i'm desperate. I published the wrong update for an app on the play store by the new Play Developer Console. No i need to rollback my update, simply REMOVING it and re-publish the previous. I cannot understand 2 things: how remove it from the apps versions menu re-publish the previous one Please help me! Thanks in advance In previous versions of Google Developer Console this could be possible unpublising the last .apk and enable to production your desired version but now it can´t be possible. Note that rollbacks aren’t supported due to the app versioning requirements of the Android platform. If

Ok, I want to preface that I have tried multiple solutions such as: Android Studio - Google map still blank on real Android device Android Google Maps API in Release not working I've tried to obtain the SHA1 fingerprint, and added those "Restrictions" to the Google Developer Console API Credentials. Also tried hardcoding the API into the manifest (can't find the link that recommended this). At this point, I've narrowed it down to these possible issues: 1) The keystore I am using has the following line when checking it Signature algorithm name: SHA256withRSA I noticed that many of the solutions

I have an existing app published to production and beta tracks that require SMS permissions. In order to comply with Google's recent policy changes on these permissions I have removed all SMS permissions and have new versions with higher version codes that do NOT require these permissions sitting in both internal-test and alpha tracks. I am unable to either promote these compliant versions to beta or production tracks or upload new higher versions directly to beta or production tracks. I am always presented with the red "changes cannot be saved" bar. I am unable to disable or remove testers

I've been using Google Play app signing, Flutter and VS Code without problems for a while now but since yesterday, every release build for every single Flutter project I'm working on keeps hitting an error and reporting that I'm trying to upload a debug build. "You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode" Even a new app is having same problem I've cleaned the build folder out, I've used the --release flag, neither option worked. One thing I'd like to try is manually compiling app, manually signing then