Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Possible Unhandled Promise Rejection: Geocoder is not running

See original GitHub issue

Environment

SDK 32

My target is Android and IOS. I am experiencing this error on my android device, i haven’t yet tested it on the iphone.

Steps to Reproduce

Cmd: expo init geocodebug
Choose blank template
Name: geocodedebug Slug: geocodebug
Cd geocodebug
Cmd: npm install --save react-navigation
Copy files from the Github repo and overwrite in ‘geocodedebug’ folder
Npm start
Open app in expo
Click on the ‘Open shared link’ button.

Expected Behavior

I expected the full output (latitude,longitue) of the translated address from the geocode process in the console.

Actual Behavior

No output on the console from the geocoder function. Instead error:

`[Unhandled promise rejection: Error: Geocoder is not running.]

node_modules\react-native\Libraries\BatchedBridge\NativeModules.js:146:41 in createErrorFromErrorData
node_modules\react-native\Libraries\BatchedBridge\NativeModules.js:95:55 in <unknown>
… 5 more stack frames from framework internals`

Reproducible Demo

Github repo

Download these files and place and replace them in your new project. The issue seems to come up only when I use the Linking.addEventListener('url', this._handleRedirect); and then continue to another page to then convert the address to coördinates.

Issue Analytics

State:
Created 5 years ago
Comments:12 (5 by maintainers)

Top GitHub Comments

1reaction

cruzachcommented, Mar 19, 2019

I’m running the same version of the Expo CLI as you, only major difference is npm version (I’m using 6.9.0).

Was there anything significantly different about the environment of the computer you were able to get it to work correctly on?

0reactions

stale[bot]commented, Mar 10, 2020

It’s been a while since we’ve had any activity on this issue, and seeing as it needs more info before we can properly address it, we will be closing it in one month. If you’ve found a fix, please share it! Otherwise, please provide the info we asked for, especially a reproducible example. Thanks!