Sure, I will try to to go that way then. At least, to find the root cause.
About my minimal example, there is no such hard code, the reproduction will include the same implementation for the routing, because the most basic app example doesn’t have that issue and you probably know it.
I had to implement both react-router and react-navigation to support web and native, they can be change at runtime for development convenience (since RN5 use JSX it was possible).
All the pages can be unplugged to the routing system, the error happen on the home page which does not have anything.
The related code that could cause the scrolling issue can be :
- in RN5 (since it’s the default navigation library activated for the apk)
- in my core where I init the routing (a ScrollView, an overflow, ListView within ListView…)
This is why the reproduction code would remain the same minus all the unecessary pages.
I believe the issue is in (2) but it is hard to catch since (1) is massively tested, but as you said it is pretty hard to catch especially that I do not know if the expo client app is a web app completely different than the native builded apk.
TaskManager, why is it necessary and how having it enabled on the apk will make the app identical to the expo distributed app, this is a mystery.
I still do not get how big are the differences and how I could rely on expo client , at what point, for both ios and android development.
Thanks a lot for your time.