Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Android crashes: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

See original GitHub issue

I hope this is the correct place to create the issue since it seems to be caused by some changes in the way standalone apps are built using expo build:android.

We are detecting crashes on multiple devices: Screen Shot 2019-05-31 at 21 26 14

The error:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
<anonymous>

Backtrace is almost empty: Screen Shot 2019-05-31 at 19 51 50

The interesting part is:

standalone build that was built March 5th and is using the same Expo SDK version and very similar code works fine
when the app was opened via older Expo client app it worked
the app again crashes when opened in the latest Expo client app (v33)

This makes me think that the issue is caused by a build option that was added in the last few weeks.

Expo CLI 2.18.7 environment info:
    System:
      OS: macOS 10.14.4
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 8.15.1 - ~/.nvm/versions/node/v8.15.1/bin/node
      Yarn: 1.13.0 - ~/.nvm/versions/node/v8.15.1/bin/yarn
      npm: 6.4.1 - ~/.nvm/versions/node/v8.15.1/bin/npm
      Watchman: 4.7.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 3.4 AI-183.6156.11.34.5522156
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      @types/expo: ^32.0.10 => 32.0.10 
      @types/react: ^16.4.14 => 16.8.10 
      @types/react-native: ^0.57.43 => 0.57.43 
      @types/react-navigation: ^3.0.6 => 3.0.6 
      expo: ^32.0.5 => 32.0.6 
      react: 16.5.0 => 16.5.0 
      react-native: https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz => 0.57.1 
      react-navigation: ^3.8.1 => 3.8.1 
    npmGlobalPackages:
      expo-cli: 2.18.7

Issue Analytics

State:
Created 4 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

wkozyra95commented, Jun 4, 2019

Yes, we updated sdk-32 by accident with jsc used in react-native@0.59. Sdk32 build will be fixed first, so you need to just rebuild app when it’s ready.

For client we have 2 options

downgrading version jsc to the one used previously (might not work with new react-native in sdk33)
upgrading to newest jsc (it was just released, so it’s a bit risky and might be less stable)

0reactions

Elijencommented, Jun 9, 2019

Thank you, I can confirm that rebuilding the app fixed the issue.