expo: Uncaught Error: Module AppRegistry is not a registered callable module and Uncaught Error: undefined is not an object

I received three different errors from users using the Android version of my app in the play store. The two errors below came from one device and I already opened another issue that I received on someone else’s device. This is only on specific Android devices though and I can’t reproduce it on mine. Is there anything I can do about these:

Uncaught Error: Module AppRegistry is not a registered callable module (calling runApplication)
value@cached-bundle-experience-%40ahadcove***

Uncaught Error: undefined is not an object (evaluating’h.getExponentPushTokenAsync’)
<unknown>@cached-bundle-experience-%40ahadcove***

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 15 (5 by maintainers)

Most upvoted comments

I had the same issue. After trying so many times, I figured out the final working SOLUTION: uninstall Expo, stop using it, subscribe this issue ticket until it’s closed then re-install Expo.

haotangio on Nov 13, 2017

@brentvatne I am only getting this “AppRegistry is not a callable module” in iOS only in android it’s working just fine.

samassango on Dec 11, 2017

hello!

@AhadCove - it’s called getExpoPushTokenAsync, not getExponentPushTokenAsync, if you still have this error then we need to see the code that you’re using (the entire file, not just one or two lines) to help you out. this is not a bug in expo, there is some error in your code.

@mehtaanshul and perhaps others with the same error that @mehtaanshul posted: this error is described in the release notes and also easily googleable. View.propTypes was removed in react-native in 0.48, and unfortunately it only causes problems with development mode disabled.

some library that you use, or your own app code, tries to use View.propTypes.style but that throws an error because View.propTypes is not an object anymore. this problem does not come from expo itself, fwiw. we do try to do our best to make upgrades as easy as possible, and we’ll try to keep a closer eye out for upstream issues like this in order to make sure that they at least show up as errors in development mode.

for everyone in this thread and others who stumbled across it - “AppRegistry is not a registered callable module” just means that there is some error in your code that prevents the JS from being loaded – the error underneath it is the error that you are looking for.

if anyone has specific error messages that they are having trouble with, please post a new issue with the information on what the error message is (“AppRegistry is not a …” is not the actual error message)

brentvatne on Nov 13, 2017