New post
0

[Bug] SkySafari 6 Pro Lags And Cannot Access Settings When Location Is Disabled And Permission Is Denied

Device Used - Nexus 7 tablet running Android 6.0.1

When initially starting SkySafari 6 Pro, with Storage permission allowed, and Location permission denied, the app was in a near frozen state.  Panning around took several seconds before it recognized the pan, and just jumped to a location instead of smoothly panning around.

When trying to access any of the bottom menu options, the app never pulled up the menu options.  I was trying to get to the settings, to change my location, selecting it "from list", like I did previously in SkySafari 5 Pro, Skysafari 4 Pro, and Skysafari Pro.

This was not the case when the same permissions were selected as stated above with Skysafari 5 Pro, 4 Pro, or Pro.  I was able on initial run to go to the settings, and select my location from list.

 

The walkaround I had to take in order to get Skysafari 6 Pro running, was use the app FakeGPS, select my location (Cuba) after turning on location in the Android OS, and allowing the location permission for Skysafari 6.  Then on initial startup, it ran flawlessly, and I was able to then select items from the bottom menu, such as settings, get into that menu, and change my location to one selected from the list.  I then quit Skysafari, force closed it, turned off location in Android OS, and denied the permission for Skysafari for Location.  Next startup of Skysafari remembered the setting of the location selected from list, and ran flawlessly.

4 comments

  • 0
    Avatar
    Bill Tschumy

    Jason,

    Why are you using FakeGPS?  Doesn't it work fine you just manually input your location?  You need to name the location something other than Current Location or it will try to get a GPS fix.

  • 0
    Avatar
    Bill Tschumy

    OK, I just got time to try this.  You are right that if you have the location permissions off the app is glacially slow if you have your location set to "Current Location".  I need to track down what is going on in this case.  Stay tuned.

  • 0
    Avatar
    Jason M

    Thanks for looking into this. I don't want other users to be dissuaded by an otherwise great application.

  • 0
    Avatar
    Bill Tschumy

    Jason,

    I have this fixed.  Apparently now that we are no longer supporting Android 4.0, the system is invoking some new behavior that put us into an infinite loop.  We just hadn't tested the case where the user refused permission (our bad).

    Thanks for bringing this to our attention.  I will probably release a new version with this fix tomorrow.

Please sign in to leave a comment.