Clojurians Log v2

I have a bug like that as well at the moment... want to share?

I’m dying to share! There is some info here https://clojurians.slack.com/archives/C0E1SN0NM/p1623144035106200 But at a higher level I’d summarize it as for reasons unknown to me some of the recent changes we’ve made to our mobile, React Native, app causes it to sometimes stop responding to taps on Android phones. I don’t know how to reproduce it. Sometimes it happens in development, but then the same thing that causes this also causes the REPL connection to die, making me blind. I can see in the system logs of the phone that it registers the taps, but nothing happens in the RN logs and neither my app logging. So, probably some infinite loop somewhere locking the JS thread. That loop is not in the changed code. It could be in some of our code, even if I doubt that. More likely it’s somewhere in the react native thins. We’re on a pretty old version. I am now seeing if I can make it happen on a branch where we have upgraded to latest stable react native. My hopes now are that it will happen on this branch as well, falsifying this hypotesis, because if it doesn’t happen I will not know if that’s just a coincidence. 😃 No idea how much sense this made. Your turn to share!

being on an old version of RN doesn't help here I suspect.

not sure about adb though.

does it happen on the simulator as well?

Being on an old version of RN does not help. Thing is that the app is super slow on Android in the branch where we have upgraded to RN 64, so there is probably a large amount of work still to do there before we can upgrade…

hmm that sucks.

any ideas why the slow downs on newer version of RN?

It doesn’t happen on iOS. Haven’t tried on the Android emulator, if that’s what you mean. I use a phone instead and Vysor to make Android development bearable.

No idea yet. I’ve mostly been using that branch with iOS so this slowness is still new to me. Thinking it might be a neighbouring cause to the thing happening for Android only with the old RN.

It happens in release builds as well, btw.

Anyway, mainly sharing for the sympathy. 😃 What about your bug?

I have an expo app and there is on crash on iOS only. and it is the OS killing the App.

but only with a build through TestFlight.

all other builds work fine (debug and optimized local builds)

So not with a relasebuild uploaded to the phone locally?

haven't tried that...

Maybe that’s the same as “optimized local builds”?

can you just download an IPA to the phone and install.

in expo you can say optimise the build(minify etc.)

I added bugsnag to my app... but it is not the app it self throwing an exception. it is the OS killing it. and I don't know why.

Does iOS monitor some metrics of the app maybe and killing it because of some threshold met, maybe? Is it easily reproducable?

Do you get a dump of your app-state together with the Bugsnag report? Something you can load into the dev version of the app and examine from there?

not sure about iOS logging things... I don't know enough about iOS for that... I have been googling a bit about this this morning.

I don't get a bugsnag report in this case... as the app gets killed by the OS I think.

Ah, yeah, maybe it is not given the chance to say goodbye properly.

If there is something that could tell you that it has happened when the app starts you can send the snag then?

I think it is at the end of a network operation... I could add some bugsnag log statements to that..

and I just found a page that explains where the logs are on iOS

Please share!

https://help.dayoneapp.com/en/articles/440759-getting-ios-crash-logs-for-day-one

hope that help

s

Ah, yes, I recall that from the days I hacked iOS apps using Objective C… 😃

👍

Hi @pez I got a bit further yesterday... It is a EXC_CRASH (SIGBART) crash. but no idea how to debug that at the moment....

Progress! I googled it quickly. Seems like it happens because of a bad call to the system from the app. Is that what you have found out about it as well?

yes... and I am trying to figure out how to symbolize the crash report... but as it is an Expo app that isn't straight forward it seems.

So that gets trickier because it’s an Expo app?

I think so... it is build on the Expo build farm.

and the xcode version I have is really old.

ok, it looks like I need to eject from Expo and use a so called bare workflow.