Troubleshooting

This guide helps you troubleshoot issues in Nitro and should give you enough context to open a well-formed issue, even if you're not a native developer.

Minimum requirements

First, make sure you meet the minimum requirements for Nitro.

Ask for help

If you want to ask for help, join our Margelo Community Discord.

Build error

If your app fails to build after installing Nitro or a library powered by Nitro, make sure to post full build logs:

iOS

1. Build the app with Xcode.

2. When the build fails in Xcode, open the "Report Navigator" tab from within the left sidebar:

   

3. Then, find the most recent build attempt and click on "Build":

   

4. Scroll through the build report and find the step(s) that failed to build. They usually have a ❌ icon on the left. Click on the parent item's hamburger menu on the right to open the full logs:

   

5. Scroll down through the build logs (the long part is just the command invocation) to find the actual error messages:

   

6. Copy those bottom logs only (not the build command invocation above) and create a GitHub issue with that.

Android

1. Build the app with Android Studio.

2. When the build fails in Android Studio, open the "Build" tab from within the bottom left sidebar:

   

3. Find the top-most entry in the Build window (which contains full unfiltered logs) and click it:

   

4. Copy those full logs and paste them in the GitHub issue (or serve via pastebin). Make sure they actually contain the error message and not just something like "BUILD FAILED in 7s" (which is what most people post):

   

Runtime error

If your app crashes at runtime, make sure to inspect the native logs.

iOS

1. Run your app through Xcode

2. If the app hits an unhandled error, it should pause in Xcode. Share the line it stopped in, and also the call-stack (stacktrace) on the left side.

3. If the app didn't pause, then it might have been a handled error - in this case just check the Xcode logs at the bottom:

   

Android

1. Run your app through Android Studio by using the Debug button (🪲)

2. If the app hits an unhandled error, it should pause in Android Studio. Share the line it stopped in, and also the call-stack (stacktrace) on the bottom window.

3. If the app didn't pause, then it might have been a handled error - in this case just check the Android Logcat logs at the bottom: