Hi all, thanks for the report. We've received reports of this error around 15 min ago and it seems to be resolved now.

If any of you are still getting this error, restarting the device should fix it.

Thank you and apologies for the inconvenience.