Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(react-native): check for nullability in SettingsManager?.settings #758

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

quinnturner
Copy link
Contributor

@quinnturner quinnturner commented Jan 24, 2025

This check seems necessary for the new architecture (on React Native 0.77) to prevent an immediate crash.

Closes #757

Verified

This commit was signed with the committer’s verified signature.
tippmar-nr Marty T
@mobinni
Copy link

mobinni commented Jan 24, 2025

We ran into this as well, it would be great to get this in upstream

@kinyoklion kinyoklion merged commit 3449934 into launchdarkly:main Jan 24, 2025
24 of 25 checks passed
@github-actions github-actions bot mentioned this pull request Jan 24, 2025
kinyoklion pushed a commit that referenced this pull request Jan 24, 2025

Verified

This commit was signed with the committer’s verified signature.
tippmar-nr Marty T
🤖 I have created a release *beep* *boop*
---


<details><summary>react-native-client-sdk: 10.9.5</summary>

##
[10.9.5](react-native-client-sdk-v10.9.4...react-native-client-sdk-v10.9.5)
(2025-01-24)


### Bug Fixes

* **react-native:** check for nullability in SettingsManager?.settings
([#758](#758))
([3449934](3449934))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

react-native iOS settings may not be defined with new architecture
3 participants