I have completed an application that works fine in development env, both on android emulator and android phone.
I created a keystore, added INTERNET_PERMISSION to my manifest and followed the guide to release pretty much perfectly.
However, when I download the release app from the play store (it is in internal testing), the login API (and presumably the other APIs) do not work and infinitely load.
What did I miss?
The IOS Application is working perfectly in Testflight.
Assuming that you are using firebase.
After deployment to playstore.
Go to Play Console → Open App → Setup (Left panel) → App Integrity
you should be able to see something like this.
add the SHA-1 and SHA-256 fingerprint to the firebase project in firebase console and it should work after that.
Open Firebase Console → Open Project → Project Settings → General, scroll to very last and add these certificates.
UPDATE:
You need to get the new google-services.json from firebase, add it to your app, make new build and re-deploy to playstore with a new version for this to work.
Related
I implemented google login in flutter without using firebase in flutter (google cloud console). It was working in apk then later I needed push notification service for which I used firebase (fcm token and all) then I released the app to playstore but google login does not work. I keep getting apiexception error. Has anybody faced this issue? if yes any help would be highly appreciated.
I do not have a specific answer to your problem but I have also faced this problem once, I accidentally resolved it though.
But Error 12500 is a general error code that may occur when attempting to use the Google Sign-In feature and is caused by a few potensial issues:
An issue with the SHA-1 fingerprint of your app's signing
certificate: To use Google Sign-In, you need to configure your app's
SHA-1 fingerprint and package name in the Firebase console. Make
sure that the fingerprint and package name you have configured in
the Firebase console match the ones you are using to sign your app.
An issue with the Google Services configuration file: Make sure you
have properly added the Google Services configuration file to your
app.
An issue with the Google Play Services library: Make sure you have
the latest version of the Google Play Services library installed in
your app.
An issue with the device or emulator you are using: Make sure you
are testing on a device or emulator that has Google Play Services
installed and is up to date.
Possible fixes to try/check:
Double-check the SHA-1 fingerprint and package name: Make sure that
the SHA-1 fingerprint and package name you have configured in the
Firebase console match the ones you are using to sign your app.
Make sure you have added the Google Services configuration file: The
Google Services configuration file is required for your app to
communicate with Google services, including Google Sign-In. Make
sure you have properly added this file to your app.
Update the Google Play Services library: Make sure you have the
latest version of the Google Play Services library installed in your
app. You can check for updates by going to the "SDK Manager" in
Android Studio.
Test on a device or emulator with Google Play Services installed:
Make sure you are testing on a device or emulator that has Google
Play Services installed and is up to date.
I hope this helps! I will quickly search if I can find any other solution.
When I am updating the logo of the PWA app the icon is not getting updated for the previously installed applications. However for newly installed apps I am getting the correct logo.
Did you try updating the new image icon in manifest.json & then showing a prompt to users to refresh the PWA?
You can try to have a look at the documentation for Android APK (from the question is not clear your target device: web or mobile).
Chrome will periodically compare the locally installed manifest against a copy of the manifest fetched from the network. If any of the properties in the manifest required to add the PWA to the home screen have changed in the network copy, Chrome will request an updated WebAPK, reflecting those new values.
This feature is not yet available for desktop, but planned in a future release.
Do you use any framework (Angular, React) to build your PWA? If you want to read more details about how to install an app on the homescreen or the web manifest properties, you can have a look here.
I have a monolith jhispter app and an ionic-jhipster app both working fine together (Thanks to Matt Raible and JHipster team). And I'm not sure if my problem has anything to do with JHipster.
Since I'm working on windows, I thought maybe I'd be better to use Ionic Pro cloud services to build my app for ios and Android. Please correct me if I'm wrong.
Here is the process I went through:
1-I added my Ionic app on GitHub. So, I'm using GitHub as my Source Control
2-I used "ionic ssh setup" command to create SSH public/private keys and I believe it took care of generating the keys and putting them in the right place I guess I didn't have to generate the SSH keys since it could work just by my user name and password too. Is that right?
3-I went to my app's folder and used "ionic link" to link my existing app to my Ionic Pro dashboard
4-In answer to existing app or new app (which was not clear to me what it's asking for), I chose new app since GaëlMarziou helped me in the comments section to understand there should be an app already created in my Ionic Pro so I can link my local app to it. It took me a while so I understood this prompt is asking about the dashboard app not my local app. I chose "new" since it was the first time I was using my Ionic Pro account and I had no app on it.
5-Then it asked about the source control and I chose GitHub and provided the credentials
6-Then it showed me a list of my repositories on GitHub so I can choose one. But before I do anything it just jumped out with no error/success messages. And I considered it done since I had the same names for my app and GitHub repository and I thought maybe it was smart enough to find the correct repository.
Now, I can see an app in my Ionic Pro dashboard but the build and commit history is empty and it looks like the app is not linked yet.
I tried "git push origin master" to build my app when I was in my Ionic app folder. I assume "origin" would work for any git repository, am I right? It tells me everything is up-to-date and nothing happens in my Ionic Pro dashboard.
Can you upload app in Fastlane command with android and Fastlane app in the google play console or I need to make draft in console before I do?
Fastlane unfortunately can not create an Android app from scratch, as it can with create_app_online (formerly known as produce) for iOS. Google just doesn't offer any API for that.
So yes, you have to at least create the app on the Google Play Console which usually includes uploading a first APK (so the Play Console knows about the package name [com.example.app] or your app) to one of the available lanes (which doesn't have to get published though).
i integrated crashlytics into my unity game, everything worked fine, but then i had to change my package name and my working mail, since then whenever i open the dashboard it gives me an alert "Sorry the app could not be located".
I reinstalled the crashlytics sdk in unity, used new login in prepare fabric tab, but the issue is still there, although the crashlytics seems to be working.
Thanks. Usually this means we aren't detecting the build and run event. Please make sure you are building and running in the relevant IDE. Also, clean your app and dependencies in the native IDE to make sure the bundle ID is updated in all locartions. If you still run into issues, you will need to contact support as your app may be in a weird state in our system.