Skip to content

stop_activity has no parameter activity_id #25

Closed

Description

@wrohdewald

That is what this API says but it seems wrong.

if the API description is actually correct, could you please specify what happens if the user has two lifetracking clients? Which one will be stopped?

Activity

  1. rob-tinderhouse commented on Oct 3, 2018

    @rob-tinderhouse

    For stop_activity, the system stops the activity_id held in the user's session.
    We would recommend not tracking concurrent activities on the same user account.

  2. wrohdewald commented on Oct 17, 2018

    @wrohdewald
    Author

    If tracking concurrent activities on the same user account is illegal, can you please add that to the api definition?

    Otherwise I believe this will fail if the client ip address changes just before stop_activity (like when switching between LTE and Wifi).

    BTW this api does not work anymore anyway at all. Try using get_activities on a free account. See my question http://support.mapmytracks.com/customer/portal/questions/17402402-did-something-change-with-api-access-

  3. nicktatt commented on Nov 13, 2018

    @nicktatt
    Contributor

    As a user of the API I wanted to draw your attention to a notice of change we have posted today. Details are here - https://github.com/MapMyTracks/api

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions