14

“hi all, we are cancelling the last two releases this year due to instability that we can’t fix by the cut off. If the server returns an error, every react-native built component crashes and stops working until a relaunch”

Comments
  • 1
    This reaction is related equal parts to the issue and the decision to use react-native
  • 0
    Wait, what?
  • 0
    @Root I don't have full details as it doesn't involve my team. What I understand is:

    40 - 50% of the app is written in react-native. If one of the initial network calls, that fires after launch, fails. This somehow breaks something in every component using react-native. I think the app continues to run, but anything react-native is just blank.
  • 1
    Now i know where the idiotic trend comes from to not handle the sad path at all, or return
    200 {result:"",error:"Not found"}
  • 1
    @practiseSafeHex Is this one of the company's bugs, or is it in React native?
  • 2
    @Root The bug is the company's. I think multiple teams committed a lot of code to try get into the last release before holiday. I think these commits were stepping on each other modifying similar values and this wasn't tested together until it all went into the release branch at the last minute.
  • 0
Add Comment