requestLocation() fails to provide Course on watch hardware but work in Sim





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I've written a standalone Applewatch app which uses GPS. Trying to be a good citizen and minimize power consumption, I am using the single shot location request method. On the Xcode sim, this works fine, providing a location AND course and speed (when using one of the recorded movements in the sim). On real hardware, I get accurate lat and long data back but course always returns "-1". Note: I am not looking for Heading data as there is no magnetometer hardware in watch. I want course over the ground from ∆X,Y from the GPS fixes. Expected behavior is that it should not work in Sim with a single shot requestLocation(), but since it does, why not work on the real thing? Has anyone else seen this? Is this a bug to Radar, or a feature?



I suppose if this approach is known to fail, I could try startUpdating() until I see a course, then stop updating, but Apple says this is a power hogging approach.










share|improve this question























  • Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation No course reported by hardware(Sim does report), nbut when locationMgr.desiredAccuracy = kCLLocationAccuracyBest locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation , then the watch does report course.

    – BlueskyMed
    Jan 4 at 20:33




















1















I've written a standalone Applewatch app which uses GPS. Trying to be a good citizen and minimize power consumption, I am using the single shot location request method. On the Xcode sim, this works fine, providing a location AND course and speed (when using one of the recorded movements in the sim). On real hardware, I get accurate lat and long data back but course always returns "-1". Note: I am not looking for Heading data as there is no magnetometer hardware in watch. I want course over the ground from ∆X,Y from the GPS fixes. Expected behavior is that it should not work in Sim with a single shot requestLocation(), but since it does, why not work on the real thing? Has anyone else seen this? Is this a bug to Radar, or a feature?



I suppose if this approach is known to fail, I could try startUpdating() until I see a course, then stop updating, but Apple says this is a power hogging approach.










share|improve this question























  • Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation No course reported by hardware(Sim does report), nbut when locationMgr.desiredAccuracy = kCLLocationAccuracyBest locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation , then the watch does report course.

    – BlueskyMed
    Jan 4 at 20:33
















1












1








1








I've written a standalone Applewatch app which uses GPS. Trying to be a good citizen and minimize power consumption, I am using the single shot location request method. On the Xcode sim, this works fine, providing a location AND course and speed (when using one of the recorded movements in the sim). On real hardware, I get accurate lat and long data back but course always returns "-1". Note: I am not looking for Heading data as there is no magnetometer hardware in watch. I want course over the ground from ∆X,Y from the GPS fixes. Expected behavior is that it should not work in Sim with a single shot requestLocation(), but since it does, why not work on the real thing? Has anyone else seen this? Is this a bug to Radar, or a feature?



I suppose if this approach is known to fail, I could try startUpdating() until I see a course, then stop updating, but Apple says this is a power hogging approach.










share|improve this question














I've written a standalone Applewatch app which uses GPS. Trying to be a good citizen and minimize power consumption, I am using the single shot location request method. On the Xcode sim, this works fine, providing a location AND course and speed (when using one of the recorded movements in the sim). On real hardware, I get accurate lat and long data back but course always returns "-1". Note: I am not looking for Heading data as there is no magnetometer hardware in watch. I want course over the ground from ∆X,Y from the GPS fixes. Expected behavior is that it should not work in Sim with a single shot requestLocation(), but since it does, why not work on the real thing? Has anyone else seen this? Is this a bug to Radar, or a feature?



I suppose if this approach is known to fail, I could try startUpdating() until I see a course, then stop updating, but Apple says this is a power hogging approach.







gps watchkit core-location






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 4 at 0:33









BlueskyMedBlueskyMed

151211




151211













  • Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation No course reported by hardware(Sim does report), nbut when locationMgr.desiredAccuracy = kCLLocationAccuracyBest locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation , then the watch does report course.

    – BlueskyMed
    Jan 4 at 20:33





















  • Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation No course reported by hardware(Sim does report), nbut when locationMgr.desiredAccuracy = kCLLocationAccuracyBest locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation , then the watch does report course.

    – BlueskyMed
    Jan 4 at 20:33



















Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation No course reported by hardware(Sim does report), nbut when locationMgr.desiredAccuracy = kCLLocationAccuracyBest locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation , then the watch does report course.

– BlueskyMed
Jan 4 at 20:33







Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation No course reported by hardware(Sim does report), nbut when locationMgr.desiredAccuracy = kCLLocationAccuracyBest locationMgr.distanceFilter = kCLDistanceFilterNone locationMgr.activityType = .otherNavigation , then the watch does report course.

– BlueskyMed
Jan 4 at 20:33














1 Answer
1






active

oldest

votes


















0














Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when



locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer
locationMgr.distanceFilter = kCLDistanceFilterNone
locationMgr.activityType = .otherNavigation



No course reported by hardware(Sim does report),but when

locationMgr.desiredAccuracy = kCLLocationAccuracyBest
locationMgr.distanceFilter = kCLDistanceFilterNone
locationMgr.activityType = .otherNavigation


then the watch does report course. It would seem that .DistanceFilter should be relevant to ∆X,∆Y reports for course, but why should .desiredAccuracy matter?



BTW, original code had Accuracy of 1km due Apple noting increasing accuracy increases power drain.






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54031708%2frequestlocation-fails-to-provide-course-on-watch-hardware-but-work-in-sim%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when



    locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer
    locationMgr.distanceFilter = kCLDistanceFilterNone
    locationMgr.activityType = .otherNavigation



    No course reported by hardware(Sim does report),but when

    locationMgr.desiredAccuracy = kCLLocationAccuracyBest
    locationMgr.distanceFilter = kCLDistanceFilterNone
    locationMgr.activityType = .otherNavigation


    then the watch does report course. It would seem that .DistanceFilter should be relevant to ∆X,∆Y reports for course, but why should .desiredAccuracy matter?



    BTW, original code had Accuracy of 1km due Apple noting increasing accuracy increases power drain.






    share|improve this answer




























      0














      Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when



      locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer
      locationMgr.distanceFilter = kCLDistanceFilterNone
      locationMgr.activityType = .otherNavigation



      No course reported by hardware(Sim does report),but when

      locationMgr.desiredAccuracy = kCLLocationAccuracyBest
      locationMgr.distanceFilter = kCLDistanceFilterNone
      locationMgr.activityType = .otherNavigation


      then the watch does report course. It would seem that .DistanceFilter should be relevant to ∆X,∆Y reports for course, but why should .desiredAccuracy matter?



      BTW, original code had Accuracy of 1km due Apple noting increasing accuracy increases power drain.






      share|improve this answer


























        0












        0








        0







        Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when



        locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer
        locationMgr.distanceFilter = kCLDistanceFilterNone
        locationMgr.activityType = .otherNavigation



        No course reported by hardware(Sim does report),but when

        locationMgr.desiredAccuracy = kCLLocationAccuracyBest
        locationMgr.distanceFilter = kCLDistanceFilterNone
        locationMgr.activityType = .otherNavigation


        then the watch does report course. It would seem that .DistanceFilter should be relevant to ∆X,∆Y reports for course, but why should .desiredAccuracy matter?



        BTW, original code had Accuracy of 1km due Apple noting increasing accuracy increases power drain.






        share|improve this answer













        Continuing with experiments, it appears that the course issue is dependent on the properties of the instance of CLLocationManager: when



        locationMgr.desiredAccuracy = kCLLocationAccuracyKilometer
        locationMgr.distanceFilter = kCLDistanceFilterNone
        locationMgr.activityType = .otherNavigation



        No course reported by hardware(Sim does report),but when

        locationMgr.desiredAccuracy = kCLLocationAccuracyBest
        locationMgr.distanceFilter = kCLDistanceFilterNone
        locationMgr.activityType = .otherNavigation


        then the watch does report course. It would seem that .DistanceFilter should be relevant to ∆X,∆Y reports for course, but why should .desiredAccuracy matter?



        BTW, original code had Accuracy of 1km due Apple noting increasing accuracy increases power drain.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 4 at 20:47









        BlueskyMedBlueskyMed

        151211




        151211
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54031708%2frequestlocation-fails-to-provide-course-on-watch-hardware-but-work-in-sim%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Monofisismo

            Angular Downloading a file using contenturl with Basic Authentication

            Olmecas