mapbox / mapbox/mapbox-navigation-android
[Telemetry] Handle telemetry enable/disable in runtime
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
The SDK has to handle the Telemetry events library disabled/enabled in runtime and stop correspondingly Nav Telemetry.
Might need support from an outer team to provide an observer of a Telemetry state to not handle it on the SDK side.
Telemetry enable/disable before initialization was resolved in https://github.com/mapbox/mapbox-navigation-android/issues/5450
@LukasPaczos
Contributor guide
First steps
- 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.
Research direction
Start by reviewing the runtime enable/disable behavior for the Telemetry events library and the resolution of pre-initialization handling in issue 5450. Identify the SDK entry point and any tests covering Nav Telemetry lifecycle changes; done means Nav Telemetry responds correspondingly when the library is enabled or disabled after initialization, with any required observer support clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100