mapbox / mapbox/mapbox-navigation-android
Bug: android-auto-components:3.23.1 aar contains Git LFS pointer instead of raw asset (ic_search_black36dp.png)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
The 3.23.1 release of com.mapbox.navigationcore:android-auto-components fails to compile because an image asset was incorrectly packaged. The release pipeline appears to have packaged the Git LFS pointer file instead of pulling the actual binary asset.
Steps to Reproduce
Include com.mapbox.navigationcore:android-auto-components:3.23.1 in an Android project.
Attempt to assemble/build the project.
Error:
AAPT: error: file failed to compile.
/res/drawable/ic_search_black36dp.png: AAPT: error: file failed to compile.
Root Cause Evidence
Inspecting the unzipped .aar from the Maven repository reveals that res/drawable/ic_search_black36dp.png is actually a plain text file containing Git LFS metadata instead of image bytes:
version https://git-lfs.github.com/spec/v1
oid sha256:9c807...
size 1492
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 reproducing the failure with com.mapbox.navigationcore:android-auto-components:3.23.1 and inspect the AAR's res/drawable/ic_search_black36dp.png entry. Then trace the release pipeline's Git LFS handling and verify that the packaged entry contains the raw PNG bytes and that an Android project assembles successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100