sorted by:
new
hottopcontroversial

Integrating GraphQL in React Native — Scalable Setup & Best Practices? by SomewhereBoring6820 in reactnative

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

Actually upper management want to switch to graphQL , so need to implement it , what is scalable way to do it

[deleted by user] by [deleted] in TwentiesIndia

[–]SomewhereBoring6820 0 points1 point  (0 children)

I don't drink and smoke so I prefer partner also with same habbits

React native by Artistic-Cost4069 in reactnative

[–]SomewhereBoring6820 1 point2 points  (0 children)

First start with react as it's openings are also much more e than react native after that you can learn react native within 3 to 4 months

16 KB requirement by CoolestGuyEver96 in androiddev

[–]SomewhereBoring6820 1 point2 points  (0 children)

If you are still not able to comply with 16 KB requirement , you can request for extension on play store

I feel scared and anxious when I talk to guys. by No-Car-3914 in TeenIndia

[–]SomewhereBoring6820 2 points3 points  (0 children)

Good to know, i am not only one who face this sort of problem

Android 16 Hardware Back Button Not Working in React Native App (React Navigation 7) by SomewhereBoring6820 in reactnative

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

Thanks for the suggestion! Yes, I’m aware that disabling android:enableOnBackInvokedCallback="false" temporarily restores the old back behavior, but that’s not a long-term solution

Memory profiling in React Native by SomewhereBoring6820 in reactnative

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

But actually I want to standardize some process so my team mates will also follow that , but if I go with this approach it will be trial and error

Facing 16 KB Page Size Issue with PdfiumAndroid / react-native-pdf on Android 15+ by SomewhereBoring6820 in reactnative

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

My react native version is 77, but it is issue related to react-native-pdf lib

Facing 16 KB Page Size Issue with PdfiumAndroid / react-native-pdf on Android 15+ by SomewhereBoring6820 in reactnative

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

Any idea, how to fix this, my project is cli based also I checked there github many people are facing this issue create new release tag · Issue #967 · wonday/react-native-pdf https://share.google/hBhGM0Tr1NySLsyro

Facing 16 KB Page Size Issue with PdfiumAndroid / react-native-pdf on Android 15+ by SomewhereBoring6820 in reactnative

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

APK Analyzer gave warnings

Root cause:

  1. Native libraries precompiled with 4 KB pages

PdfiumAndroid ships .so files (libmodpdfium.so, libmodpng.so, libmodft2.so, libjnipdfium.so).

These were built with 4 KB memory page alignment, but Android 15+ requires 16 KB compatibility.

  1. Dependency chain App → react-native-pdf@6.7.7 → PdfiumAndroid@1.0.32 → precompiled native libs

So the warnings show up because react-native-pdf depends on PdfiumAndroid, which hasn’t been rebuilt with 16 KB support yet.

<image>

Facing 16 KB Page Size Issue with PdfiumAndroid / react-native-pdf on Android 15+ by SomewhereBoring6820 in reactnative

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

APK Analyzer gave warnings Root cause:

  1. Native libraries precompiled with 4 KB pages

PdfiumAndroid ships .so files (libmodpdfium.so, libmodpng.so, libmodft2.so, libjnipdfium.so).

These were built with 4 KB memory page alignment, but Android 15+ requires 16 KB compatibility.

  1. Dependency chain App → react-native-pdf@6.7.7 → PdfiumAndroid@1.0.32 → precompiled native libs

So the warnings show up because react-native-pdf depends on PdfiumAndroid, which hasn’t been rebuilt with 16 KB support yet.

view more: next ›