NativeRunnable.java: Failed to create Value from JSON:

[NicWickman]

• Review the documentation: https://facebook.github.io/react-native
• Search for existing issues: https://github.com/facebook/react-native/issues
• Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

react-native: 0.57.7

React Native Environment Info:
System:
OS: Windows 10
CPU: (12) x64 Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
Memory: 2.48 GB / 11.90 GB
Binaries:
Yarn: 1.9.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.2.0 - C:\Program Files\nodejs\npm.CMD

Description

Fetching a photo object from the Google Maps API causes a fatal error. Works as expected on RN 55.4, but crashes on 57.7

"Error calling RCTDeviceEventEmitter.emit
Failed to create Value from JSON:"

Reproducible Demo

React Native 57.7

fetch('https://maps.googleapis.com/maps/api/place/photo?maxwidth=200&photoreference=CnRvAAAAwMpdHeWlXl-lH0vp7lez4znKPIWSWvgvZFISdKx45AwJVP1Qp37YOrH7sqHMJ8C-vBDC546decipPHchJhHZL94RcTUfPa1jWzo-rSHaTlbNtjh-N68RkcToUCuY9v2HNpo5mziqkir37WU8FJEqVBIQ4k938TI3e7bf8xq-uwDZcxoUbO_ZJzPxremiQurAYzCTwRhE_V0' + '&key={SOME API KEY}')

[code-jenn-or]

I also have this issue on 57 when it is a photo. I've racked my brain trying to figure out a way around this, but so far nothing.

Can reproduce by a fetch call that is pulling a photo response. Like above.

[NicWickman]

As an alternative for now I am using the package react-native-fetch-blob which works as expected.

…

On Dec 20, 2018 8:54 PM, "Jenn" ***@***.***> wrote: I also have this issue on 57 when it is a photo. I've racked my brain trying to figure out a way around this, but so far nothing. Can reproduce by a fetch call that is pulling a photo response. Like above. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22445 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASZsAQIqJ5WnEuuCq03SO-0GzLdPCUwqks5u7GlvgaJpZM4Y3bdk> .

[Pingou]

Same problem using XMLHttpRequest().

[AppleMango23]

Error will come out when i try to read a photo, but text file just work fine. Is there anyone know how to make it work? : (

[NicWickman]

Use axios package instead of fetch for now

…

On Jan 28, 2019 12:40 AM, "nonoyek" ***@***.***> wrote: Error will come out when i try to read a photo, but text file just work fine. Is there anyone know how to make it work? : ( — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22445 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASZsAfd76jKsVsOk5zW3nBxBviZO--8Lks5vHrd9gaJpZM4Y3bdk> .

[darknblack]

Facing the same problem. Face no issues when using axios.

[kelset]

(sorry clicked the close button by mistake!)

Can anyone create a repro with 0.59 (via the init command) and link it here?

[grabbou]

Hello there 👋 this issue doesn't have a repro (which means, a react-native init-ed project with the minimal changes that leads to creating the same issue you are reporting). Unfortunately, I have no way of helping you in a meaningful way – there is no easy way for me to recreate the situation and check that the issue reported is still there when changing the code.

Because of this, we are going to close this issue - but if a repro is shared, we are happy to reopen it 🤗

[grabbou]

Update: I've tried reproducing with another image and it downloads it w/o issues. Please provide Snack link, here's my example: https://snack.expo.io/HkeWCL0PV

[cahaverl]

@grabbou Actually that Snack example was very helpful. It does crash on the Honor 7X (made by Huawei) BND-L24. Getprop gives: [ro.build.version.base_os]: [HONOR/BND-L24/HWBND-H:8.0.0/HONORBND-L24/344(C567):user/release-keys].

With the latest version of the Expo app (2.11.4), I get crashes for Expo SDK versions 31 and 32, but not 33, leading to hope that this is fixed in RN 0.59.8.

Huawei-derived phones have been the most susceptible to this bug in my experience.

[cahaverl]

@grabbou I found also that the "Tap to Play" (again for https://snack.expo.io/HkeWCL0PV) in Snack on Android follows the same pattern, failure for SDKs 31 and 32, success for SDK 33.

[wiess-huabo]

why this is close? come across this issue.