mapbox / mapbox/mapbox-navigation-ios

[Bug]: "Location Error when creating location indicator layer: unexpectedType" error in logs

Open
#3,595 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug jira-sync-complete UI
Dominant language
Swift
Stars
918
Forks
326
Avg merge
1h 16m
Merged PRs (30d)
3

Description

Mapbox Navigation SDK version

v2.0.0-rc.1

Steps to reproduce
  1. Run the Example application.
  2. Start an active guidance navigation
Expected behavior

"Location Error when creating location indicator layer: unexpectedType" doesn't appear in logs.

Actual behavior

On each location update there is a "Location Error when creating location indicator layer: unexpectedType" error in console:

2021-11-15 16:30:12.376046+0300 Example[38452:367972] Location Error when creating location indicator layer: unexpectedType
2021-11-15 16:30:13.342458+0300 Example[38452:367972] Failed to convert UIImage
Is this a one-time issue or a repeatable issue?

repeatable

Contributor guide

Open the contributing guide

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.

Research direction

Start by running the Example application with Mapbox Navigation SDK v2.0.0-rc.1, begin active guidance, and confirm the repeated unexpectedType and Failed to convert UIImage messages on location updates. Trace the code path that creates the location indicator layer and identify why the image conversion fails. Done means the repeatable console errors no longer appear during navigation.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.