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

React Native 0.71 Support #173

Closed
holospeed opened this issue Feb 7, 2023 · 12 comments
Closed

React Native 0.71 Support #173

holospeed opened this issue Feb 7, 2023 · 12 comments

Comments

@holospeed
Copy link

The problem
The SDK is not working with the latest RN minor version ( 0.71 ).

The solution
I would like to use the SDK with the latest RN version.

Alternatives
There is no alternative, which is why the company bought the license.

@louis-launchdarkly
Copy link
Contributor

Hello @holospeed, thank you for reaching out. We are currently in the process of preparing the next React Native SDK major version, and that should have RN 0.71 support. We do not have the exact date yet, and I can give an update when we have an ETA for the release.

@tmadej
Copy link

tmadej commented Feb 8, 2023

This is a blocker for us as well. Paid license. I suspect you will be getting a lot of people now that 0.71.2 is out and expo 48 is in beta.

Is there a pre-release hot fix that will get us unblocked?

@lorenzoangelini
Copy link

@louis-launchdarkly it would perfect if was released a 6.3.1, with the support for react native 0.71. I think that it should be an emergency to make your library available for the last stable release.

@louis-launchdarkly
Copy link
Contributor

Hello @tmadej and @lorenzoangelini, I hear your concern and we understand the interest as we already see a lot of people looking at this issue. The team is currently working on the next major version of RN SDK that will support Contexts. We aim to release the work for Contexts first and will take on upgrading to support RN 0.71 as the immediate next minor release afterward, as upgrading to support RN 0.71 is a non-trivial amount of work.

We also understand the hope to get this as a 6.x minor update. However, the current 6.x supports down to RN 0.64, and the older version of RN is slowing down our uptake of new RN releases. So we may not be able to provide a 6.x SDK that is compatible with RN 0.71, even when getting 0.71 support is a top priority.

@mfelix5
Copy link

mfelix5 commented Feb 10, 2023

We're in the same position with our efforts to upgrade to react-native 0.71 blocked until this is resolved. Thank you for prioritizing this.

@idov-softserve
Copy link

@louis-launchdarkly Sorry for rechecking, but let me clarify this: does your comment mean that RN 0.71 will only be supported by Context-based version of LD SDK? And in order to use it, we'll have to revise the current LD implementation too?

Or is it possible to have RN 0.71 support in SDK that doesn't support Contexts?

And yes, it would be really great to have at least some approximate ETA. Our biggest concern is, of all the other external services and libraries used in our project, LD is the only blocker for RN 0.71 update - and we have no idea when it's expected to be resolved.

@chernandezlt
Copy link

Any solutions here? I have the same problem with React Native 0.71.2

@hwekim
Copy link

hwekim commented Feb 27, 2023

any update on RN > 0.71 support?

@gakinson
Copy link

+1

@louis-launchdarkly
Copy link
Contributor

Hello all, really sorry for the delayed response. As you all may have noticed, we released the 7.x RN SDK last Friday. At this point, getting RN 0.71 is the immediate priority of LaunchDarkly, and we will give more frequent updates on this ticket. I will post another update on Friday giving a concrete ETA.

@idov-softserve While the 7.x React Native SDK is going to be Context-based, the logic is backward compatible (i.e. The user you create will transparently convert to a user context and will work with the existing rules that you have).

@louis-launchdarkly
Copy link
Contributor

We are working on the update and support for RN 0.71 should be coming in about two weeks. I will give another update by end of next week or if there is any release before the end of next week.

@louis-launchdarkly
Copy link
Contributor

Hello all, LaunchDarkly has released https://github.com/launchdarkly/react-native-client-sdk/releases/tag/7.1.1 today supporting RN 0.71. Once again, sorry that this collided with the Context work and took us a while for releasing the support.

If you are using RN SDK 6.x, please follow the migration guide to upgrade to 7.x. While we highly encourage you all to give Contexts a try, there is backward compatibility built in, so flag rules working with only the user will work correctly if you provide the same user object, even after you upgrade.

LaunchDarklyReleaseBot pushed a commit that referenced this issue Dec 19, 2023
Bumps
[react-devtools-core](https://github.com/facebook/react/tree/HEAD/packages/react-devtools-core)
from 4.28.0 to 4.28.4.
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/facebook/react/commits/HEAD/packages/react-devtools-core">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=react-devtools-core&package-manager=npm_and_yarn&previous-version=4.28.0&new-version=4.28.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

You can trigger a rebase of this PR by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/launchdarkly/react-native-client-sdk-private/network/alerts).

</details>

> **Note**
> Automatic rebases have been disabled on this pull request as it has
been open for over 30 days.

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Louis Chan <91093020+louis-launchdarkly@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

No branches or pull requests

9 participants