JavaScript strings with NULL character are not handled properly
<Text style={styles.welcome}>{'Hello \u0000 World'}</Text>
The text is cuted to Hello
It does not happen when Debug JS Remotely.
Hello World
https://github.com/gaodeng/RN-NULL-character-ISSUE
info
React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (4) x64 Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Memory: 282.02 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.1 - /usr/local/bin/node
Yarn: 1.5.1 - /usr/local/bin/yarn
npm: 6.8.0 - /usr/local/bin/npm
Watchman: 4.7.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 22, 23, 24, 25, 26, 27, 28
Build Tools: 23.0.1, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.2, 27.0.3, 28.0.0, 28.0.3
System Images: android-18 | Google APIs Intel x86 Atom, android-22 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-24 | Intel x86 Atom_64, android-25 | Google APIs ARM EABI v7a, android-25 | Google APIs Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom, android-P | Google APIs Intel x86 Atom, android-P | Google Play Intel x86 Atom_64
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5314842
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.1 => 0.59.1
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
react-native-create-library: 3.1.2
react-native-git-upgrade: 0.2.7
react-native-rename: 2.1.5
@kelset It's not just Text component have this issue.Any string with NULL character is cuted when It is
passed to native module
Uhm does this happen with both platforms? 馃
Uhm does this happen with both platforms? 馃
@kelset
RN 0.58 ,RN 0.59 have this issue on both platforms.
RN 0.57 only android platform has this issue.
Confirmed repro on Android (Expo 32 => RN 0.57): https://snack.expo.io/@jkcooper/rn24129---null-string-cuts-text
Hi any update related to this issue?
I have the same issue in my app. I use stomp protocol to communicate with other devices and stomp require null character in the end of message, but I can't send this and whole communication breaks.
no updates on my side, sorry 馃槗
can anyone test a repro with the latest 0.60 RC?
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
I just tested this on an iOS Simulator running iOS 13, and React Native version 0.60.5 and this is still happening.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
Some update on this? I can't see any linked commit ... so probably unchanged, hm? Maybe someone could remove the stale-label again?
It seems this bug was reported almost 3 years ago #12731. To me it looks like an issue that needs to be immediately addressed? I don't get why it is not a priority.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
Can some moderator please mark this as "do not close", so that ugly stale-bot does not just cover a not-fixed bug?!?
AFAIK this bug is still present and such NULL-bugs are wild to find.
Most helpful comment
Can some moderator please mark this as "do not close", so that ugly stale-bot does not just cover a not-fixed bug?!?
AFAIK this bug is still present and such NULL-bugs are wild to find.