We got user reports that courses that didn't start yet and a user already enrolled in it, didn't become accessible after the course start date was passed. The notice "Course has not been started yet" was still shown.
I was able to reproduce this but it can be tricky to duplicate such a state with production data. Maybe manipulate the incoming data or use dummy data, like the tests.
I experienced the issue for the following courses, but they obviously have started in the meantime:
We got user reports that courses that didn't start yet and a user already enrolled in it, didn't become accessible after the course start date was passed. The notice "Course has not been started yet" was still shown.
I was able to reproduce this but it can be tricky to duplicate such a state with production data. Maybe manipulate the incoming data or use dummy data, like the tests.
I experienced the issue for the following courses, but they obviously have started in the meantime:
Clearing the app memory has solved the problem as a workaround.