Bolling Posted December 6, 2016 Report Share Posted December 6, 2016 I downloaded 2.0 today, and first off, I would like to say that it looks great. I hope to get out and use it soon! However, I was surprised to find a "bug" almost immediately. I am using iOS v10.1 and experienced this problem on both an iPhone 6, and an iPad Pro 9.7. I am a premium geocaching.com member. I downloaded a pocket query on the device. The map view looked good. I then went to the List view and sorted by Ascending and Distance. The caches appeared to be in no logical order. I then tried other sorts such as Type, and Difficulty. They displayed as expected. I then switched back to Distance and it displayed as expected. I also tried this with an GSAK GPX file import from DropBox with similar results. In Ascending order my distance I get caches that are 30 miles, then 40 miles than less than one mile away. I'll be glad to send a GPX file and screenshot. Like this Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted December 6, 2016 Report Share Posted December 6, 2016 Thanks for reporting this. We had another user with this issue in the beta stage but we couldn't replicate it. Does this happen always? Or are there things that cause it such as not being on wifi or having no data connection? Quote Link to comment Share on other sites More sharing options...
Bolling Posted December 6, 2016 Author Report Share Posted December 6, 2016 42 minutes ago, Nic Hubbard said: Does this happen always? Or are there things that cause it such as not being on wifi or having no data connection? I'd say it's too soon to say if it "always" happens. I downloaded on wifi on both devices and was connected to wifi when using. Note though that the problem was only noticed with offline data. Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted December 6, 2016 Report Share Posted December 6, 2016 16 minutes ago, Bolling said: I'd say it's too soon to say if it "always" happens. I downloaded on wifi on both devices and was connected to wifi when using. Note though that the problem was only noticed with offline data. Thanks. I will look into this report right away and get it fixed. Quote Link to comment Share on other sites More sharing options...
MrGigabyte Posted December 6, 2016 Report Share Posted December 6, 2016 Nic, I think this is the same issue we discussed. It was based on the map refresh location I recall. Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted December 6, 2016 Report Share Posted December 6, 2016 8 minutes ago, MrGigabyte said: Nic, I think this is the same issue we discussed. It was based on the map refresh location I recall. Yes, working to fix this for our 2.0.1 release. Thanks! Quote Link to comment Share on other sites More sharing options...
Bolling Posted December 7, 2016 Author Report Share Posted December 7, 2016 After further investigation this problem is very repeatable. It also occurs when sorting Live cache data by distance, not just offline cache data. Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted December 7, 2016 Report Share Posted December 7, 2016 2 minutes ago, Bolling said: After further investigation this problem is very repeatable. It also occurs when sorting Live cache data by distance, not just offline cache data. This has been fixed in the 2.0.1 beta. Would you want to test it? Quote Link to comment Share on other sites More sharing options...
Bolling Posted December 7, 2016 Author Report Share Posted December 7, 2016 I'm more than willing to test. Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted December 7, 2016 Report Share Posted December 7, 2016 1 hour ago, Bolling said: I'm more than willing to test. If you are not already on our beta testing list (I don't always know everyone's names, just emails) then please contact support through Cachly so that we can set you up. Thanks! Quote Link to comment Share on other sites More sharing options...
Bolling Posted December 7, 2016 Author Report Share Posted December 7, 2016 The issue appears to be fixed in the beta. That was quick. Quote Link to comment Share on other sites More sharing options...
Nic Hubbard Posted December 7, 2016 Report Share Posted December 7, 2016 35 minutes ago, Bolling said: The issue appears to be fixed in the beta. That was quick. That is good news. Let me know if you see it crop up again. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.