Open netstart opened 6 years ago
Any news on this? It's would be really helpful if we had crashlytics for the web applications now that we have performance monitoring supported.
Seems like Crashlytics is now the only GA Firebase product not supported for web...
Yeah... It's really missing piece of the puzzle. Hope it will be considered in near future :)
Maybe this can be integrated into firebase-performance?
https://github.com/GoogleCloudPlatform/stackdriver-errors-js
any updates on that?
@dzienisz I would just relax and wait until end of March they are currently rebuilding the Crashlytics SDK as the current one was built for Fabric (Crashlytics was a product of Fabric).
And maybe this will enable them to also support Crashlytics for Web.
Haven't seen anything about the web in their new rebuild.
+1
+1
+1 š
+1
+1
Iām building a template for ES module Firebase apps. Fully agree with @netstart ās original text that this should/could be within the Firebase umbrella.
I was hoping to use Crashlytics for a react-native & expo mobile app without ever having to touch any android/iOS-specific code. Looks like I have to use Bugsnag or is there any way to integrate Crashlytics (for web)?
For React Native, you could use React Native Firebase https://rnfirebase.io/ but it would have to be plain React Native, as it doesn't work with Expo. It doesn't require using any native mobile code though.
Thanks @hsubox76 for the quick reply and the pointer. That is a path forward if I eject from Expo and start using "bare" React Native.
Just to clarify, the only way I could use Firebase Crashlytics in my mobile app that is running on Expo would be if Crahslytics supported JS/Web apps, right?
I'm not sure what form a Crashlytics for Web product would take, or what the underlying technology would be, so I can't guarantee it would work with React Native or Expo.
But as this is a feature request issue, it seems like a good place for users to register a preference for any solution to work for React Native or anyone else's preferred environment.
A Javascript solution would also allow support for Flutter Web. Currently, the official supported crash reporting tool for Flutter Web is Sentry, which works well but would be nice to integrate with Crashlytics since most mobile apps will likely use that.
I'd love to see this added one day!
+1
+1
+1
Why can't you just mark exiting comment with a reaction and instead you put meaningless notification in dozens of mailboxes???
While various hacks exist we're still hanging out for this important feature.
Azure app insights supports JS web apps.
Their JavaScript SDK was first released in 2015!
Any updates?
still no updates? Or any ETA?
In my case I ended up using google's stackdrive which allows to keep track of errors and manage them. Its free and it's still from google. You can check how to set it up in this stackoverflow answer.
Works well so far while we are waiting for crashlytics support.
Seems like Crashlytics is now the only GA Firebase product not supported for web...
Nope. A/B Testing, Predictions and In-App messaging are still not supported for the web.
š¬ Still waiting. Any updates. We want to use our existing app on web, too but this stops us.
@Galti Have you considered Sentry? I've gone there.
@akauppi Sentry is Sentry and firebase is firebase. Current issue about firebase. (however Sentry nice tool and more or less good workaround for now)
@akauppi Thank you for your suggestion. But sometimes you can't decide which library/service to use in your app as you are not the CTO/Team Lead. By the way firebase works great for mobile and I think running it on the web is not enough reason to change to Sentry and do refactoring.
There is another alternative for the time being - Stackdrive, which is also google's product.
Here is a post on how to use it: https://stackoverflow.com/a/65500440/1713920
On Mon, Aug 1, 2022 at 7:52 AM Tigran Galstyan @.***> wrote:
@akauppi https://github.com/akauppi Thank you for your suggestion. But sometimes you can't decide which library/service to use in your app as you are not the CTO/Team Lead. By the way firebase works great for mobile and I think running it on the web is not enough reason to change to Sentry and do refactoring.
ā Reply to this email directly, view it on GitHub https://github.com/firebase/firebase-js-sdk/issues/710#issuecomment-1200740646, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6EXKTB6YZEV4VFWTWTME3VW5QZFANCNFSM4E3WDGUQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I wanna use Firebase Crashlytics for my app, nothing else. That's the only thing I know of that provides detailed and nice crash reports. Also, the Crashlytics SDK may have a small bundle size.
In a total perspective Firebase Crashlytics should focus on web-support, especieally when there isn't any emphasize on those pages that Crashlytics isn't supported for Flutter Web (and other web based systems), when it is supported for iOS, android.
If it is supported for Flutter Web (lately ?), please let is know. Page ref:
https://pub.dev/packages/firebase_crashlytics : emphasizes that there is no web support!! https://firebase.google.com/docs/crashlytics/get-started?platform=flutter : not mentioned
I totally agree with you. I'd love to have Firebase Crashlytics bring support to the web as well, especially because we're already using some other Firebase products, and don't want to continue adding more third-party providers to our projects, if it's not needed.
Reading about the latest cool Crashlytics feature feels kinda like another Firebase "let down" if you're a web dev. Seems like the Crashlytics devs have a "don't bother us" attitude to the web SDK. Seriously how hard can it be? It would seem like most of the stack is in place.
While I'm looking forward to having crashlytics, I don't think whining would do much to help.
If you need to track crashes, use Stackdrive for the time being - there is nothing to integrate, just enable it in your google account and you'll get crash reports. If you use standard "console.error" logs that's it, you don't even need to change your code at all.
If Stackdrive is not an option, then just wait.
Or you can become an employee of the Crashlytics team and implement it. Everyone else here would be grateful.
Other than that, comments with the whine attitude don't really add anything to the conversation, so please stop posting them.
On Wed, Sep 28, 2022 at 1:45 PM Tony OHagan @.***> wrote:
Reading about the latest cool Crashlytics feature feels kinda like another Firebase "let down" if you're a web dev. Seems like the Crashlytics devs have a "don't bother us" attitude to the web SDK. Seriously how hard can it be? It would seem like most of the stack is in place.
ā Reply to this email directly, view it on GitHub https://github.com/firebase/firebase-js-sdk/issues/710#issuecomment-1260784022, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6EXKXENZCQ4JMJSZFQDATWAQVULANCNFSM4E3WDGUQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Speaking for the JS SDK team, we would be happy to add Crashlytics to web and we know the high demand for it. A lot of moving parts need to come together to make that happen, so we can't guarantee anything. But feature request issues like this are very important for demonstrating demand and getting those moving parts to start moving, etc, so if this is important to you, absolutely thumbs up the original post.
And if you have any interesting use cases or reasons why it's important to you, or other Google/Firebase products you would use more of if Crashlytics was available, please feel free to add comments about it.
Also welcome are what are the most important features or requirements of a Crashlytics Web SDK? It will necessarily be different from mobile crashlytics as the definition of crashes and errors aren't perfectly parallel between mobile and web platforms. Or if there are other existing products out there that you like and you want us to match.
Interested particularly in Crashlytics for Flutter. Would love to the get the Dart stack trace in error reports.
Also welcome are what are the most important features or requirements of a Crashlytics Web SDK? It will necessarily be different from mobile crashlytics as the definition of crashes and errors aren't perfectly parallel between mobile and web platforms. Or if there are other existing products out there that you like and you want us to match.
For a Flutter app I don't see any differences between the definition of mobile/Web crashes and errors.
My Flutter app is available for Android, iOS and Web (+PWA app). I have added Sentry to my Web app, but I don't really use it because decrypting minified stack traces seems to require uploading my source codes to Sentry backend which I don't want to do. Also adding another service like Sentry to my app is just extra work and extra risk regarding e.g. privacy policy. So currently my Flutter app for Web is without functional error reporting. I fix issues I see from Android/iOS Crashlytics and trust that it is good enough also for Web for now.
I am not that familiar with other Web development tools, but I believe Flutter/Web developers in particular miss Crashlytics for Web a lot.
Also welcome are what are the most important features or requirements of a Crashlytics Web SDK? It will necessarily be different from mobile crashlytics as the definition of crashes and errors aren't perfectly parallel between mobile and web platforms. Or if there are other existing products out there that you like and you want us to match.
Our Flutter Web app could really use Crashlytics. Web is our primary deployment target, and occasionally Web has exceptions and issues that are not present on mobile, especially with federated plugin packages that have different implementation across platforms. Tracking web OAuth flows for exceptions in production, for example, is virtually impossible right now.
We are currently using Sentry instead of Crashlytics because of the multi-platform support - however, while Sentry allows us to see that flutter web exceptions are happening, there is a source map code minification issue https://github.com/flutter/flutter/issues/87734#issuecomment-927627149 that prevents accurate reporting of which part of the code is causing the exception.
Any update on here - been waiting patiently for years....
Very much needed...
UPDATE:
We moved to Sentry due to this.
Welcome to 2023, still waiting
UPDATE: To anyone still waiting for this FR, believe me, just move on to Sentry.
Even if the Firebase Team want to implement this, it'll take a long time until it gets as advanced as Sentry.
Welcome to 2023, still waiting
And the wait will continue. It seems that it will not be taken into account.
Its fun that looks like we'll close this year without any update on this lol
Sentry is actually really good lol just use it, don't worry about waiting
+1
I found i can just activate Google Error Reporting, create a simple firebase function that accepts and logs an Error object and call it from my web apps. By sending an Error object from the client, you ensure the client side stack is captured so the Error Reporting system can aggregate similar errors and allow you to manage and track resolutions.
https://cloud.google.com/error-reporting
I had a look at the client side library that Sentry add into your web app and while I'm sure it boasts some powerful features my conclusion was that in addition to $/month Sentry adds a large client side library that will likely impact app load times and TTI.
Speaking for the JS SDK team, we would be happy to add Crashlytics to web and we know the high demand for it. A lot of moving parts need to come together to make that happen, so we can't guarantee anything. But feature request issues like this are very important for demonstrating demand and getting those moving parts to start moving, etc, so if this is important to you, absolutely thumbs up the original post.
And if you have any interesting use cases or reasons why it's important to you, or other Google/Firebase products you would use more of if Crashlytics was available, please feel free to add comments about it.
Also welcome are what are the most important features or requirements of a Crashlytics Web SDK? It will necessarily be different from mobile crashlytics as the definition of crashes and errors aren't perfectly parallel between mobile and web platforms. Or if there are other existing products out there that you like and you want us to match.
hey, any news on the progress or timeline? Tell us anything please!
Please, support crashlytics firebase.
I do not want to use other services, like https://www.bugsnag.com/report crash in my web app writed in Angular