Yes.
Yes.
react-native -v: 0.46.4node -v: v.7.7.2npm -v: 4.1.2Then, specify:
(Write your steps here:)
In IOS and Android emulator it's working
I'm having same problem
same problem
Interestingly same problem. Is react-native broken?
+1
+1 the same on iOS
+1 the same on android
Same problem on Android:
Unable to symbolicate stack trace. The stack is null.
"react": "16.0.0-alpha.12",
"react-native": "0.48.4"
Node version: 8.6.0
NPM version: 5.4.2
OS: Linux Elementary OS
+1 checked on android
i am also facing this issue, any ideas/fixes?
+1 on android physical device
Same for me on an android device.
+1 checked on android
+1, same issue on iOS
Same issue on Android
react-native -v:
react-native-cli: 2.0.1
react-native: 0.41.0
node -v: v8.7.0
npm -v: 5.5.1
+1 checked on android
@medidt
rm -rf ~/.rncache
watchman watch-del-all
npm start -- reset-cache
react-native run-[ios/android]
+1 checked on android
react-native-cli: 2.0.1
react-native: 0.50.3
Node version : v9.2.0
npm version : 5.5.1
+1
+1
+1
+1
Same problem on both iOS and Android!
We are seeing this on debug builds which we also FORCE_BUNDLING on 0.53.0
Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?
I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.
Yes. it is. This problem still exists.
Somehow the react-native run-ios is quit unexpectedly inside the terminal
+1 problem still exists in version 0.55
+1 same issue 0.55.3
+1 version 0.55.4
+1 only when Hot Reloading version 0.55.4
was this gone with rn 0.56?
Hacky way to ignore:
Place console.disableYellowBox = ["Unable to symbolicate"]; anywhere in your code.
I put it at the top of App.js for now and will put it in a better place later.
@lustigdev thanks, until is fixed we don't have that annoying message around 👍
@Drisicus You're welcome, I just wish I wasn't too stupid to just fix the bug. /shrugs/
As you can see, your app needs more security.
More to come tomorrow.
On 11 Aug 2018 21:21, "Michael Lustig" notifications@github.com wrote:
@Drisicus https://github.com/Drisicus You're welcome, I just wish I
wasn't too stupid to just fix the bug. /shrugs/—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/15431#issuecomment-412299257,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASq96SXzdQ4tPVQFaVrpcP3Wfb0NSoKNks5uPzzSgaJpZM4Ox87g
.
@gbsimon87 Sorry, what do you mean?
same problem here. very annoying thing
i've the same problem here yet
+1 -- rn version 0.57.8 -- Android only, iOS does not display error and hot-reloads as expected
Can this be reopened?
got this problem on ios
React Native Environment Info:
System:
OS: macOS 10.14.2
CPU: (12) x64 Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz
Memory: 305.79 MB / 24.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.15.3 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.6.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: 28
Build Tools: 28.0.3
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5314842
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1
npmGlobalPackages:
react-native-cli: 2.0.1
Is this issue has been solved or is there anyone who solved it?
Most helpful comment
Yes. it is. This problem still exists.