Hi there,
That looks like a bug, but I'm not sure we can reproduce it without more details. Can you try to debug the network to see which request is triggering this response? If you don't know how to do that, you can check out the following document: Debugging network requests in the Moodle App
I'd also suggest that you try to reproduce this in a browser, rather than a native device; it should be easier to debug.