Expo框架下React Native Headless JS遇AppRegistry未注册报错求助

First, let's unpack the two key errors you're seeing and why they're happening:

1. "The Expo SDK requires Expo to run..." #

Your custom LockScreenOpenService Java class is a native Headless JS service, but when it starts, it's not loading the Expo native module environment. Expo's JavaScript code relies on its wrapped native modules to function—since this service is bypassing Expo's native setup, the SDK throws this error.

2. "Module AppRegistry is not a registered callable module..." #

Expo has its own initialization flow for React Native's AppRegistry. When your native service calls startHeadlessTask, Expo's registry hasn't been properly initialized yet, leading to this unregistered module error.

Solutions Based on Your Expo Workflow #

Option 1: Use Expo's Official Background Task APIs (Managed Workflow) #

If you're using the Managed Expo Workflow (no custom native code), you can't use raw Headless JS services like HeadlessJsTaskService directly. Instead, use Expo's built-in tools for background tasks:

1. Install required packages:

npx expo install expo-task-manager expo-background-fetch

2. Rewrite your task using Expo Task Manager in App.js:

import React, { useEffect } from 'react';
import * as TaskManager from 'expo-task-manager';
import * as BackgroundFetch from 'expo-background-fetch';

// Define your task identifier
const LOCK_SCREEN_TASK = 'LockScreenOpenService';

// Define the background task logic
TaskManager.defineTask(LOCK_SCREEN_TASK, async ({ data, error }) => {
  if (error) {
    console.error('Lock screen task error:', error);
    return BackgroundFetch.Result.Failed;
  }
  
  console.log("== Debug: Received LockScreen View Open");
  return BackgroundFetch.Result.NewData;
});

// Register the task when the app starts
async function registerLockScreenTask() {
  try {
    await BackgroundFetch.registerTaskAsync(LOCK_SCREEN_TASK, {
      minimumInterval: 1, // Adjust based on your needs
      stopOnTerminate: false, // Keep task running after app closes
      startOnBoot: true, // Restart task on device reboot
    });
    console.log('Lock screen task registered successfully');
  } catch (err) {
    console.error('Failed to register task:', err);
  }
}

export default function App() {
  useEffect(() => {
    registerLockScreenTask();
  }, []);

  // Rest of your app code...
}

If you need to listen specifically for lock screen events, pair this with expo-device to detect device state changes, or use expo-sensors for more granular triggers.

Option 2: Switch to Bare Workflow (For Custom Native Code) #

If you absolutely need to use a custom native HeadlessJsTaskService, switch to Expo's Bare Workflow (which allows custom native code) and follow these steps:

1. Convert your project to Bare Workflow:

npx expo prebuild

This generates native Android/iOS projects with Expo's modules pre-integrated.

2. Update your LockScreenOpenService.java to initialize Expo's environment before starting the task:

import android.app.Application;
import android.content.Intent;
import android.os.Bundle;
import com.facebook.react.HeadlessJsTaskService;
import com.facebook.react.HeadlessJsTaskConfig;
import com.facebook.react.bridge.Arguments;
import com.facebook.react.ReactApplication;
import com.facebook.react.ReactNativeHost;
import expo.modules.core.ExpoModulesPackage;

public class LockScreenOpenService extends HeadlessJsTaskService {
  @Override
  protected HeadlessJsTaskConfig getTaskConfig(Intent intent) {
    // Ensure Expo's native modules are initialized
    Application application = getApplication();
    if (application instanceof ReactApplication) {
      ReactNativeHost reactNativeHost = ((ReactApplication) application).getReactNativeHost();
      // Initialize Expo modules and create React context
      new ExpoModulesPackage((ReactApplication) application);
      reactNativeHost.getReactInstanceManager().createReactContextInBackground();
    }

    Bundle extras = intent.getExtras();
    if (extras != null) {
      return new HeadlessJsTaskConfig(
          "LockScreenOpenService",
          Arguments.fromBundle(extras),
          5000, // Task timeout
          false // Disallow task in foreground
      );
    }
    return null;
  }
}

3. Verify your AndroidManifest.xml entry remains correct:

<service android:name=".lockscreen.LockScreenOpenService" android:enabled="true" android:exported="true" />

Key Takeaway #

Managed Expo doesn't support custom native Headless JS services because it wraps the entire native layer. Stick to Expo's background task APIs for Managed Workflow, or switch to Bare Workflow if you need full native control.

内容的提问来源于stack exchange，提问作者Jin Beom Jeong