You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user (that has manually changed the JSESSIONID cookie to apply to both domains) tries requesting their timetable or the lernbüros, the backend server instantly exists with Code 0 without any traces in the logs, not even the request that caused the crash is mentioned. This does not happen in debug builds, where the methods still dont work, but return a 'Untis done fucked up' error instead of instantly exiting.
I will provide logs later today
The text was updated successfully, but these errors were encountered:
When a user (that has manually changed the JSESSIONID cookie to apply to both domains) tries requesting their timetable or the lernbüros, the backend server instantly exists with Code 0 without any traces in the logs, not even the request that caused the crash is mentioned. This does not happen in debug builds, where the methods still dont work, but return a 'Untis done fucked up' error instead of instantly exiting.
I will provide logs later today
The text was updated successfully, but these errors were encountered: