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 getUserUUID() returns null, c:geo makes a request to /okapi/services/caches/shortcuts/search_and_retrieve with the found_by parameter set to unknown-user, which is not a valid UUID and causes an error.
I suggest implementing proper handling for cases where the UUID is invalid.
Below is a table showing the expected behavior in various cases and the current behavior:
(To simplify the examples, I used /okapi/services/caches/search/all instead of /okapi/services/caches/shortcuts/search_and_retrieve)
stefopl
changed the title
Handle invalid UUIDs in found_by parameter for OKAPI services
Handle invalid UUIDs in found_by parameter within prepare_common_search_params()
Nov 21, 2024
stefopl
pushed a commit
to stefopl/okapi
that referenced
this issue
Nov 21, 2024
There are a lot of errors of this type appearing:
I suspect that all of them are coming from c:geo.
https://github.com/cgeo/cgeo/blob/405083903b8da9e88f3a00ba329ff10285b82eeb/main/src/main/java/cgeo/geocaching/connector/oc/OkapiClient.java#L445
https://github.com/cgeo/cgeo/blob/405083903b8da9e88f3a00ba329ff10285b82eeb/main/src/main/java/cgeo/geocaching/connector/oc/OkapiClient.java#L494
When getUserUUID() returns null, c:geo makes a request to /okapi/services/caches/shortcuts/search_and_retrieve with the found_by parameter set to unknown-user, which is not a valid UUID and causes an error.
I suggest implementing proper handling for cases where the UUID is invalid.
Below is a table showing the expected behavior in various cases and the current behavior:
(To simplify the examples, I used /okapi/services/caches/search/all instead of /okapi/services/caches/shortcuts/search_and_retrieve)
The text was updated successfully, but these errors were encountered: