fix(android): Remove verbose FrameMetricsAggregator failure logging #2293
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.
📜 Description
Removes log output when calling the FrameMetricsAggregator fails.
💡 Motivation and Context
Right now any error when calling the FrameMetricsAggregator gets logged, including it's stacktrace. This can be confusing to the user, since we know FrameMetricsAggregator is expected to throw exceptions for various reasons.
Prior to 6.4.4 exceptions were swallowed, we should revert to that behavior.
Related issue: #2292
💚 How did you test it?
Ran tests.
📝 Checklist
🔮 Next steps