HomeiOS Developmentios - The right way to make Expo stack traces extra readable?

ios – The right way to make Expo stack traces extra readable?


My Expo app is throwing an error on the iOS simulator, and I am struggling to establish the place it is occurring in my code. The stack hint seems to be like this:

ReferenceError: Property 'id' does not exist
    at nameless (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:195968:39)
    at tryCallTwo (/Customers/distiller/react-native/packages/react-native/sdks/hermes/build_iphonesimulator/lib/InternalBytecode/InternalBytecode.js:61:9)
    at doResolve (/Customers/distiller/react-native/packages/react-native/sdks/hermes/build_iphonesimulator/lib/InternalBytecode/InternalBytecode.js:216:25)
    at Promise (/Customers/distiller/react-native/packages/react-native/sdks/hermes/build_iphonesimulator/lib/InternalBytecode/InternalBytecode.js:82:14)
    at nameless (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:195967:33)
    at nameless (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:196666:36)
    at nameless (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:196479:19)
    at nextTick (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:196450:37)
    at tryCallOne (/Customers/distiller/react-native/packages/react-native/sdks/hermes/build_iphonesimulator/lib/InternalBytecode/InternalBytecode.js:53:16)
    at nameless (/Customers/distiller/react-native/packages/react-native/sdks/hermes/build_iphonesimulator/lib/InternalBytecode/InternalBytecode.js:139:27)
    at apply (native)
    at nameless (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:15376:26)
    at _callTimer (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:15255:17)
    at _callReactNativeMicrotasksPass (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:15300:17)
    at callReactNativeMicrotasks (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:15506:44)
    at __callReactNativeMicrotasks (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:2856:46)
    at nameless (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:2630:45)
    at __guard (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:2829:15)
    at flushedQueue (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:2629:21)
    at callFunctionReturnFlushedQueue (http://192.168.0.129:8081/index.bundle//&platform=ios&dev=true&sizzling=false&lazy=true:2614:33)

I feel I am looking for the improper issues, as a result of every part I learn says Metro “generates sourcemaps by default” and supplies methods to STOP doing that, clearly not my use case right here.

Wanting simply chopping out logical blocks of code and including console.logs in all places (which I have been doing and it simply appears like boiling the ocean), how can I isolate the supply of this error? Is there a strategy to make this stack hint extra readable?

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments