Home → Bug Reports →

CalTopo App - MB Layers Blank After Offline Download

• Edit

Scott

07 Apr, 2021 04:01 PM

After download MB Tiles and elevation data the layers no longer work for the area I just downloaded - it's just a blank map.
To fix it I go back to Download Layers, select the quadrants, and delete.

I have had this happen to myself and others when using the CalTopo app (iOS and Android). I'm using iOS app version 0.7.7.

I also downloaded Scanned Topos and that layer is working fine.

Thanks,
-Scott

1. Support Staff 1 Posted by Ben Lantow on 07 Apr, 2021 04:14 PM

   

   Hi Scott,
   Can you share what layer and what specific area you downloaded, and was it standard or high resolution downloads?

   When you have this issue are you connected in cell service, in airplane mode, or just in low or no service but with cell data on?

   When you go and delete the quadrants are you saying maps load correctly?

   Best,
   Ben

   • Edit

2. 2 Posted by Scott on 07 Apr, 2021 05:44 PM

   

   Hi Ben,

   I downloaded 4 quadrants of MB Topo in the Vancouver, BC area.
   The first time I tried with 'Max' resolution. Then I deleted the download and tried again with 'High' resolution but had the same problem.

   I'm having this happen on Wifi.

   MB Overlay and Scanned Topos work fine.

   Correct, when I delete the downloaded quadrants the MB Topo layer displays fine.

   I've attached a screenshot that shows the blank space where the downloaded tiles should be.

   -Scott

   • IMG_143A69AB21B6-1.jpeg 1.21 MB
   • Edit

3. Support Staff 3 Posted by Ben Lantow on 08 Apr, 2021 01:31 AM

   

   Scott,
   We think we have a handle on the potential issue. If you switch to light mode and try the same steps that were causing you an issue, does the problem still persist?

   Best,
   Ben

   • Edit

4. 4 Posted by Scott on 08 Apr, 2021 04:47 AM

   

   Hi Ben,

   Interesting. Yes, when I switch to light mode the layer works as it should.

   Scott

   • Edit

5. Support Staff 5 Posted by Ben Lantow on 13 Apr, 2021 12:06 AM

   

   Scott,
   We found the problem and fixed the bug for the next app release. Thanks for letting us know!

   Ben

   • Edit

6. Ben Lantow closed this discussion on 13 Apr, 2021 12:06 AM.