Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
504 views
in Technique[技术] by (71.8m points)

react native - Firebase Crashlytics non-fatal issue in main.jsbundle

I have recently been receiving emails from Firebase Crashlytics reporting that issue detected in main.jsbundle. Screenshot as per below

enter image description here

However if I were to click into my app's Crashlytics, I can't find this issue in the issue lists at all. Even if I filtered out the specific build version, I still can't find it.

I'm only navigated to the stack trace below, while I click on the LEARN MORE button in crashlytics's email.

enter image description here

It's very different from rest issue reported by Crashlytics. Any idea what is this about?

question from:https://stackoverflow.com/questions/65939473/firebase-crashlytics-non-fatal-issue-in-main-jsbundle

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

Are you using async/await or promise's chaining? One of your promises is not catching exceptions.

Example for async/await:

try {
  const result = await doSomething();
  ....
} catch (error) {
  console.warn(error);
}

or chaining:

doSomething
  .then(e => {...})
  .finally(...)
  .catch(error => {...})

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...