[ℹ️] NT-1143 Adding more info to TrackingWorker error logs #839
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
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📲 What
Adding more info to TrackingWorker error logs.
🤔 Why
Tracking failures are a big mystery! Hopefully with more info in the logs, we can get down to the bottom of it.
🛠 How
response.messageandrunAttemptCountto the error message that's logged when an event fails to track.build.gradle
I had to add another repo for Apollo because it was causing the build to fail. More ammo for justification to get rid of it.
👀 See
Logs only.
📋 QA
We will see these failures in the Firebase console 🚀
Story 📖
NT-1143