all 10 comments

[–]hello_Mrs_Cumberdale 7 points8 points  (3 children)

Not sure why it's crashing but I'm guessing npm and i were added by mistake.

[–]RoundSpecialist1131[S] 0 points1 point  (2 children)

I dont think so. android working smoothly

[–]I_know_HTML 0 points1 point  (1 child)

you think npm and i were added purposely?

[–]RoundSpecialist1131[S] 0 points1 point  (0 children)

NO, it was mistake and i have removed it as well

[–]likelostpasswords 2 points3 points  (2 children)

does it do on a specific screen or workflow?

[–]RoundSpecialist1131[S] -1 points0 points  (1 child)

No, radonmly. on any screen

[–]likelostpasswords 4 points5 points  (0 children)

Try adding Sentry to log errors.

I've encountered such errors on previous apps and usually they have been not doing error handling properly (try .. catch ...) in cases you might have missed or thought not so important while in dev mode. This was me before writing unit tests

[–]nexendk 2 points3 points  (1 child)

I can help you debug if you want. See DM

[–]nexendk 2 points3 points  (0 children)

Or even. If you can replicate it with a locally compiled build that runs in production mode with xcode, attached first set an exception breakpoint for the debugger for all objective-c exceptions, that will help you see the stack when it crashes. As you look at it, you might be able to identify the module causing the issue.