I have two projects.
connected like this document.
connected with Frabric plugin on Android Studio.
First of all, My colleague connected the first way. It worked fine. After that I needed to create a new project for test. And I connected Crashlystics with Fabric plugin(I didn't know how my colleague connected at that time.)
Now, I needed to connect Crashlystics to the original version(which is 1).
However, It shows the crash graphs, But I don't get any reporting like which line got which error. I checked my test project and it gets the reporting.
So, I disconnected my account connected to Fabric and my app. And then, I get 0 reporting in both project.
At the moment, My setting is just like the document. And of course, I have google-services.json file correctly.
How can I solve this problem?
The two methods that you've followed would have crash reporting at different places.
1st one would report everything on Firebase Console.
2nd would report everything on Fabric dashboard.
To connect fabric to firebase you would just need to migrate your app over to firebase with just a few button clicks and no code change.
My assumption is that you might not have stripped out the Fabric API Key (In your AndroidManifest.xml file) from your code hence the reports are not coming in at firebase console.
Related
I am trying to link my Firebase project to BigQuery. It seems to not work and every time clicking the "Link to BigQuery" fails with this error (screenshot attached) even though I am the owner of the project. I could not find any more details about what is the issue. The same project successfully links to Google Analytics. Would be great to get any inputs on fixing this issue.
Based on inputs from firebase support team I was able to resolve this issue. We need to enable Firebase Management API in https://console.cloud.google.com/. I have put down the error response which you can lookout if the error occurs.
We're using Firebases authentication for logging in and registering accounts. For some reason, one person on the team (member 1) is able to use it properly but when myself or another team member (member 3) tries to test it by creating an account or logging in we get the error
com.google.firebase.auth.FirebaseAuthException: The given sign-in
provider is disabled for this Firebase project. Enable it in the
Firebase console, under the sign-in method tab of the Auth section.
We have tried everything we can think of to fix this error. Email/password sign-in is enabled in the firebase project. We've tried completely copying the files on his machine to ours and it still won't work. What's even odder is that it works fine on member 3's laptop, but not his desktop. I've also had member 1 send me a build from his machine onto my phone and it will work then. I tried completely reinstalling Android Studio as well. I'm not even sure what files to show because I can't imagine it's a problem with the code, since it works perfectly fine for member 1 and member 3 on his laptop. If there's any file you need to see I'll be glad to add it.
That might actually be working in the third members laptop because he would have linked the firebase with your project and put the SHA-1 of his laptop, If you want that to work with yours as well then you need to go to firebase console and add SHA-1 to the console to have it work. try this.
And if it helps please do accept i, if I didnt help let me know and il check more for you.
I have Firebase Crashlytics set up correctly on my application. But I have been unable to access my Crashlytics dashboard on Firebase.
It keeps taking me to this page to this page up fabric which I have been unable to. Is there a way around this.
Fabric/Firebaser here - hopefully this helps anyone who might run into something like this in the future. More clarification has been added to this particular screen since this question's creation as well.
One reason why this can happen is some sort of misstep in the migration process. If you have a Fabric app and are attempting to migrate to Firebase Crashlytics, you should complete the clickthrough migration and then you should be able to entirely skip seeing these options once that's complete. No other code changes are required. You will also be linked to the clickthrough migration if you choose option 1 on step 1 of the above view.
Other than that, ensure that you're installing Crashlytics correctly via these instructions. You can also click "Test your Implementation" at the bottom of that page to see how you can enable Crashlytics debug logging (to verify in your Xcode logs if Crashlytics is communicating with the server) and perform a test crash.
I have an Android app which uses Firebase Auth, and while fixing some issues I had, I noticed that there is no need to add the file google-services.json to the project.
My issue was the following. I perform a sign-in via Google Sign-In, and in the GSO (Google Sign-In Options) I specify
gsob.requestIdToken(".....apps.googleusercontent.com");
gsob.requestEmail();
because I want an idToken which I then can pass to the Firebase SDK in order to sign the user into Firebase (I'm using it this way for historical reasons).
It had stopped working which was the reason why I was meddling around with the google-services.json file, since I had deleted a Client-ID in console.developers.google.com and thought I made a mistake.
While being at removing stuff, I also removed an entry
<meta-data android:name="identitytoolkit.server_client_id" android:value="....apps.googleusercontent.com" />
and some more identitytoolkit metadata entries from the Manifest.
In the end the only thing that would matter was that the correct client-id is passed to gsob.requestIdToken(".....apps.googleusercontent.com");
I'm not sure if Google had some hiccups with the idTokens between Google Sing-In and Firebase during these last two days, but in the end I think I really didn't change anything to make it work again.
So the last couple of minutes I was reading through the Firebase documentation, and read that there are now two options for adding Firebase to an Android app, one is the one I used before, and then there's a new option to use the Firebase Assistant.
I never used the Firebase Assistant, but am wondering if it has been enabled automatically in my app (I never clicked "Click Connect to Firebase to register your app with an existing or new Firebase project and to automatically add the necessary files and code to your Android project.")
How can I find out if something in Android Studio has been altered to add my Firebase configuration automatically? Where do I know which client-id's it's using?
I'm asking because even the email-based authentication with Firebase (which is not using Google Sign-In explicitly) is working in the app, and there are is no json file or other client-id's in the Manifest or in the code which could be used for this.
Nothing has changed in the setup instructions. You either need to have the Play services plugin and google-server.json present, or you need to duplicate its work manually. The only ways to manually duplicate its work are to add the specific string resources to your app that it requires, or call initalizeApp with your specific settings. There are currently no alternatives.
I've been following the docs here and have made it all the way to the point where I've installed it and am trying to send an error. I added a button to my page that when pressed just does:
throw new Error('Test Error for Crashlytics'). I've got it running in my simulator as well as an ad-hoc install of the app onto my phone, but no matter how many times I make my app error, the Crashlytics page in Firebase just shows
I've seen that this can take some time, but I've been waiting about 2 hours now since the first error and about 30 min since I last tried and still nothing. Not really to sure what to try next, I can't seem to find any documentation on how to possibly debug what is going on as well.
Firebase crashlytics will automatically record crashes so you won't need to add anything, unless you have custom requirement. For that you need to follow the this documentation.
And for forcing your app to crash, actually you can use
Crashlytics.getInstance().crash();
here is the tutorial from firebase documentation.