E ActivityTrigger: activityStartTrigger: not whiteListed com.wesleyapp/com.wesleyapp.MainActivity/1

Overview

(My app name is wesleyapp)

I am able to run my app perfectly fine with react-native run-android after creating a dev bundle.

However when I try to run react-native run-android --variant=release, the app crashes immediately when started. This is after creating a release bundle.

Bundle command being used (without --dev false for dev bundle): react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle

Looking at the logs, there appear to be a few possible culprits. The most likely one, I believe, is the one in the title: E ActivityTrigger: activityStartTrigger: not whiteListedcom.wesleyapp/com.wesleyapp.MainActivity/1

The next most likely candidate would be W unknown:ViewManagerPropertyUpdater: Could not find generated setter for class …

And lastly E ReactNativeJS: { [RangeError: Maximum call stack size exceeded.] line: 343, column: 7038, sourceURL: 'index.android.bundle' }

After scouring these forums and attempting to debug for 3 days now, I’m turning to you for help.

I tried looking through these similar issues but have found no success: https://github.com/facebook/react-native/issues/6692 https://github.com/facebook/react-native/issues/16689 https://github.com/facebook/react-native/issues/20476

React Native version:

Environment: OS: Windows 10 Node: 10.16.2 Yarn: Not Found npm: 6.9.0 Watchman: Not Found Xcode: N/A Android Studio: Version 3.4.0.0 AI-183.6156.11.34.5692245

Packages: (wanted => installed) react: 16.3.1 => 16.3.1 react-native: 0.55.4 => 0.55.4

Package.json

{
  "name": "wesleyapp",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "@babel/runtime": "^7.7.7",
    "react": "16.3.1",
    "react-native": "0.55.4",
    "stacktrace-parser": "0.1.4",
    "react-native-audio": "^4.3.0",
    "react-native-image-picker": "^1.1.0",
    "react-native-sound": "^0.11.0",
    "react-native-tts": "^3.0.0",
    "vue-native-core": "0.0.8",
    "vue-native-helper": "0.0.11",
    "vuex": "^3.1.1",
  },
  "devDependencies": {
    "babel-jest": "24.8.0",
    "babel-preset-react-native": "4.0.1",
    "jest": "24.8.0",
    "react-test-renderer": "16.3.1",
    "vue-native-scripts": "0.0.16"
  },
  "jest": {
    "preset": "react-native"
  }
}

Android logs:

https://gist.github.com/bmbmjmdm/5f6c971fc43a207c68edcd65949aa77f

[react-native-bot]

I am closing this issue because it does not appear to have been verified on the latest release, and there has been no followup in a while.

If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue with up-to-date information by clicking here.

[derwaldgeist]

activityStartTrigger: not whiteListed is not an error. It only says that your activity is not getting some very special privileges reserved to some system (or vendor) apps.

If it is not an error, then why is it flagged as one?