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
{{ message }}
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
The time values are sometimes more than just a simple one line string, but with multiple lines and \n. Probably received like that from the API and not properly formatted.
Environment
Phone: OnePlus 5T
OS version: OxygenOS 10.0.1
TUM Campus App version: v3.9-dev
Language: German & English
The text was updated successfully, but these errors were encountered:
Can confirm it's the server who's at fault here. The newlines within the json vary among literal "\\n", "\/n" and "\n". Both 1 and 2 are essentially wrong following ECMA 404. Number 1 is where this issue appears, number 2 is "fixed" by the weird string-replace stuff happening here.
Gson (correctly) interprets the "\\n" in the json as literal "\n", "\/n" as "/n", and "\n" as an actual newline character. While number 1 probably occurs because of a single escaping backslash too many (in the json source), I don't really see why number 2 would happen, even though it seems to be the most frequent by far.
Other json elements are also affected (like "infos").
Opening hours are simply stored in the backend and retrieved by the app, we can easily replace any inconsistencies there I suppose. @SiKreuz you can open this in https://github.com/TUM-Dev/Backend if you want.
Steps to Reproduce
\n
. Probably received like that from the API and not properly formatted.Environment
Phone: OnePlus 5T
OS version: OxygenOS 10.0.1
TUM Campus App version: v3.9-dev
Language: German & English
The text was updated successfully, but these errors were encountered: