Telemetry bug: issues with `originalRequestIdentifier` and `requestIdentifier`

Open

#4,751 opened on Aug 25, 2021 2 comments 0 reactions 1 assignee View on GitHub

@RingerJK is already working on this.

Since Jan 24, 2022.

jira-sync-complete

Description

While trying to test, noticed that `requestSessionId` is inconsistent (probably unrelated to this PR but wanted to flag so we don't forget) 👀

_First re-route event_

![reroute_event_same_request_id](https://user-images.githubusercontent.com/1668582/130690628-d08ef08e-fc38-49b0-9fa5-e3eb59950d0e.png)

the original request id and the request id are the same but should be different.

_Second re-route event_

![reroute_event_different_request_id](https://user-images.githubusercontent.com/1668582/130690755-97ce4bd2-43c7-40d8-abbb-90e0eddef011.png)

the request ids are different, OK.

_Cancel event_

![cancel_event_different_request_id](https://user-images.githubusercontent.com/1668582/130690798-e0c16866-8ad4-43cf-9038-62de1ca61588.png)

the request ids are different but the request id doesn't match the previous one (from the latest re-route event) 🤔

-----
ref https://github.com/mapbox/mapbox-navigation-android/pull/4693#pullrequestreview-737575430

cc @Guardiola31337

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

This issue has not been assessed yet.