React Native全局捕获异常和未处理的Promise错误

[1uokun]

全局捕获JS运行时错误代码

react-native / polyfills / error-guard.js

使用global.ErrorUtils.setGlobalHandler全局捕获错误以避免崩溃

if(!__DEV__){
  global.ErrorUtils.setGlobalHandler(async (e, isFatal) => {
      if (isFatal) {
          e.name //错误类型
          e.message //错误信息
          e.componentStack||e.stack //错误代码定位
      }
  }
}

补充：

• isFatal
  建议保留isFatal=true的判断，尽管目前都是true ^[1]

全局捕获未处理的Promise错误

react-native / Libraries / Promise.js

require('promise/setimmediate/rejection-tracking').enable({
    onUnhandled:(id, error = {})=>{
        console.log("全局捕获未处理的Promise错误",id,error)
        console.log(error.name)
        console.log(error.message)
        console.log(error.componentStack||error.stack)
    }
})

重启rn页面

• ios

  NativeModules.BridgeReloader.reload()

• android

  @ReactMethod
  public void reload() {
    Activity activity = getCurrentActivity();
    Intent intent = activity.getIntent();
    activity.finish();
    activity.startActivity(intent);
  }

[1uokun]

打包之后发现捕获的错误代码定位不全

比如像这种的，是因为我们在打包jsbundle的时候没有开启sourceMap模式 --sourcemap-output ，代码被压缩了

Invariant Violation:
Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

    in P
    in RCTView
    in ScrollableTabView
    in RCTView
    in u
    in Connect(u)
    in ReceiveFile
    in O
    in RCTView
    in w
    in RCTView
    in b
    in PanGestureHandler
    in ve
    in GestureHandlerRootView
    in Unknown
    in b
    in x
    in Connect(x)
    in y
    in RCTView
    in RCTView
    in RCTView
    in P
    in w
    in C
    in RCTView
    in RCTView
    in C
    in RCTView
    in V
    in C
    in Unknown
    in D
    in R
    in RCTView
    in c
    in o
    in x
    in RCTView
    in RCTView
    in f
    in o
    in RCTView
    in RCTView
    in c
    in RCTView
    in v
    in RCTView
    in RCTView
    in x