0Pricing
React Native Academy · 课时

来自原生代码的异步回调、Promise 与事件

使用 Promise 和 RCTPromiseResolveBlock 从原生代码返回数据,使用 RCTEventEmitter 向 JavaScript 发送事件,并在 JS 中使用 NativeEventEmitter 处理事件。

来自原生代码的异步回调、Promise 与事件 是 CoddyKit 上的免费 React Native Academy 课时。 这是第 4 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 React Native Academy 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 React Native Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

Why Native Methods Must Be Async

React Native native module methods run on a native background thread, not the JavaScript thread. Because the two runtimes run independently, native code cannot return a value directly. Instead it must communicate results back to JavaScript through one of three patterns: Callbacks, Promises, or Events. Each pattern suits different use cases based on how many responses you need and when they arrive.

Callbacks: The Original Pattern

Callbacks are JavaScript functions passed as arguments to a native method. The native code stores them and invokes them later. The convention is to pass two callbacks — one for success and one for failure — similar to Node.js error-first callbacks. A callback can only be invoked once; invoking it twice throws a runtime error on the JS side.

// Kotlin
@ReactMethod
fun readFile(
    path: String,
    successCallback: Callback,
    errorCallback: Callback
) {
    try {
        val content = java.io.File(path).readText()
        successCallback.invoke(content)
    } catch (e: Exception) {
        errorCallback.invoke(e.message)
    }
}

// JavaScript
NativeModules.FileModule.readFile(
  '/data/test.txt',
  (content) => console.log(content),
  (error) => console.error(error)
);

Promises: The Modern Approach

Promises are now the preferred pattern for native methods that return a single result. Add Promise as the final parameter in Kotlin or RCTPromiseResolveBlock / RCTPromiseRejectBlock in Swift. React Native automatically wraps the call in a JS Promise, so you can await it or chain .then(). Promises are self-documenting and integrate naturally with async/await in modern JavaScript.

// Kotlin
@ReactMethod
fun fetchUserData(userId: String, promise: Promise) {
    Thread {
        try {
            val data = apiClient.getUser(userId)
            val map = Arguments.createMap()
            map.putString('name', data.name)
            map.putString('email', data.email)
            promise.resolve(map)
        } catch (e: Exception) {
            promise.reject('FETCH_ERROR', e.message, e)
        }
    }.start()
}

// JavaScript
try {
  const user = await NativeModules.UserModule.fetchUserData('123');
  console.log(user.name);
} catch (err) {
  console.error('Failed:', err.message);
}

Promise Rejection Codes and Messages

When rejecting a Promise, provide three pieces of information: an error code string (like 'PERMISSION_DENIED'), a human-readable message, and optionally the native exception object. On the JavaScript side these become properties of the caught Error: err.code, err.message, and err.nativeStackAndroid or err.nativeStackIOS for debugging.

// Kotlin — structured rejection
@ReactMethod
fun openCamera(promise: Promise) {
    val permission = ContextCompat.checkSelfPermission(
        reactApplicationContext,
        Manifest.permission.CAMERA
    )
    if (permission != PackageManager.PERMISSION_GRANTED) {
        promise.reject(
            'PERMISSION_DENIED',
            'Camera permission is not granted. Please enable it in settings.',
            null
        )
        return
    }
    // proceed...
    promise.resolve(true)
}

// JavaScript
try {
  await NativeModules.CameraModule.openCamera();
} catch (err) {
  if (err.code === 'PERMISSION_DENIED') showSettingsPrompt();
}

Events: Push Data from Native to JS

Events are the right tool when native needs to push data to JavaScript multiple times — such as location updates, sensor readings, download progress, or Bluetooth device discovery. Events flow one-way: native emits, JS listens. On Android you use RCTDeviceEventEmitter; on iOS you use RCTEventEmitter methods.

// Kotlin — emit an event
private fun sendEvent(name: String, data: WritableMap) {
    reactApplicationContext
        .getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter::class.java)
        .emit(name, data)
}

// Call this from a background task:
val map = Arguments.createMap()
map.putDouble('progress', 0.75)
map.putString('fileName', 'video.mp4')
sendEvent('downloadProgress', map)

Listening to Events in JavaScript

On the JS side, subscribe to native events using NativeEventEmitter. Pass it the native module object that emits events, then call addListener with the event name and a handler. Always store the subscription reference and call subscription.remove() in a cleanup function (e.g., inside useEffect's return) to prevent memory leaks from stale listeners.

import React, { useEffect, useState } from 'react';
import { NativeModules, NativeEventEmitter } from 'react-native';

const emitter = new NativeEventEmitter(NativeModules.DownloadModule);

export function DownloadScreen() {
  const [progress, setProgress] = useState(0);

  useEffect(() => {
    const sub = emitter.addListener('downloadProgress', (event) => {
      setProgress(event.progress);
    });
    return () => sub.remove(); // cleanup
  }, []);

  return <ProgressBar value={progress} />;
}

addListener and removeListeners on iOS

On iOS, any class that extends RCTEventEmitter must implement two boilerplate methods: addListener(_:) and removeListeners(_:). These let the native module know when JS is actively listening so it can avoid emitting events to an empty audience. Failing to implement them causes a warning in development and may throw in newer RN versions.

// Swift
@objc(DownloadModule)
class DownloadModule: RCTEventEmitter {

  override func supportedEvents() -> [String]! {
    return ['downloadProgress', 'downloadComplete', 'downloadError']
  }

  // Required boilerplate
  override func addListener(_ eventName: String!) { }
  override func removeListeners(_ count: Double) { }

  func reportProgress(_ pct: Double, file: String) {
    sendEvent(
      withName: 'downloadProgress',
      body: ['progress': pct, 'fileName': file]
    )
  }
}

WritableArray for List Results

When you need to return an array from native to JavaScript, use WritableArray and Arguments.createArray(). You push items into it with typed methods like pushString, pushInt, and pushMap. Nested structures (maps inside arrays, arrays inside maps) work seamlessly — React Native serializes the entire tree.

// Kotlin
@ReactMethod
fun listBluetoothDevices(promise: Promise) {
    val array = Arguments.createArray()
    val devices = bluetoothAdapter?.bondedDevices ?: emptySet()
    for (device in devices) {
        val map = Arguments.createMap()
        map.putString('name', device.name)
        map.putString('address', device.address)
        array.pushMap(map)
    }
    promise.resolve(array)
}

// JavaScript
const devices = await NativeModules.BleModule.listBluetoothDevices();
devices.forEach(d => console.log(d.name, d.address));

Choosing Between Callbacks, Promises, and Events

Use this decision guide: Callbacks — legacy codebases or when you need exactly two outcomes (success/error) in one shot. Promises — any single async operation that resolves once; pairs perfectly with async/await. Events — when native must push multiple updates over time (streams, sensors, ongoing background tasks). Most new code should prefer Promises for one-time results and Events for streams.

// Decision chart as comments
// One result, awaitable? → Promise
const photo = await NativeModules.Camera.takePhoto();

// Multiple results over time? → Event emitter
const sub = emitter.addListener('locationUpdate', handleLocation);
NativeModules.LocationModule.startWatching();

// Legacy API you must support? → Callback
NativeModules.OldModule.doThing(onSuccess, onError);

Thread Safety for Event Emission

A common bug is emitting events from a background thread without a listener registered yet, causing a crash or silent drop. On Android, guard with a listener count check. On iOS, RCTEventEmitter handles this internally — sending to zero listeners is silently ignored. Always start background work (GPS polling, BLE scanning) only after the JS side has called the start method, not in the module's initializer.

// Kotlin — safe event emit with listener guard
private var listenerCount = 0

@ReactMethod
fun addListener(eventName: String) {
    listenerCount++
}

@ReactMethod
fun removeListeners(count: Int) {
    listenerCount -= count
}

private fun safeSendEvent(name: String, data: WritableMap) {
    if (listenerCount > 0) {
        reactApplicationContext
            .getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter::class.java)
            .emit(name, data)
    }
}

Testing Native Module Callbacks in Jest

When unit-testing components that use native modules, mock the module in Jest setup. Replace the native module with a Jest mock object that returns resolved Promises or calls callbacks with test data. This lets you test the JS side in isolation without a real device. Place module mocks in __mocks__/react-native.js or a setup file declared in jest.config.js.

// __mocks__/NativeModules.js
jest.mock('react-native', () => ({
  ...jest.requireActual('react-native'),
  NativeModules: {
    CameraModule: {
      takePhoto: jest.fn(() => Promise.resolve('/path/to/photo.jpg')),
      openCamera: jest.fn(() => Promise.resolve(true)),
    },
    DownloadModule: {},
  },
}));

// In your test
it('captures a photo and sets image URI', async () => {
  const { getByTestId } = render(<CameraScreen />);
  fireEvent.press(getByTestId('shutter-btn'));
  await waitFor(() =>
    expect(getByTestId('preview').props.source).toEqual(
      { uri: '/path/to/photo.jpg' }
    )
  );
});

Quick Check

Test your understanding of React Native Mobile Development concepts from this lesson.

Lesson Recap

In this lesson you learned: how to return data from native using Callbacks, Promises, and Events, how to use WritableMap and WritableArray to pass complex data structures, and how to listen to native events safely in React components with useEffect cleanup. You also saw how to mock native modules in Jest for unit testing. Next up we explore Expo Config Plugins.

常见问题解答

「来自原生代码的异步回调、Promise 与事件」课时是免费的吗?

是的 — 「来自原生代码的异步回调、Promise 与事件」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 React Native Academy 课程的其余内容,请升级到 CoddyKit PRO。 React Native Academy 课程共包含 4 节课。

「来自原生代码的异步回调、Promise 与事件」这节课中我会学到什么?

使用 Promise 和 RCTPromiseResolveBlock 从原生代码返回数据,使用 RCTEventEmitter 向 JavaScript 发送事件,并在 JS 中使用 NativeEventEmitter 处理事件。 你通过在浏览器中直接运行的动手代码来练习 React Native Academy,全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 React Native Academy 需要有经验吗?

无需任何先前经验。CoddyKit 上的 React Native Academy 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 4 节课,共 4 节。

「来自原生代码的异步回调、Promise 与事件」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 React Native Academy 课中编写并运行代码吗?

能。每节 React Native Academy 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 使用 Kotlin 编写旧版原生模块
  2. 使用 Swift 编写旧版原生模块
  3. 使用 JSI 编写 Turbo 原生模块
  4. 来自原生代码的异步回调、Promise 与事件
← 返回 React Native Academy