Today I tried to start my map “Südhang”, (south-slope) again after modifying 2 dead ends yesterday. Found a blank job tag in the list. I can not rename it, so I deleted it, created a now job with my Südhang map and added the deadends, but still the same, can not name it and can not start it.
I have no clue where those areas xxx are. How can I get rid of them?
I can not even start the map alone anymore without the deadends.
Edit: did the app update from playstore, found the areas in area settings and deleted them (all 0,0m²), now everything is broken. My plan list is empty, I can not recreate or even restore the maps from a previous version.
And the support center is gone, link leads me to knowledge base, don’t know where my tickets are. I can’t connect to yarbo via HaLow through wifi from my phone, it works when I disable wifi and go through my phones data plan also through HaLow.
If yes, this is the error. They don’t support special characters. I opened a ticket to let them know that 2 days ago.
Rename the map by replacing the ü by u… Then you can save it. And you can delete the extra ones…
Happened to me with French Characters (é, è, ë).
This is a super rookie mistake you learn in your first programming class (always specify your encoding when you have open text fields) but it seems they skipped that one too…
Following up on this. The issue stopped initially (because I initially deleted the map), but it restarted. I finally found the issue. When I rename a map with an “accent” (è, é, ê, etc), it doesn’t save and create a new map of 0 squared meters. In short, it seems to be a bug with charset encoding recognition. Not sure what character set you support, but the app clearly doesn’t support UTF-8. Given you international outreach, you may wish to fix this. As a data scientist, I can tell you this is a very easy fix… Client sidde, you can ensure that when the app sends the new map name to your server, the text is explicitly encoded in the required format… You could also enforce a charset validation during the saving process so a user cannot use special characters (so you would get an error such as “é” character not supported, or something like that… For example in swift in your app you could create a function like:
import Foundation
/// - Returns: true if the string is ASCII-only, false otherwise.
func canBeSaved(withText text: String) → Bool {
// This will return false if the string contains any special character that are outside the ASCII set.
return text.canBeConverted(to: .ascii)
}
// The user’s input from a text field
let mapNameFromUser = “Carte arrière” // An example with a special character
// Perform the validation check before saving
if canBeSaved(withText: mapNameFromUser) {
print(“Validation passed. Saving map: (mapNameFromUser)”)
// Proceed with your network request to save the data
} else {
print(“Validation failed. Unsupported characters detected.”)
// Display an error message to the user, for example:
// “Error: The name cannot contain special characters like ‘é’. Please try again.”
}
// — Example with a valid name —
let anotherMapName = “My Summer Map”
if canBeSaved(withText: anotherMapName) {
print(“Validation passed. Saving map: (anotherMapName)”)
}
Same error. Why it starts giving you problems just now, no idea. Maybe the bug was introduced in a recent update? But I can reproduce the error each time I rename an area with an accent…
