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

"Invalid Character \ud835" when used in React Native Android app. #66

Open
jsh8w opened this issue Feb 1, 2022 · 5 comments
Open

"Invalid Character \ud835" when used in React Native Android app. #66

jsh8w opened this issue Feb 1, 2022 · 5 comments

Comments

@jsh8w
Copy link

jsh8w commented Feb 1, 2022

Hello.

We're seeing the following error when using the contentstack JS dependency in a React Native 0.66.4 project. Interestingly, this issue only occurs when the app is run in debug mode. When the app is run in release mode, the issue does not appear.

I've done a fair amount of debugging today and found that when I remove the import of contentstack, the app works correctly and we don't see the error. This leads me to think it's something in the contentstack dependency.

Screenshot 2022-02-01 at 17 40 09

We can see that the \ud835 unicode symbol renders as � and we can see this symbol within the contentstack directory in node_modules.

Screenshot 2022-02-01 at 17 40 41

I'm at a bit of a loss as to what is actually throwing this particular error and why.

Any help would be greatly appreciated.

Thanks.

@uttamukkoji
Copy link
Contributor

Hi @jsh8w ,

Thanks for raising the issue, we will look into this issue and will let you know once we resolve this issue.

@jsh8w
Copy link
Author

jsh8w commented Feb 2, 2022

Thanks @uttamukkoji.

We have done some further digging this morning and found that v3.14.0 works in our React Native project and we no longer see the issue. So it is something that has been introduced in v3.15.0 that is causing the issue.

We will downgrade to v3.14.0 in the meantime whilst you are looking into the issue.

Thanks.

@markymc
Copy link

markymc commented Jun 29, 2023

Just a note that we've just seen this in a Next.js project on Safari iOS 13 (iOS 14 is fine). Any updates on a fix @uttamukkoji?

@cs-raj
Copy link
Contributor

cs-raj commented Sep 11, 2024

Hi @jsh8w thanks for raising this issue we will be looking into the issue ASAP!. Once we have the fix we will update
cc: @netrajpatel

@reeshika-h
Copy link

Hey @jsh8w, can you please check with the latest version of the sdk and let us know if the issue persists?

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

5 participants