rnmapbox / rnmapbox/maps

[Bug]: `LocationPuck` bearing not visible on Android

Open
#3,391 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug 🪲
Dominant language
Kotlin
Stars
2.9k
Forks
947
Avg merge
6d 37m
Merged PRs (30d)
1

Description

Mapbox Implementation

Mapbox

Mapbox Version

default

React Native Version

0.73.4

Platform

Android

@rnmapbox/maps version

10.1.15

Standalone component to reproduce
import React from 'react'
import { Camera, LocationPuck, MapView } from '@rnmapbox/maps'

export default function App() {
  return (
    <MapView style={{ flex: 1 }}>
      <Camera
        zoomLevel={14}
        followUserLocation={true}
      />
      <LocationPuck
        puckBearingEnabled={true}
      />
    </MapView>
  )
}
Observed behavior and steps to reproduce

When rendering the LocationPuck with its bearing enabled on Android, the bearing does not appear. The bearing does appear on iOS.

Android iOS
unnamed (1) IMG_69F787A3B577-1
Expected behavior

The LocationPuck's bearing should be visible on both Android and iOS if enabled.

Notes / preliminary analysis

No response

Additional links and references

No response

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 with the standalone React Native reproduction using MapView, Camera, and LocationPuck with puckBearingEnabled on Android, then compare the Android and iOS LocationPuck implementations. Verify the behavior on the reported React Native 0.73.4 and @rnmapbox/maps 10.1.15 versions. Done means the bearing is visible on Android when enabled, matching the expected iOS behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin, react-native
Domain
mobile-dev
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.