I have added firebase authentication to my flutter project. and when it is running on the emulator. it is perfectly run on it with authentication feature(Login and sign in both are working fine).
but when I use it with my real mobile phone using USB debugging. it is perfectly running, except authentication. every time it is failed to login and sign in with real device
Are you doing both in Debug mode or are you doing Release mode on your device? If so, you might need to add the release SHA keys to Firebase.
cd android ./gradlew :app:signingReport
Related
I'm getting a prompt on my mobile device asking if I want to install the app on my device. I give yes, then nothing happens! for the first time and the app never installed before
I tried to use the cmd to connect my mobile device , I tried to restart my device and I've done the same steps in my device setting again
Is it possible to have a "reserved" emualtor in the cloud where I can save the emulator state and re-access it?
I tried Browserstack however at each test run, the emulator that I use is brand new.
The problem with that is that each time I need to log in to the app which requires a 2 step verification with SMS. If I'm able to once log in to the app with my account and save the state (like what I can do with a local emulator with Android Studio), then I can launch my Appium tests in the future with no issue and be automatically log in my app account.
I am using Firebase Authentication for my flutter application. When I try to login with my virtual device it works, but if I try to login with my real device or Chrome, nothing happens if I press the button. There is no error in the logs.
Creating a release apk and using the release version of the sha keys from firebase? It solved the problem for me when I had it.
On this website (https://ionicframework.com/docs/intro/deploying/) I read that I should give this command on the command prompt: ionic cordova run android --prod --release
I tried it but it only tried to start the app on an emulator (I have some problems with it, so it didn't actually start the emulator). Does this command also create a file I can put on my mobile and install the app? I don't want to put the app on Google play, just on my mobile.
I tried putting the android-debug.apk on my mobile and running it but my mobile couldn't install it (.../platforms/android/build/outputs/apk/android-debug.apk)
I'm not trying to test the app on my mobile, I'm trying to install it.
If you want to deploy the apk to your device
ionic cordova run android --device is indeed correct. (try adding --device)
You only need --prod --release when building for production (longer buildtime).
Before running (= building, installing and starting your app) check if your device has USB-debugging enabled. You can check if your device is connected by running adb devices. Since the run command includes building, yes run should create a apk for you.
As you said you also could install the apk manually. Here make sure to use the correct apk. android-debug.apk is the development build (no --release tag) and since your trying to run a production one (--release) you are looking for android-release.apk or android-release-unsigned.apk.
go to settings -> security in your phone then check Unknown sources (Allow installation of apps from sources other than the play store) and try to put the android-debug.apk again. this should work
Hey Im trying to Remote debug an Ionic Application, it was working recently, but now the device shows on Chrome Remote devices but when i click the device the app process wont show. it will show other mobile chrome tab Processes but not the Ionic app.
any clues ?
I fixed this, It was my fault, I built a release apk and was expecting a debug mode. When you build without the --release, It works