Basically I want to get an event that the message has been received and send that message to my database (database bit already works)
I've tried all npm solutions including react-native-android-sms-listener, react-native-get-sms-android and other, but none seem to work, I've read somewhere, that expo may not support sms reading, but don't know how to use anything else for this sort of task
Nope, It is not available for now in expo variant, regarding Bare Workflow, there are few solutions that helps in reading the SMS
I want to integrate Firebase Crashlytics with Prometheus by reexporting crahses from Crashlytics as a Prom dashboard. I tried to utilize Google Cloud Functions for that but they do not seem to be called on every crash (there is no hook to integrate on every crash event). I also tried to export crashes to BigQuery, but the dataset was always empty.
What other options do I have, if any? Is this integration possible at all?
Thanks Alex. Todd from Firebase. Cloud functions is setup to only report on new issues, not individual crashes, so it unfortunately won't work for your use case. BQ is latent by 24 hours right now so it won't currently resolve your issue. We are considering real time BigQuery exports which is exactly what you need. Keep an eye on your dashboard, we'll share the news there if something is made.
My problem is about the analytics feature of Firebase. I set up my project with the help of react-native-firebase.
If I call: firebase.analytics(); which is provided by react-native-firebase no analytics data shows up in my Firebase console.
Why is that happening?
Info:
- I set up all as described in the official docs
It takes a few hours. In my case, it takes like 4 hours or something like that.
If you want to check out other features or check if Firebase is working for your app, you can force a crash, and see it in the Crash panel, cause this works almost real time.
Or you can send a notification to all users, this should work too, and it is faster than waiting for 4h or more to see if it is working really.
In the devCenter I can see how many people had downloaded my app, but I can't see how many of them use my app, daily, weekly, how long in a day etc.
Is there a way to get this information?
Thanks.
It is possible using an analytics framework, but you have to integrate one into your app during development.
There are various analytics frameworks available, such as Google Analytics, PreEmptive Solutions, Bango Analytics, Flurry Analytics, and so on and so forth.
I'm looking for a iOS crash reporter web service. I know MacDevCrashReports but they currently do not accept new sign ups.
I know there is a open source crash reporter framework on GitHub, but I don't want to put that stuff on a server, configure it and so on. A nice web service would be much nicer.
Thanks,
Patrick
I've been using Crittercism for my iOS and Android apps. It's saved me a LOT of time. It has a few more features than BugSense and Hoptoad.
MacDevCrashReports is running out, since I am not able to continue providing the service for free, the amount of data is just too huge. 100.000 crash reports e.g. require about 2GB of storage. BUT I am working on a new service with some friends to provide enhanced functionality for managing crash reports and other developer related data. You might want to check for HockeyApp for news about that.
Until then, you can also use the source MacDevCrashReports is based on, on your own web server. It is completely open source and available at GitHub.
The process of collecting crashes is using PLCrashReporter. Which is more reliable and is async-safe. There are also cases of crashes, like crashes in objc runtime, where it will result in a deadlock (Information by Landon Fuller, creator of PLCrashReporter).
Symbolication of PLCrashReporter created crash log files, can be done with the dSYM bundles, check this description.
Regarding the AppStore argument from Peter. As Patrick points out, this is not working for Ad-Hoc builds, which is one big issue, since you want to find and fix the crashes while testing. On the other side, the crash reports in iTunes Connect are very inaccurate:
The data set only updates once a day
The data is only available after users sync their devices with iTunes and only IF they agreed sending that data. Since most users don't understand the dialog, they deny
You only get a subset of crashes, the top 5
You don't get instant reports, as opposed using an in-app reporter
You don't get grouping of similar crashes as the web service does
You don't get a web interface to work with the crashes, make notes, mark as fixed, etc.
iTunes connect reports for my app to have 0 (zero) crashes, but in my database there are about 200! Check this blog post by futuretap about their experience and findings of using an in-app crash reporter.
There is a new service called BugSense . Give it a shot!
For ad-hoc crash reports you can use TestFlight. It has TestFlights SDK, using which you can collect crash reports and additional data, checkpoints, feedbacks.
If you're distributing through the App Store, you should get crash reports in iTunes Connect.
We're playing around with Hoptoad for some apps. Looks to work pretty well.
I've used HockeyApp and Crashlytics with great success. HockeyApp is nice in that once you've added your IPA file to their service they even provide a download page for you to distribute your build to your testers.
Crashlytics is a little cleaner from a UX perspective but it's still in beta and has a bit of a wait period whereas HockeyApp you can use immediately and it's a bit more mature. It also seems Crashlytics gives preference to apps that are already in the app store when you sign up for the program.
You can also check out BugHD,support iOS,Mac & Android Crash Report
For tracking crashes, I really like Appsee for iOS (although also great for Android apps). It gives detailed crash reports, and also session recordings that let you visually monitor all crashes within your app.
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
Appsee.start()
return true
}