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

Publish a working version for RN >= 0.60 users #445

Closed
usmansbk opened this issue Jul 25, 2019 · 5 comments
Closed

Publish a working version for RN >= 0.60 users #445

usmansbk opened this issue Jul 25, 2019 · 5 comments

Comments

@usmansbk
Copy link

Do you want to request a feature or report a bug?
Publish a version with NetInfo fixed for RN >= 0.60

What is the current behavior?
App crash due to aws-appsync-react Rehydrated component and aws-appsync using deprecated NetInfo

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
react-native run-android any project using aws-appsync and aws-appsync-react

What is the expected behavior?
use new @react-native-community/netinfo for rehydrated component and update aws-appsync package.json to use @redux-offline/redux-offline: "2.5.2-native.0"

Which versions and which environment (browser, react-native, nodejs) / OS are affected by this issue? Did this work in previous versions?

System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Memory: 1.92 GB / 7.90 GB
Binaries:
Node: 10.13.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.16.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.2.0.0 AI-181.5540.7.32.5056338

@felixchan
Copy link

Agree

@bernhardt1
Copy link

has anyone implemented a workaround ?

I don't want to wait for a release to upgrade to 0.60.+

@amie-wilt
Copy link

See this comment: #443 (comment)

@manueliglesias
Copy link
Contributor

Updated posted at #443 (comment)

@Ashish-Nanda
Copy link
Contributor

Hi,
We have just released an unstable version that addresses this issue. More details here: #443 (comment)

@usmansbk usmansbk closed this as completed Aug 8, 2019
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

6 participants