Apple API startDate and endDate parameters

Open
#137 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
macos, swift
Domain
api, reverse-engineering

Research direction

Start with the OHServerApp code path that builds location-report requests and compare how startDate and endDate are sent. Reproduce the request against Apple’s API and determine whether the fields are ignored for custom applications and Apple devices; done means their support or omission is confirmed and documented.

Written by the indexing model from the issue text.

Description

question

I am using a custom application through the OHServerApp, and I am able to download location reports just fine.

I tried modifying the OHServerApp code to also send startDate and endDate, but Apple seems to ignore those fields.

Could anyone confirm that Apple just ignores those fields?
If so, how did the OH Team discover those attributes at all?
Do those fields get ignored if iPhones or other Apple devices send them?

Using those fields would save me tons of traffic...

Dominant language
Swift
Stars
13.6k
Forks
681
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seemoo-lab/openhaystack

All issues in seemoo-lab/openhaystack

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.