Wei102193
Wei102193
I posted a similar issue on [This](https://github.com/GeekyAnts/NativeBase/issues/4681). I believe the more React Native components you use the slower your app will be. Native Base is great. But this is a...
if you are using package "native-base", remove that from your project completely before it is too late.
same issue godamn it drives me nuts
> @Wei102193 I suggested above to add a `loading.js` file for the affected route. Did you observe this helping or not? seems to work, why? also don't really want that...
> I don't know precisely why, but I'm guessing it's some conflict with the client-side router cache trying to display content that has been purged and somehow running into a...
the latest release has fixed this issue On Sun, Mar 3, 2024 at 7:29 AM Darius ***@***.***> wrote: > Really happy I found this. > > *Workaround*: Use a loading.js...
upgraded to 14.0.2 and added ``` module.exports = { experimental: { serverActions: { allowedOrigins: ["localhost:3000", "demo.your-actual-domain.com], }, }, } ``` solved my problem
Native base is not longer maintained. And it has bad performance. DROP IT. [https://github.com/GeekyAnts/NativeBase/issues/4302#issuecomment-1650492491](https://github.com/GeekyAnts/NativeBase/issues/4302#issuecomment-1650492491)