I want to use Crashlytics for crashes only and disable any analytics events for my iOS app. I disabled everything I could find in setting:
but I still see that the app is hitting https://e.crashlytics.com/spi/v2/events endpoint regularly and posting some data.
I am wondering if there is a way to disable sending any events apart from crashes. In addition to it will it have more granular settings after migration to Firebase?
Thanks.
Related
I'm a new programmer. I've launched my first app on the Apple App Store and I incorporated Firebase to do user authentication. But I'm completely new to Firebase, so I thought that incorporating Firebase as a Swift Package would automatically enable Firebase Analytics such as in_app_purchase or first_open. I've noticed that those events don't seem to be registering even though I have users using the app. (screenshot of the firebase analytics page in the link below)
Would anyone know what I'm missing here? Any guidance would be appreciated since I'm new to this.
The most common cause is not adding the -ObjC to the Other Linker Flags options in the Xcode Build Settings tab. More details at https://github.com/firebase/firebase-ios-sdk/blob/master/SwiftPackageManager.md.
I followed all the Fabric documentation concerning crash reports for iOS.
I can see my first crash test on the dashboard, but now the App is on the AppStore, and I see no crashes, no active users, no data at all on the Fabric App.
But I know there are a lot of users right now, we can see all the stats for Android.
How can we make this solution working for iOS ?
you might want to check 3 things:
missing dYSIM
runscript
plist
I have enabled Flurry crash analytics in my app. My app crashes but it is not reported under the Errors section of Flurry Dashboard , but can be seen as exception logs under the "errors" option of Technical section.
How long will it take to report ?
Regarding Flurry, I dont know if the behavior is sent straightaway. In the case of flurry analytics, is not straightaway and you have to wait sometime. My questions now are : have you configured correctly the application with your flurry key? does the application ask you to send the report once it has happened and you reopen the app? Sometimes, and it happens in all the frameworks like crashlytics, if the app doesnt ask you to send the report, it can mean a hardware problem has happened (external to the app) and it wont be sent to the backend. Take a look in all the steps.
Does anyone know when GoogleAnalytics iOS SDK v3 sends the crash to their servers (when app is on AppStore)?
Does it send when the app crashes, or when the user reopens it?
The problem is that, I'm viewing a lot of crashes from a bug that I think I solved, and on HockeyApp I'm not receiving anymore of these.
Thanks
Some points:
Crash reports are usually send the next time the app starts. Trying to send them at crash time may cause big harm to an app and its data. As far as I know GoogleAnalytics only sends reports on the next startup.
Google Analytics can only catch crashes caused by exceptions! In addition, any other exception handler will NOT be able to catch the exception! This is why you only see reports in Google Analytics but not in HockeyApp. This will happen with any other 3rd party SDK too. Usually the last crash reporting SDK you setup in your app wins.
You can test this yourself by using the CrashProbe open source project and include the SDK or SDKs you want to use. And then monitor the behavior for various crash types.
From my personal experience, Google Analytics is not good in capturing crash report as I think the crash report might not be real time . Personally, I like bugsense and I am using paid version of Bugsense. Its free version is good for most apps as well. May be you can try out the free version.
I am currently working on a project using Crashlytics and I'd like to try Flurry's new crash analytics. I haven't been able to find any information as to whether it's possible to set up both Crashlytics and Flurry error reporting in the same application. Is it possible to run both? Would there be any drawbacks to doing so?
EDIT:
Here's the reply from Flurry:
You can use only 1 crash reporting tool. So, if you have crash analytics, you cannot use any other tool. Else, crash analytics will not report crashes.
Using two crash analytics providers is not recommended for iOS, since Apple only allows you to set one exception handler in your app at a time.
For Android, using multiple crash analytics providers is usually okay.
http://support.flurry.com/index.php?title=Analytics/FAQ/CrashAnalytics#But_I_use_another_Crash_Analytics_SDK.