--- title: Firebase Crash Reporting Full Release | daily.dev description: Firebase Crash Reporting has moved out of beta into full release, adding issue resolution features (marking clusters closed with automatic reopening on... canonical: https://daily.dev/posts/firebase-crash-reporting-full-release-gdygwckqa twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Firebase Crash Reporting Full Release | daily.dev og:description: Firebase Crash Reporting has moved out of beta into full release, adding issue resolution features (marking clusters closed with automatic reopening on... og:url: https://daily.dev/posts/firebase-crash-reporting-full-release-gdygwckqa og:image: https://api.daily.dev/og/posts/gdyGwCkqA.png og:image:alt: Firebase Crash Reporting Full Release og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Firebase Crash Reporting Full Release **[Firebase](https://daily.dev/sources/firebase-blog)** · 3 min read · 0 upvotes · 0 comments ## Summary Firebase Crash Reporting has moved out of beta into full release, adding issue resolution features (marking clusters closed with automatic reopening on regression), reduced reporting latency from about twenty minutes to under a minute, email alerts for new or regressed error clusters, Firebase Analytics events embedded in crash logs, a mobile-friendly console redesign, a fix for Android SDK compatibility with apps declaring an Application class, and updated symbol support for Swift 2 and 3 on iOS. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Does Firebase Crash Reporting support apps written in Swift? Yes, Firebase Crash Reporting shows symbols from apps written in Swift 2 and Swift 3 as of its full release. This update resolved earlier limitations in symbol resolution for Swift-based iOS apps, making crash reports readable for developers using either Swift version. _Developers tracking mobile SDK updates like this can follow crash reporting changes on daily.dev._ ### How long does it take for a crash to appear in the Firebase console after it occurs? Crash reporting latency in Firebase was reduced from about twenty minutes down to less than a minute at general availability. This improvement, combined with new email alerts for new or regressed error clusters, was designed to help developers diagnose and respond to crashes faster. _daily.dev helps engineers stay on top of performance improvements like reduced crash reporting latency._ ### Does Firebase Crash Reporting work with Android apps that declare a custom Application class? Yes, this compatibility limitation was fixed in the full release of Firebase Crash Reporting. The initial Android SDK release had trouble working with apps declaring an Application class, but that issue was resolved so the service should work with any Android app. _Android developers debugging SDK integration issues can track fixes like this on daily.dev._ --- Tags: [#mobile](https://daily.dev/tags/mobile), [#android](https://daily.dev/tags/android), [#ios](https://daily.dev/tags/ios), [#firebase](https://daily.dev/tags/firebase) [View this post on daily.dev](https://daily.dev/posts/firebase-crash-reporting-full-release-gdygwckqa) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Firebase Crash Reporting Full Release","url":"https://daily.dev/posts/firebase-crash-reporting-full-release-gdygwckqa","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/firebase-crash-reporting-full-release-gdygwckqa"},"datePublished":"2026-08-23T12:21:14.377Z","dateModified":"2026-08-23T12:36:28.889Z","description":"Firebase Crash Reporting has moved out of beta into full release, adding issue resolution features (marking clusters closed with automatic reopening on...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/firebase-crash-reporting-full-release-gdygwckqa","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"mobile,android,ios,firebase","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Firebase Crash Reporting Full Release"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/firebase-crash-reporting-full-release-gdygwckqa#faq","mainEntity":[{"@type":"Question","name":"Does Firebase Crash Reporting support apps written in Swift?","acceptedAnswer":{"@type":"Answer","text":"Yes, Firebase Crash Reporting shows symbols from apps written in Swift 2 and Swift 3 as of its full release. This update resolved earlier limitations in symbol resolution for Swift-based iOS apps, making crash reports readable for developers using either Swift version. Developers tracking mobile SDK updates like this can follow crash reporting changes on daily.dev."}},{"@type":"Question","name":"How long does it take for a crash to appear in the Firebase console after it occurs?","acceptedAnswer":{"@type":"Answer","text":"Crash reporting latency in Firebase was reduced from about twenty minutes down to less than a minute at general availability. This improvement, combined with new email alerts for new or regressed error clusters, was designed to help developers diagnose and respond to crashes faster. daily.dev helps engineers stay on top of performance improvements like reduced crash reporting latency."}},{"@type":"Question","name":"Does Firebase Crash Reporting work with Android apps that declare a custom Application class?","acceptedAnswer":{"@type":"Answer","text":"Yes, this compatibility limitation was fixed in the full release of Firebase Crash Reporting. The initial Android SDK release had trouble working with apps declaring an Application class, but that issue was resolved so the service should work with any Android app. Android developers debugging SDK integration issues can track fixes like this on daily.dev."}}]} ```