So I built a React Native App with expo. I wanted to add Firebase Analytics so I followed expo's instructions:
https://docs.expo.dev/guides/using-firebase/
My app is already published in Google Play Store and Apple Store, and my Firebase Dashboard only show's Android's analytics. It's as if IOS was never activated, yet I followed the instructions rigorously. My app.json looks like this picture (1):
app.json image
I have both services files in the correct folder, so i don't know what could be going wrong.
I finally could solve this. Apparently Firebase in IOS through Expo, takes a little bit more time to activate. After 2 weeks runing in Android, Firebase Analytics started to run on IOS
Related
We have a project where we use Firebase Crashlytics to collect crash reports from our iOS and Android app. Currently, the console is not showing any crash reports. Initially we assumed something was wrong with our project setup, but today I discovered that Crashlytics actually has been receiving the crash data, since I can see it on the Project Overview page:
However, when I open the Crashlytics page it is empty (it only shown me the guide on how to integrate Crashlytics in your app):
This is the case for both out iOS and Android app. We also have another project that is set up in the same way, but here the reports are shown correctly.
Is there perhaps some console configuration we are missing?
I use some of the Flutter-Fire plugins in my app (I don't use the Firebase Analytics plugin).
I initialize Firebase normally in the main() method like this:
await Firebase.initializeApp();
My problem is that only the Android app is being tracked by Firebase.
The iOS app seems to prevent Firebase from tracking user's data or something...
For example, the Firebase dashboard indicates that the "Daily active users" is about 195 on Android, but 1 or 2 on iOS:
This data can't be true according to the Apple Connect stats and AdMob stats, which shows about 100 active users per day.
Another example is the latest release, which shows me that the latest release for iOS was a few months ago (and again, this is not true - Android and iOS have the same version - 1.3.3):
What could be the problem?
The data was accurate also in iOS a few versions ago, but something has changed...
Just try using the analytics package. It should fix ios statistics
We are using Firebase for push notifications for Android and iOS, and all the notifications are working perfectly.
But when I log into firebase, and try to see the activity in “Streamview”, I see only iOS activity, and nothing for Android.
I do see the activity in Cloud messaging’s Report section, for both iOS and Android.
The application we have built is built using Xamarin forms.
One thing to note from the Firebase console is that it doesn’t appear as though the console recognizes that SDK setup was fully complete.
When going into the link where it says “Continue SDK Setup”.
Finally, when proceeding to step #4 it tries to verify that there has been communication between the app and Google’s servers and it doesn’t seem to find anything and it just sits there looking.
Notifications appear to work, but the app just doesn’t seem to be registering as being used under the Android side.
Any pointers in this direction will be very helpful.
i don't have any idea what is wrong here.
I want to watch complete report of my push notifications sending count, for both platform Android and iOS. but i am getting only iOS report in stream view tab not for Android.
I made the comment above and now I have found an answer, at least for my situation. I had added Xamarin.Firebase.Core to the PCL project as the documentation suggests. Later I saw documentation for Android Java that showed Firebase Core being added to the gradle file at the app level. So I added Xamarin.Firebase.Core NuGet package to the Android project also and now I can see data for Android in the Firebase Console.
I have implemented firebase in my xamarin ios project. FCM token is getting generated, but when I am pushing a notification from firebase console nothing is happening. Can anyone tell me what wrong I am doing? I have used packages such as
Firebase.ios.InstanceID - 2.0.4,
Firebase.ios.Core - 4.0.8,
Firebase.ios.CloudMessaging - 2.0.4
Assuming you are testing it on a physical device and have all the necessary code in place. Make sure you have team id added in project setting at FCM console.
I'm using #ionic-native/firebase plugin in our Ionic App, and crash reporting is included in this plugin. Since Firebase Crash Reporting will no longer be accessible after September 9, we are trying to switch to Firebase Crashlytics. But we're not getting any crash data on Crashlytics dashboard. Here's what I've tried:
First, I followed Get started with Firebase Crashlytics, built and ran our App.
Then I found I could access Crashlytics dashboard, which I thought the SDK was implemented successfully. But after I crashed the app for a few times and waited for at least one day, but nothing showed up on either Crash Reporting or Crashlytics dashboard.
Then, I reversed the changes made to our app and built & ran again, firebase console didn't change back. I found this plugin cordova-plugin-firebase-crash and installed it to my app successfully.
After crashing the app, almost immediately I got the crash data on Crash Reporting dashboard but no crashes on Crashlytics dashboard, but I could see the change on Crash-free statistics graph, which is weird. Now the Crashlytics dashboard looks like this:Crashlytics dashboard
.
My question is: does crashlytics not work when crash reporting is used in the App? Or did I implement crashlytics wrong? Any help would be appreciated.
For those who are stuck with cordova , try get capacitor (which also supports cordova out-of-box)
There’s a plugin for crashlytics
once you got the stuff set up you'll only have to
import { Crashlytics } from 'capacitor-crashlytics';
const crashlytics = new Crashlytics();
//
// log user
crashlytics
.logUser({
name: "John Doe",
email: "john#doe.com",
id: "123"
})
.then(() => alert(`user logged`))
.catch(err => alert(err.message));
//
// force a crash
crashlytics.crash();
Check this out to learn more
https://github.com/stewwan/capacitor-crashlytics
side note: I’m the creator, feel free to PR or file issues.
Finally I found my mistake.
I am using cordova-plugin-firebase and to check the crash I am using the logEvent and logError method of that plugin ttlo check whether it is reflecting to console or not but I for the first time I am not able to see any of the log.. I waited like 24 hours but then I read the documentation about the Non-Fatal error here and check the Firebase-plugin.java and come to conclution that this 2 methods are basically logging the non-fatal error so you have to apply filter in firebase console to see you manual logs like this..
And when you app actually crashed by any reason you will defnalty see the logs in Crashes section..
You can use the Sentry Capacitor plugin here.
Sentry's Capacitor SDK enables automatic reporting of errors,
exceptions, and messages. It includes native crash support on iOS and
Android.
Official doc: https://docs.sentry.io/platforms/javascript/guides/capacitor/