I have several customized Apps which have different package name/bundle ID. Crash data will be sent to different apps in Fabric Crashlytics dashboard (I guess they have different package name), even if the crash data are same(same type, same exceptions...). My question is: is that possible or is there a way to get the aggregated crash data from these Apps? Thanks.
Mike from Crashlytics and Fabric here.
If you want multiple apps to flow into a single "parent" app on your Fabric dashboard, then here's what you need to do.
First ensure that the parent app has been added to your Fabric dashboard. Then you want to use something like this, depending on the kits of Fabric that you're using:
Fabric.with(new Fabric.Builder().kits(new Crashlytics(), ...).appIdentifier("parent app identifier").build());
One important note is that if you're using Proguard or Dexguard, de-obfuscation will not work correctly on crashes from the child app. Second, currently this only supported on Android.
Related
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 am maintaining a website where people can customize an Android application and download as an apk file.
I need to implement push notifications. I had it implemented in Google Cloud Messaging before. But I am moving to Firebase now.
The problem is that Firebase is configured with specific application ids through google-services.json configuration file. But I need it to run with automatically generated application ids.
I have already tried to change the id in the configuration file. It compiles, but notifications are not delivered.
Please, can anyone tell me if there is a way to make it work?
Edit:
I don't see how my question is related to an Android Datepicker question with nothing to do with Firebase.
There is only one way, you need always create new android app per every unique app id in firebase console. Then download and build new app instance with generated 'json'. Unfortunately, firebase does not provide any API for automatization this, and you have to do it manually every time.
As announced by Google, the Firebase Crash Reporting is joining forces with Fabric. Here's a link
The exact details of how is this going to happen are abstract. But for developers who were using Firebase Crash Reporting, does this mean that they have to create a new account on Fabric and integrate its SDK and remove the one from Firebase?
I know I could wait until Google does the actual implementation, but switching from one SDK to another is not the best approach, if anyone has any insight on this...
The following is the text from the Firebase console when looking at Crash Reporting for the first time without any existing data. There's no additional information available about how exactly it's going to work.
Fabric’s Crashlytics
In the future, Fabric’s Crashlytics will become our primary crash
reporter because it provides advanced tools for solving stability
issues. If you’d like to be an early adopter, you can get a head start
by using Crashlytics on Fabric’s platform.
Crash Reporting
If you prefer to monitor stability in Firebase, you still have access
to Firebase Crash Reporting, which equips you with the essential tools
you need to track and resolve crashes. Eventually, Firebase Crash
Reporting will be seamlessly upgraded to Crashlytics.
according to the Google groups discussion, they recommend ppl to use crashytics for now if they don't have any strong preferences.
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/firebase-talk/_uUuJm0wui8/rHuWYKbABwAJ
Ian Barber
We're mainly trying to signal forward intent - the feature sets are slightly different so I appreciate you may prefer to use Firebase Crash on a new app, but for those with no standing inclination we're recommending they go with crashlytics.
I am developing an application in Firebase. Earlier i was using parse. Parse creates an install object on installation which is then added to the server database.
I have not been able to find anything similar in case of Firebase. So does Firebase has any database with installation properties like the date installed, updated, timezone and version?
Firebase provides developers to analyze the user data, FCM Analytics has been built so wonderfully that you can get every small detail like :
1.the count of different versions of the app installed
2.the device model names.
3.the different OS versions which the app is running on
4.geographical count of the app installs in various countries and many many details
It also provides a facility for crash reporting,by simply adding a dependency in your build.gradle, developers can get a detailed crash report and the full stack trace with line numbers.
Developers can also set something called the user property with which they can analyze the different user usage patterns.
And many more features, all in one single console.
For better understanding you can go through the docs for FCM from the below link:
https://firebase.google.com/docs/analytics/
We're using Fabric Crashlytics with BETA for distribution of our builds and we noticed that it adds certain set of unwanted preferences to app data. One of them is called 'TwitterAdvertisingInfoPreferences' which doesn't seem to be useful for our usage and may become a privacy issue. How can we prevent Crashlytics from adding it?
Mike from Fabric here.
That preference is added when an app starts using Fabric and is one of the identifiers used to help uniquely identify devices to give accurate counts of the number of users affected by crashes. Fabric completely respects the limit ad tracking features on both iOS and Android so if a user reset their advertising identifier then they would be treated as a new user for Crashlytics or Answers.
You should be able to write your own random value to advertising_id in that shared preference in order to block the tracking. I don't know if that would violate Fabric's terms of use.