Skip to content

fix: prop handling on native Android implementation#592

Draft
jokerttu wants to merge 1 commit into
mainfrom
fix/timing-issue-on-ios-mapview-initialization
Draft

fix: prop handling on native Android implementation#592
jokerttu wants to merge 1 commit into
mainfrom
fix/timing-issue-on-ios-mapview-initialization

Conversation

@jokerttu
Copy link
Copy Markdown
Contributor

Fixes how view controller props are set on view initialization on Android platform

Fixes #590
Fixes #582

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I signed the CLA.
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation
  • I added new tests to check the change I am making
  • All existing and new tests are passing.

Comment on lines -378 to -380
if (fragment.getMapController() != null) {
sink.applyToController(fragment.getMapController());
}
Copy link
Copy Markdown
Contributor Author

@jokerttu jokerttu May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@illuminati1911 this PR fixes situation where controller was not ready, and therefore controller settings on the sink were never applied.

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]: myLocationEnabled not working [Bug]: Widgets do not show up when enabled

2 participants