Escrevendo um módulo nativo legado em Swift
Crie um arquivo de ponte Objective-C e uma classe Swift que esteja em conformidade com RCTBridgeModule, exponha um método com RCT_EXPORT_METHOD e chame-o a partir do JS do React Native.
Escrevendo um módulo nativo legado em Swift é uma aula grátis de React Native Academy no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de React Native Academy, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de React Native Academy inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
iOS Native Modules Overview
On iOS, legacy native modules expose Swift or Objective-C code to JavaScript through an Objective-C bridge. Even when you write the implementation in Swift, React Native requires an Objective-C bridge header file to register the module because the RN bridge is built in Objective-C. You write a thin .m bridge file alongside your Swift class.
Creating the Swift Module Class
Create a Swift class that conforms to NSObject and is decorated with the @objc attribute so Objective-C can see it. The class implements the RCTBridgeModule protocol. Swift modules also need @objcMembers on the class so all methods are visible to the bridge without individual @objc annotations on each one.
// CalendarModule.swift
import Foundation
@objc(CalendarModule)
class CalendarModule: NSObject {
@objc
func createCalendarEvent(
_ name: String,
location: String
) {
print('Creating event: \(name) at \(location)')
}
}The Objective-C Bridge File
The bridge file is a plain .m file that does no implementation — it only declares your module and its methods using macros. RCT_EXTERN_MODULE registers the class name, and RCT_EXTERN_METHOD declares each exported method with its parameter labels exactly matching the Swift signatures.
// CalendarModuleBridge.m
#import <React/RCTBridgeModule.h>
@interface RCT_EXTERN_MODULE(CalendarModule, NSObject)
RCT_EXTERN_METHOD(
createCalendarEvent:(NSString *)name
location:(NSString *)location
)
@endExposing the Module Name
React Native identifies your module by the name in RCT_EXTERN_MODULE. On the JavaScript side, this becomes the key on NativeModules. By convention the name matches the Swift class name. If you want a different JavaScript-facing name, you can provide an alias as the second argument to RCT_EXTERN_MODULE, but keeping them the same avoids confusion.
// JavaScript — accessing the iOS module
import { NativeModules } from 'react-native';
const { CalendarModule } = NativeModules;
if (!CalendarModule) {
console.warn('CalendarModule not found — iOS only?');
} else {
CalendarModule.createCalendarEvent('Team Lunch', 'Conference Room A');
}Returning Data with Promises in Swift
Swift native methods that return data use RCTPromiseResolveBlock and RCTPromiseRejectBlock parameters. These are passed in as the last two arguments when declared in the bridge file. Call resolve(value) on success or reject(code, message, error) on failure. On the JS side, await the call as you would any async function.
// Swift method
@objc
func getDeviceModel(
_ resolve: @escaping RCTPromiseResolveBlock,
rejecter reject: @escaping RCTPromiseRejectBlock
) {
let model = UIDevice.current.model
resolve(model)
}
// Bridge file
RCT_EXTERN_METHOD(
getDeviceModel:(RCTPromiseResolveBlock)resolve
rejecter:(RCTPromiseRejectBlock)reject
)
// JavaScript
const model = await CalendarModule.getDeviceModel();Running on the Main Thread
Native module methods run on a background serial queue by default. If your method touches UIKit (which requires the main thread), you must dispatch to the main queue. You can override the static method requiresMainQueueSetup() to return true if the module needs to be initialized on the main thread from the start.
@objc
static func requiresMainQueueSetup() -> Bool {
return true // init on main thread
}
@objc
func openAlert(_ message: String) {
DispatchQueue.main.async {
let alert = UIAlertController(
title: 'Alert',
message: message,
preferredStyle: .alert
)
alert.addAction(UIAlertAction(title: 'OK', style: .default))
UIApplication.shared.keyWindow?.rootViewController?
.present(alert, animated: true)
}
}Exporting Constants to JavaScript
Like Android, iOS native modules can expose constants via the constantsToExport() method. Return a dictionary of values that React Native serializes and attaches to the module object in JavaScript at startup. Constants are synchronous and zero-cost to read after initialization.
// Swift
@objc
func constantsToExport() -> [String: Any]! {
return [
'PLATFORM': 'ios',
'OS_VERSION': UIDevice.current.systemVersion,
'IS_PAD': UIDevice.current.userInterfaceIdiom == .pad
]
}
// Bridge file (add inside the interface)
RCT_EXPORT_MODULE()
// JavaScript
const { PLATFORM, IS_PAD } = NativeModules.CalendarModule;
console.log(PLATFORM, IS_PAD);Sending Events to JavaScript
To push data from native to JavaScript proactively, your Swift module should extend RCTEventEmitter instead of NSObject. Override supportedEvents() to list event names, and call sendEvent(withName:body:) to emit. On the JS side, use NativeEventEmitter to subscribe to the events.
// Swift
@objc(LocationModule)
class LocationModule: RCTEventEmitter {
override func supportedEvents() -> [String]! {
return ['onLocationUpdate']
}
func startTracking() {
sendEvent(withName: 'onLocationUpdate',
body: ['lat': 37.7749, 'lng': -122.4194])
}
}
// JavaScript
import { NativeModules, NativeEventEmitter } from 'react-native';
const emitter = new NativeEventEmitter(NativeModules.LocationModule);
const sub = emitter.addListener('onLocationUpdate', (loc) => {
console.log(loc.lat, loc.lng);
});
// cleanup: sub.remove();Cross-Platform Module Wrapper
When your module only exists on one platform, guard calls with Platform.OS in your wrapper file to avoid runtime crashes on the other platform. A common pattern is to export a no-op stub on unsupported platforms so calling code never needs to check Platform.OS itself.
// CalendarModule.js
import { NativeModules, Platform } from 'react-native';
const { CalendarModule: NativeCalendar } = NativeModules;
export const CalendarModule = {
createEvent: (name, location) => {
if (Platform.OS === 'ios' && NativeCalendar) {
NativeCalendar.createCalendarEvent(name, location);
} else {
console.warn('CalendarModule not available on', Platform.OS);
}
}
};Handling Bridging Header for Mixed Projects
When you add Swift files to an Objective-C project (the default for older React Native), Xcode asks to create a bridging header. This file imports the Objective-C headers that Swift needs to see. You typically import React/RCTBridgeModule.h, React/RCTEventEmitter.h, and any other RN headers your Swift code references. Without this file, Swift cannot see the RCT types.
// YourApp-Bridging-Header.h
// Auto-created by Xcode when adding first Swift file
#import <React/RCTBridgeModule.h>
#import <React/RCTEventEmitter.h>
#import <React/RCTLog.h>
#import <React/RCTUtils.h>Testing the Native Module End-to-End
After writing your Swift class and bridge file, rebuild the app from Xcode (not just Metro) because native code changes require a full native build. Open the iOS Simulator, trigger the JS code that calls your module, and use console.log or Xcode's console to verify the native side executes. Xcode's debugger can set breakpoints in Swift code while the React Native app runs.
// Quick integration test in a component
import React, { useEffect } from 'react';
import { View, Text } from 'react-native';
import { CalendarModule } from './CalendarModule';
export function TestScreen() {
useEffect(() => {
CalendarModule.createEvent('Standup', 'Zoom')
.then((result) => console.log('Event created:', result))
.catch((err) => console.error('Error:', err));
}, []);
return <View><Text>Native Module Test</Text></View>;
}Quick Check
Test your understanding of React Native Mobile Development concepts from this lesson.
Lesson Recap
In this lesson you learned: how to create a Swift class conforming to RCTBridgeModule, write an Objective-C bridge file with RCT_EXTERN_MODULE and RCT_EXTERN_METHOD, and return async data using RCTPromiseResolveBlock and RCTPromiseRejectBlock. You also saw how to emit events with RCTEventEmitter. Next up we explore the modern Turbo Native Module architecture with JSI.
Perguntas Frequentes
A aula “Escrevendo um módulo nativo legado em Swift” é grátis?
Sim — o texto completo de “Escrevendo um módulo nativo legado em Swift” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de React Native Academy, atualize para CoddyKit PRO. O curso de React Native Academy inclui 4 aulas no total.
O que vou aprender em “Escrevendo um módulo nativo legado em Swift”?
Crie um arquivo de ponte Objective-C e uma classe Swift que esteja em conformidade com RCTBridgeModule, exponha um método com RCT_EXPORT_METHOD e chame-o a partir do JS do React Native. Você pratica React Native Academy com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar React Native Academy?
Nenhuma experiência prévia é necessária. React Native Academy no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.
Quanto tempo leva a aula “Escrevendo um módulo nativo legado em Swift”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de React Native Academy?
Sim. Cada aula de React Native Academy inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Escrevendo um módulo nativo legado em Kotlin
- Escrevendo um módulo nativo legado em Swift
- Módulos nativos Turbo com JSI
- Retornos de chamada assíncronos, Promises e eventos do código nativo