Skip to content

Unhandled JS Exception: TypeError #13299

Description

@sphairo

simulator screen shot 04 04 2017 14 11 31

[info][tid:main][RCTBatchedBridge.m:72] Initializing <RCTBatchedBridge: 0x61800019aa90> (parent: <RCTBridge: 0x6000002bb2a0>, executor: RCTJSCExecutor)
2017-04-04 14:10:58.478 [warn][tid:com.facebook.react.JavaScript][RCTBatchedBridge.m:507] Failed to execute source code: Unhandled JS Exception: TypeError
2017-04-04 14:10:58.479 [fatal][tid:main] Unhandled JS Exception: TypeError
2017-04-04 14:10:58.480 iMusica[65976:4706659] -[RCTJSStackFrame objectForKeyedSubscript:]: unrecognized selector sent to instance 0x608000854e20

Activity

  1. cooperka commented on Apr 17, 2017

    @cooperka
    Contributor

    @hramos I'm curious why this was closed? I assume because of bad formatting, but it's unclear.

    I'm having the exact same issue + found Stack Overflow post about it + this issue. Seems like a new bug in RN v0.43.

    2017-04-17 15:48:58.729 [warn][tid:com.facebook.react.JavaScript][RCTBatchedBridge.m:510] Failed to execute source code: Unhandled JS Exception: Error
    2017-04-17 15:48:58.730 [fatal][tid:main] Unhandled JS Exception: Error
    2017-04-17 15:48:58.733 MyApp[45805:8657997] -[RCTJSStackFrame objectForKeyedSubscript:]: unrecognized selector sent to instance 0x60000005f6e0

    It works just fine for Android, but this error prevents running the app on iOS.

    I've cleared every cache there is, nothing helps; reverting to RN v0.42 is the only thing that fixes it for me.

    Unfortunately I'm not able to reproduce using react-native init DemoApp. That means it's probably ultimately some dependency that's causing the issue (but the error message makes it impossible to tell which one). I'll continue debugging and update here if I find anything.

    Update: See reference below for a PR that adds more verbose iOS debug logs.

  2. zackify commented on May 18, 2017

    @zackify

    This is happening to me as well, only when I build for release :(

  3. hramos commented on May 18, 2017

    @hramos
    Contributor

    @cooperka issues that do not use the template are likely to be closed without explanation per https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md

  4. cooperka commented on May 19, 2017

    @cooperka
    Contributor

    Wow, harsh policy @hramos. Seems like it hurts new contributors... explanations are always nice (e.g. the link you just sent is all that's needed).

  5. hramos commented on May 19, 2017

    @hramos
    Contributor

    The text from the link I sent is what populates every new issue. The very first line outlines the policy. With 1,336 issues open as of this writing, we have to be a bit more aggressive if we want to get the issue tracker back on track.

  6. cooperka commented on May 19, 2017

    @cooperka
    Contributor

    In my experience, most people just delete that text and don't read it. The issue template in general is a bad UX (on GitHub's end), but personally I don't think it's an excuse to ignore members of the community when they likely don't even realize they've done something wrong. Simply pasting that link is very helpful and can save others time and frustration.

    "Hi, your description is missing required details and is being automatically closed. Please submit a new issue following the <issue template> and we'll be happy to take another look."

    Just my opinion.

  7. shahankit commented on May 20, 2017

    @shahankit

    Hello did anyone find any solutions to this. I'm suddenly started facing this issue previously it was working. I'm using Xcode 8.3.2 and react-native 0.44 and react 16.0.0-alpha.6. These are all my dependencies:

    {
      "html-entities": "^1.2.1",
      "moment": "^2.18.1",
      "react": "16.0.0-alpha.6",
      "react-native": "0.44.0",
      "react-native-contacts": "^0.8.1",
      "react-native-elements": "^0.12.2",
      "react-native-extended-stylesheet": "^0.4.0",
      "react-native-linear-gradient": "^2.0.0",
      "react-native-vector-icons": "^4.1.1",
      "react-navigation": "^1.0.0-beta.9",
      "striptags": "^3.0.1"
    }

    and my devDependencies:

    {
      "babel-core": "^6.17.0",
      "babel-eslint": "^7.1.0",
      "babel-jest": "19.0.0",
      "babel-plugin-transform-class-properties": "^6.24.1",
      "babel-preset-es2015": "^6.18.0",
      "babel-preset-react-native": "1.9.1",
      "babel-register": "^6.16.3",
      "eslint": "^3.9.1",
      "eslint-config-airbnb": "^14.0.0",
      "eslint-plugin-import": "^2.2.0",
      "eslint-plugin-jsx-a11y": "^3.0.2",
      "eslint-plugin-react": "^6.4.1",
      "eslint-plugin-react-native": "^2.3.1",
      "jest": "19.0.2",
      "jest-react-native": "^18.0.0",
      "react-test-renderer": "16.0.0-alpha.6"
    }

    The line at which it's saying I'm getting error is this on line 1246:

    1237  babelHelpers.toConsumableArray = function (arr) {
    1238    if (Array.isArray(arr)) {
    1239      for (var i = 0, arr2 = Array(arr.length); i < arr.length; i++) {
    1240        arr2[i] = arr[i];
    1241      }return arr2;
    1242    } else {
    1243      return Array.from(arr);
    1244    }
    1245  };
    1246  })(typeof global !== 'undefined' ? global : typeof self !== 'undefined' ? self : this);
    1247  __d(/* ehfood/index.ios.js */function(global, require, module, exports) {'use strict';

    In my case there is only one entry in stack trace which says Unhandled JS Exception: TypeError and global code

  8. zackify commented on May 20, 2017

    @zackify

    @shahankit I have React navigation and React native vector icons as well. For some reason I'm leaning towards a React navigation bug? Just a hunch. No real evidence though :/ I'm debating creating a new project and pasting everything over when I have some time or if it's still an issue when my app launches.

  9. shahankit commented on May 20, 2017

    @shahankit

    Things got solved after running the packager with --reset-cache:

    node node_modules/react-native/local-cli/cli.js start --reset-cache
  10. locked as resolved and limited conversation to collaborators on May 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions