I have apps published before August 2021 but I am not getting Google Play Signing option in my Google Play Console. Nowhere do I find the option to upload PEPK file.
How to enable sign in?
Google Play Console
I'm trying to opt out from App signing in Play Console but there is no option to opt-out. As you can see in pictures i have Change signing key but not opt out. Even when i open Change Signing Key i'm given option to upload my key but not to opt out. Is there any possibility to opt out now or this is mandatory and opt-out is not an option anymore?
Reading Google's Play Console Help article on Use Play App Signing there is a paragraph that states:
Note: For apps created before August 2021, you can still upload an APK and manage your own keys instead of using Play App Signing and publishing with an Android App Bundle
To me that reads from August 2021 (i.e. now), you won't be able to upload an APK and you also won't be able to manage your own keys. They should probably have split that sentence into two to make it clear that both options will no longer be available from August 2021.
Here's the link for reference: https://support.google.com/googleplay/android-developer/answer/9842756
I published my mobile app in Google play console recently. Regarding crash logs in Android vitals I'm doing bit investigation on it and I have some doubts,
Is Google play console capable of log offline crashes when device back to online ?
I could see the crashes updated in Google Play console even I'm working in development apk with my real mobile device, How Google Play console logs the crashes occured it local apk, it is only for the apps downloaded from Google Play store right ?
Please anyone clarify my above questions since I'm new to mobile app development area
.
Yes, Google will collect crashes even when they occur offline.
Google will collect crashes even if the app is not installed via Play Store. You can however filter those crashes in the Play Console directly by adding the filter "Installed from Google Play":
I created a progressive web app, and it works perfectly. It prompts for installation and it saves the link on the android home and it shows no url address bar.
Then I used PWA2APK (https://appmaker.xyz/pwa-to-apk/) to create an APK and deploy on play store.
Once built, I downloaded the assetlinks.json, added the certificate SHA-256 modifying the assetlinks.json in this way (I changed values):
[
{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "xyz.appmaker.pblx",
"sha256_cert_fingerprints": ["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","SHA256: BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
}
}
]
Then I pushed it online, and verified that www.exemple.com/.well-known/assetlinks.json show the values in the browser.
The package name is the same of the APK, and the SHA-256 is the Application signing certificate.
I also added icons, screen capture and all the necessary stuff. the total workflow is validated. So once deployed a version for an internal test, I expected it to work correctly, but it doesn't. The application is installed with a default icon, it shows the rl address bar and it has some load problems.
Did anybody experienced the same issues? How did you solve it?
Thanks.
I am part of the team that build this tool. And as for the question, this can be solved by removing SHA256 from following.
Before:
"sha256_cert_fingerprints":
["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","SHA256:
BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
After
"sha256_cert_fingerprints": ["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
This should fix the issues you had with the address bar.
And yes, feel free to reach out in support forum anytime. Happy to help and thanks for using PWA2APK
This is just speculation, but are you using Google Play App Signing? With Google Play App Signing the app certificate should be the one Google signs your app with, not the one you sign with to upload to Google. The documentation is here. Specifically it says, under step 3 of the "New Apps" section.
Step 3: Register your app signing key with API providers
If your app uses any APIs, you usually need to register the certificate of the key Google signs your app with for authentication purposes using the fingerprint of the certificate. Here’s where to find the certificate:
Sign in to your Play Console.
Select an app.
At the left menu, select Release management > App signing.
Copy the fingerprints (MD5, SHA-1 and SHA-256) of your app signing certificate.
If the API provider requires a different type of fingerprint, you can also download the original certificate in .der format and convert it using the transformation tools that the API provider requires.
If you get the SHA-256 as described above and put it in your JSON instead it might work.
Simply copy your sha256 key from play console and paste after your original key in "sha256_cert_fingerprints" and build and deploy.
After uninstall and install the app from playstore
Yesterday i have uploaded my App on google play console. Today in the console it showing that my app is published. When i click on "show" in Google Play it shows my app. But:
there is no another app showing in suggestion
as well as when i click on my account in google play it shows that the account not found on google play
The issue is that in google console it also not showing statistics of my app.
This is a link to my App but when click on account NightmareSolution it not found on server
As #Muhammad Babar suggested, you need to wait since it may take some days until you see the app in Google Play Store properly. Please check this link for the list of duplicate questions. When you first publish your application, you need to be patient and wait for Google Play to update and process your application.