Closed tuukka closed 3 years ago
Hmm, I refactored almost everything about the OSM API parser (which this error occurred in) in v1.1.2.
Let me know if you can reproduce the issue in that version (it should get approved in the next couple of days).
I can't reproduce this in version 1.2.0. Closing for now.