Cannot find native module 'Burnt' on recent React Native (0.79.2) / Expo SDK (^53.0.10) with Hermes

[Yuya-Arashidani]

Library Version

• burnt: ^0.12.2

Environment

• React Native Version: 0.79.2
• Expo SDK Version: ^53.0.10
• Platform: iOS
• Project Setup: Generated using yarn create tamagui@latest. The application code is largely unchanged from the default starter template.
  Relevant package.json (from apps/expo):

{
  "dependencies": {
    // ... 
    "burnt": "^0.12.2",
    "expo": "^53.0.10",
    "react-native": "0.79.2"
    // ...
  }
  // ...
}

Problem Description

When running the native application on iOS, the application fails to load the Burnt native module. This occurs in a project recently scaffolded with create-tamagui@latest, with minimal modifications to the starter code.

Steps to Reproduce

1. Create a new Tamagui application using yarn create tamagui@latest.
2. The generated project structure includes an apps/expo workspace with burnt: ^0.12.2 as a dependency.
3. Attempt to run the native application (e.g., using yarn native)
4. Toast notifications do not function, and an error occurs before the toast is triggered.

Errror Messages

The following errors are observed in the console:

ERROR  Error: Cannot find native module 'Burnt', js engine: hermes
ERROR  TypeError: Cannot read property 'toast' of undefined, js engine: hermes

[Yomyer]

It’s because you’re running the app with Expo Go.

You first need to build for iOS or Android:

yarn ios

That will compile the app and open the iOS simulator (same applies for Android).

If you then run yarn native, you need to switch to a development build with “s”, and after that you can open either iOS with “i” or Android with “a”.

[chaudepark]

I have the same issue.
Run yarn ios and then run yarn native again. Press s to work on my phone, getting the same error again. I scanned the code while switching Expo go because the code, while in development build, doesn't work. Because the code displays nothing when scanning, but switching to Expo go does work. On the other hand, iOS simulator never shows the same error 🤔