It is fixed for us too. We also opened a ticket with firebase and then came to know that is was a known issue in backend and is fixed now. We are also not observing it for more than a week.