-
Notifications
You must be signed in to change notification settings - Fork 200
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
v4.4.0 does not work with latest react-native #156
v4.4.0 does not work with latest react-native #156
Comments
hi @leoschweizer, |
@Khaledgarbaya btw, the
so |
Hey @leoschweizer looks like it's a problem with platform.js, will see what I can do |
let's hope this PR gets fixed bestiejs/platform.js#130 |
Hi @leoschweizer can you get this branch of SDK-core and |
@Khaledgarbaya I can't get this to work but I'm not sure if I'm doing this correctly. Here's what I did:
But the error remains the same. Since I'm not seeing the code changes either I guess I'm missing something? |
hi @leoschweizer hmm can you clone |
@Khaledgarbaya I did, but now I ran into this: facebook/react-native#637 - so |
@leoschweizer 😭 ok I will try to do some tests on other platforms and release a patch version by tomorrow. Sorry about the ping pong |
Looks like we are still blocked here since bestiejs/platform.js#130 is merged but not released yet :( |
@leoschweizer I released https://github.com/contentful/contentful-sdk-core/releases/tag/v3.14.2 which should now work in react-native. Can you upgrade all your contentful.js (plus check that you got the latest contentful-sdk-core) and confirm if this is now working for you in react native? A small test on my local machine was promising :) |
@axe312ger I can confirm that it is working for me now 👍 |
Awesome! :) |
I'm using the contentful JS-SDK in a react-native project. After upgrading from 4.3.0 to 4.4.0, the app no longer works due to contentful throwing an error on import:
in
contentful.js:11297
which is the last line of this block:I've downgraded to
4.3.0
and everything works as expected again.The text was updated successfully, but these errors were encountered: