Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expo Android app crashing right after launch, iOS working, new NativeEventEmitter() was called #29174

Closed
jankamon opened this issue May 28, 2024 · 2 comments
Labels
incomplete issue: missing or invalid repro A minimal reproducible example is required for most issues needs review Issue is ready to be reviewed by a maintainer

Comments

@jankamon
Copy link

Minimal reproducible example

https://github.com/jankamon/my-app

What platform(s) does this occur on?

Android

Did you reproduce this issue in a development build?

Yes

Summary

I build app using Expo and discovered that the Android version of my app is crashing right after launch (iOS version is working). I reproduced this by launching "npx expo start --no-dev --minify" but in normal dev mode app is working.
Console is silent, only warning which I see in Expo Go is "new NativeEventEmitter() was called..." but I can't read it all, it's cut in half and it's not possible to open this warning and see details.

I updated dependencies (below) and tried debug with Sentry but it seems that bug occurs before App.tsx is launched because I didn't log anything.

On fresh created project by "npx create-expo-app@latest" I have the same problem but here even in dev mode Android is throwing the same error.

Can you help me what is going on and why Expo isn't logging any errors?

Environment

expo-env-info 1.2.0 environment info:
System:
OS: Windows 10 10.0.19045
Binaries:
Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
expo: ~51.0.8 => 51.0.8
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.1 => 0.74.1
react-native-web: ~0.19.12 => 0.19.12
Expo Workflow: managed

Expo Doctor Diagnostics

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check for issues with metro config
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!

@jankamon jankamon added the needs validation Issue needs to be validated label May 28, 2024
@expo-bot expo-bot added needs review Issue is ready to be reviewed by a maintainer and removed needs validation Issue needs to be validated labels May 28, 2024
@brentvatne brentvatne added the incomplete issue: missing or invalid repro A minimal reproducible example is required for most issues label May 30, 2024
@expo-bot
Copy link
Collaborator

Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue.

The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue.

A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own.

Resources

Common concerns

"I've only been able to reproduce it in private, proprietary code"

You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase.

"I didn't have time to create one"

That's understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template.

"You can reproduce it by yourself by creating a project and following these steps"

This is useful knowledge, but it's still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue.

@brentvatne
Copy link
Member

i tried to reproduce this using the information given and i was unable to do so

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incomplete issue: missing or invalid repro A minimal reproducible example is required for most issues needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests

3 participants