The same thing happened with me . But upon launching the instance multiple times the issue disappeared. I think this is not a bug but a server issue
The same thing happened with me .
But upon launching the instance multiple times the issue disappeared.
I think this is not a bug but a server issue