feat(analytics)!: remove deprecated methods for breaking change release #17560
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
10 tasks
Lyokone changed the title 
russellwheatley requested changes Jul 25, 2025
SelaseKay approved these changes Jul 25, 2025
russellwheatley approved these changes Jul 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: Removes deprecated methods from firebase_analytics package
setCurrentScreen()method (deprecated in favor oflogScreenView())logSetCheckoutOption()method (deprecated and unsupported in Enhanced Ecommerce reports)Migration Guide
Replace
setCurrentScreen()withlogScreenView()Before:
After:
Remove
logSetCheckoutOption()callsThe
logSetCheckoutOption()method has been completely removed as it's unsupported in updated Enhanced Ecommerce reports. If you were using this method, consider using alternative ecommerce tracking methods or consult the Firebase Analytics documentation for current best practices.