MagpieFourtyTwo

What about just generating a UUID *once*, store it in the db as type UUID and always just use this one as a suffix for the "normal" ZZ number, which...

> But what's the advantage of that? Backwards compatibility (cause "ZZ1409" works as well as "ZZ1409-wer76-987wer-08wer"). And if the UUID is device resp. installation specific, you add. avoid the problem...

Already mentioned: I would avoid using same GUIDs on different devices resp. installations. Otherwise you may possibly violate DSGVO, cause you make an installation trackable without giving the user the...

Yep - and there's nothing to say against it, as long as you give the possibility to reset the ID. But all this has already been mentioned ... do how...

> > [Import collision] > This is the same for all caches, imported gpx always overwrites everything. Close, but not quite, which leads us back to the initial topic of...

Over here: 

Ok ... over here it's in "Default language", on an English based Android. So probably a translation resp. NLS dictionary problem ...?

;) Overloaded translations? Don't know how NLS is implemented in c:geo, but if it works with string IDs, maybe an ID is used multiple times ...? Although the dots in...

Meanwhile it showed some even more strange texts, but currently it says "Search caches/trackables" - at least over here. Looks a bit like a compilation problem. As for the issue:...

And with today's nightly I get the text "Bike" ...