It was a bug in Firebase. I opened a support ticket with them and worked though it till they found the issue. It’s been fixed in my data for the past week or so. Are you still seeing it on fresh logs from them?