Skip to content

Fix #3889 : With react new arch, allowOverlap is always true#3890

Merged
mfazekas merged 1 commit into
rnmapbox:mainfrom
scharron:patch-1
Jul 27, 2025
Merged

Fix #3889 : With react new arch, allowOverlap is always true#3890
mfazekas merged 1 commit into
rnmapbox:mainfrom
scharron:patch-1

Conversation

@scharron

@scharron scharron commented Jun 24, 2025

Copy link
Copy Markdown
Contributor

This bug appears using the new react architecture. This is because of the id allowOverlap = RNMBXConvertFollyDynamicToId(newProps.allowOverlap); conversions that returns a pointer that is always true instead of the value of the pointed object according to #3730

Description

Fixes #3889
This bug appears using the new react architecture. This is because of the id allowOverlap = RNMBXConvertFollyDynamicToId(newProps.allowOverlap); conversions that returns a pointer that is always true instead of the value of the pointed object according to #3730

Checklist

  • I've read CONTRIBUTING.md
  • I updated the doc/other generated code with running yarn generate in the root folder
  • I have tested the new feature on /example app.
    • In V11 mode/ios
    • In New Architecture mode/ios
    • In V11 mode/android
    • In New Architecture mode/android
  • I added/updated a sample - if a new feature was implemented (/example)

Screenshot OR Video

Component to reproduce the issue you're fixing

This bug appears using the new react architecture.
This is because of the id allowOverlap = RNMBXConvertFollyDynamicToId(newProps.allowOverlap); conversions that returns a pointer that is always true instead of the value of the pointed object according to rnmapbox#3730
@scharron scharron temporarily deployed to CI with Mapbox Tokens July 3, 2025 04:48 — with GitHub Actions Inactive
@scharron scharron temporarily deployed to CI with Mapbox Tokens July 3, 2025 04:48 — with GitHub Actions Inactive
@scharron scharron temporarily deployed to CI with Mapbox Tokens July 3, 2025 04:48 — with GitHub Actions Inactive
@scharron scharron temporarily deployed to CI with Mapbox Tokens July 3, 2025 04:48 — with GitHub Actions Inactive
@scharron scharron temporarily deployed to CI with Mapbox Tokens July 3, 2025 04:48 — with GitHub Actions Inactive
@scharron scharron temporarily deployed to CI with Mapbox Tokens July 3, 2025 04:48 — with GitHub Actions Inactive
@scharron scharron temporarily deployed to CI with Mapbox Tokens July 3, 2025 04:48 — with GitHub Actions Inactive
@mfazekas mfazekas merged commit 3495bad into rnmapbox:main Jul 27, 2025
13 of 15 checks passed
efstathiosntonas pushed a commit to efstathiosntonas/maps that referenced this pull request Aug 8, 2025
…nmapbox#3890)

This bug appears using the new react architecture.
This is because of the id allowOverlap = RNMBXConvertFollyDynamicToId(newProps.allowOverlap); conversions that returns a pointer that is always true instead of the value of the pointed object according to rnmapbox#3730
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: With react new arch, allowOverlap is always true

2 participants