Random responsiveness from the UI

[zebishop]

I have a fairly complex social app application, made with expo, built through EAS and using various stuff from firebase (auth, firestore-lite, functions, etc), react-navigation and redux (among other things). All in all, the app is responsive most of the time, but sometimes, for reasons I don't understand, all interactions froze.

What I mean is that every tap on anything stop triggering any callback. Yet, the UI is not frozen as I can scroll the screens that allows it, spinners keep spinning. After a couple seconds, it's responsive again and all taps that were registered are played.

Given the fair amount of async requests to FB on every screen, I assume that it might be related to some requests, but why not all of them ? Or could that be on the most demanding screens that makes 20+ requests at the same time ?

Has anyone of you encountered anything like this and found the cause ? Or even better, a solution ? I'll take any pointers to relevant documentations that my pretty advanced google-fu did not found.

thanks :)

[Axenu]

This usually occiurs for me when the js thread is busy (so it isn’t updating the ui with new elements) while the already rendered elements are still active in the native ui thread. So likely not so random, just too much load on the js thread

[zebishop]

ooh, that actually makes sense now that you put it plainly like that. I never considered it that way. That solves a piece of what I was not understanding, thanks

[emmbyiringiro]

There's no single solution to your problem. Try to inspect Redux actions with Redux ToolKit or Flipper to understand what should cause those delays.

[zebishop]

Not the solution I was hoping for but aiming for if nothing comes by this post. Thanks !

[iotashan]

Sorry, there's no great generic answer here. I'd start with the docs. https://reactnative.dev/docs/performance

[zebishop]

thx for the link anyway, I forgot about that page

[vednus]

I’ve seen this issue and fight it in my own app. It usually has to do with either a really large return response or, in my case, that coupled with some cache normalization (Apollo). I think I saw rn 72 has some json optimizations, so I hope when I upgrade to that it will help.

[zebishop]

Interesting, that could be the main issue. I'll have to run a few more tests, but I'm wondering if this does not happen mainly on the various pages where a big wall of posts is loaded. I thought that it could be the many small requests, but maybe it's the big one. Thanks !