Solving the Module AppRegistry Issue: Fixing the Unregistered Callable Module Error in RunApplication

In this guide, we will discuss how to solve the "Module AppRegistry is not a registered callable module" error in your React Native application. This issue generally occurs when the React Native packager is not able to find the AppRegistry module, which is responsible for registering the main application component in React Native projects.

By following this step-by-step guide, you will learn how to fix this error and prevent it from occurring in the future.

Table of Contents

Understanding the Error

The "Module AppRegistry is not a registered callable module" error is usually caused by a missing or incorrect registration of the main application component in your React Native project. The error message looks like this:

Unhandled JS Exception: Module AppRegistry is not a registered callable module (calling runApplication)

To fix this error, you need to ensure that the AppRegistry module is properly imported and used in your project.

Step 1: Check Your Entry File

The main entry file (usually index.js or in older projects) should have the following structure:

import {AppRegistry} from 'react-native';
import App from './App';

AppRegistry.registerComponent('YourAppName', () => App);

Make sure that the entry file has the correct structure and points to the correct App component.

Step 2: Verify the AppRegistry Import

Ensure that the AppRegistry module is correctly imported from react-native. The import statement should look like this:

import {AppRegistry} from 'react-native';

If you see any other import statements for AppRegistry, such as:

import AppRegistry from 'react-native/Libraries/AppRegistry';

Replace them with the correct import statement.

Step 3: Validate the Component Registration

Make sure that your main application component is correctly registered with the AppRegistry module. The registration should look like this:

AppRegistry.registerComponent('YourAppName', () => App);

Replace 'YourAppName' with the actual name of your application, and make sure the App component is correctly imported.

Step 4: Clear Cache and Restart Packager

Sometimes, the error persists even after the code has been fixed. In such cases, clearing the cache and restarting the React Native packager can help. To do this, run the following commands:

watchman watch-del-all
npm start -- --reset-cache

Step 5: Check for Multiple React Native Instances

If the error still persists, it might be caused by multiple instances of React Native running in your project. To fix this issue, you can use the react-native-sudo package to identify and remove duplicates. Install the package by running:

npm install -g react-native-sudo

Then, run the following command to identify and remove duplicates:

react-native-sudo duplicates


1. What is the AppRegistry module?

AppRegistry is a JavaScript module in React Native that registers the main application component. It is responsible for managing the lifecycle of your app, including running the app, handling updates, and managing memory. Learn more about AppRegistry in the official React Native documentation.

2. Can I use a custom entry file instead of index.js?

Yes, you can use a custom entry file. However, you need to update the entryFile configuration in your metro.config.js file to point to your custom entry file. Learn more about Metro configuration in the official Metro documentation.

3. What is the difference between and index.ios.js?

In older React Native projects, and index.ios.js were used as separate entry files for Android and iOS platforms, respectively. In newer projects, a single index.js file is used as the entry point for both platforms. If you are working on an older project, make sure to update both and index.ios.js files.

4. How can I check if my main component is registered correctly?

You can check the registration of your main component by looking for the AppRegistry.registerComponent function call in your entry file. Make sure that the component is imported correctly and that the registration function has the correct app name and component reference.

5. What should I do if the error persists after following the steps in this guide?

If the error still persists, you can try creating a new React Native project using the react-native init command and then copying your existing code to the new project. This will ensure that you have the latest dependencies and configurations for your project.

If you have any further questions or need additional assistance, feel free to ask for help on Stack Overflow or the React Native GitHub repository.

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.