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
For a few months I have been seeing the behaviour in the screenshot with 100% consistency. Certain tiles were loading incorrectly. At a given zoom the same tiles would always render in the OSM style, instead of the MapBox provider style that is specified as a tile source.
To fix this problem, I had to delete /sdcard/osmdroid/*sqlite.
Things that did not fix this:
uninstalling the app
deleting /sdcard/osmdroid/tiles
Since deleting the sqlite files, those files have not reappeared. The MozStumbler app don't use sql-backed tiles.
Potentially, this is not a bug at all, and the MozStumbler app switched its OSMDroid source around in such a way that triggered this (I don't know the history of the apps OSMDroid use).
The text was updated successfully, but these errors were encountered:
i'll ping @crankycoder, he might recall. In the month after this bug was filed we made many changes to our OSMDroid usage and the bug no longer occurred.
Most likely this got worked around when the app switched at that time to using a non-shared directory for the tile source.
Cloned from: mozilla/MozStumbler#759
For a few months I have been seeing the behaviour in the screenshot with 100% consistency. Certain tiles were loading incorrectly. At a given zoom the same tiles would always render in the OSM style, instead of the MapBox provider style that is specified as a tile source.
To fix this problem, I had to delete /sdcard/osmdroid/*sqlite.
Things that did not fix this:
Since deleting the sqlite files, those files have not reappeared. The MozStumbler app don't use sql-backed tiles.
Potentially, this is not a bug at all, and the MozStumbler app switched its OSMDroid source around in such a way that triggered this (I don't know the history of the apps OSMDroid use).
The text was updated successfully, but these errors were encountered: