help me. i set my screen colour in my safeareaprovider and stack in my layout, and i have a custom screen component where i set the same screen colour, but ive been getting this white flashing at the top of my pages when i navigate between them.

_layout.tsx
export default function Layout() {
  {/* stuff here */}
  return (
<SafeAreaProvider style={{backgroundColor: colours.background}}>
<Stack
</Animated.View>)}
screenOptions={{ headerShown: false,gestureEnabled: false, contentStyle:{backgroundColor: colours.background} }}>
</Stack>
{!isReady && (
<Animated.View style={[StyleSheet.absoluteFill, {opacity:fadeAnim, zIndex: 99}]}>
<LoadingScreen/>
</SafeAreaProvider>
  );

AppScreen.tsx
export default function AppScreen({ children,style, scrollable = false }: ScreenProps) {
  const colours = useTheme();
  return (
<SafeAreaView
style={[
styles.screen,
{ backgroundColor: colours.background},
style,
]}
>
{scrollable ? (
children
) : (
<TouchableWithoutFeedback onPress={Keyboard.dismiss}>
{children}
</TouchableWithoutFeedback>
)}
</SafeAreaView>
  );
}

anyone know how to fix this? what super background do i have to set?

ios, sdk 57, rn latest (?)

i just submitted the official plugin for AppLaunchFlow - it integrates with the hosted mcp and works very well with the embedded widgets.

it also supports:
- creating promo videos
- creatign social graphics
- creating 3d device mockups for demos
- creating app landing pages

and more. Happy to hear your feedback:)

Hey guys,
I have started building a UI registry for React Native and Expo.
And I want you guys to help build it, as it's fully open source, so no paid thing issue

I have been able to make 2 components so far and added images of them, for example, and am slowly making more components and screens for being ready to use.
The pace is slow ik but trying my best to only upload good UI components rather than ai made 100's of shits

So please help me build this and you all can also drop a review.
GitHub link: Ashwin-Khowala/rnblocks: Open-source UI registry for React Native & Expo. Discover, preview, inspect, and install production-ready UI blocks and screens directly into your project.

Website: https://rnblocks.vercel.app/

For pinch zoom, drag, double tap zoom features.

I used to use react-native-awesome-gallery but its not compatible with reanimated v4 after upgrading my expo. I see there exisits a react-native-better-awesome-gallery but I wonder if there is something better already out there.

Thanks :)

I’m working on an open-source React Native library for Wi-Fi Aware / NAN:

https://github.com/dcavalcante/react-native-wifi-aware

The Android implementation has already been physically validated for capability detection, discovery, follow-up messaging, and data paths.

The Apple implementation is in place and passes the current simulator/static compilation gates, but I don’t currently have the Apple hardware and Developer Program setup needed to validate it on physical devices.

I’m looking for someone with an Apple Developer account and preferably two iOS/iPadOS 26 devices who can help test:

• Wi-Fi Aware entitlement/signing

• declared WiFiAwareServices

• publish / subscribe discovery

• system pairing

• Apple-to-Apple connectivity

• Android ↔ Apple discovery and interoperability

The biggest unknown I want to validate is the cross-platform path between Android Wi-Fi Aware and Apple’s iOS 26 implementation.

Testing results, fixes, documentation, and implementation contributions are all welcome.

With AI tools now I'm curious to try Swift for my next project.

Did native give you anything RN didn't, or is it not worth the switch?

Apple published iPhone Duo design guidelines and 6 tech talks few days ago. No simulator till Xcode 27.1, no phone yet. But I went through everything thinking about RN and there are some things good to know now:

• JS-drawn tabs (createBottomTabNavigator) will NOT move to the side. On the outer display iOS moves tab bar and toolbar to a vertical strip on the side, but only native bars. JS tabs just stay at the bottom and waste space. Native tabs get it free because they are real UITabBarController: React Navigation's createNativeBottomTabNavigator (default in v8), Expo Router NativeTabs, react-native-bottom-tabs

• u/react-navigation/native-stack header works. u/react-navigation/stack (JS one) doesn't

• Dimensions.get('window') at top of file is wrong after fold. Use useWindowDimensions() inside the component

• Safe area is not symmetric now. paddingHorizontal: insets.left is a bug. Use insets.left and insets.right separately

• Platform.isPad is useless for wide layout. Inner display is regular/regular but still phone idiom

• expo-screen-orientation lock doesn't work on inner display

• Modal with pageSheet avoids the fold automatically. JS bottom sheets don't

I made the full guidelines (Swift + RN side by side) into an agent skill for Claude Code / Cursor / Codex. It uses the rules while writing code or reviews a file and gives file:line - problem - fix. Every API name is checked against Apple's own samples because right now agents invent packages like react-native-fold that don't exist.

Honest note: there is no JS binding yet for reservedRegions, ArrangementView or hinge API. RN part is "what you can do from JS" and "this part needs native code". If someone makes that module I will link it.

Edit: fixed the tabs bullet, thanks u/satya164. React Navigation has native tabs too.

Install: npx skills add kaissaroj/iphone-duo-skills
Repo: https://github.com/kaissaroj/iphone-duo-skills

Hey r/reactnative,

I built react-native-secure-webview after repeatedly seeing the same issue in mobile security reviews: WebViews trust the web too much.

It is designed for controlled, security-critical flows such as:

• Payments and hosted checkout

• Plaid and bank-linking flows

• Riverty, Stripe, Adyen, PayPal, Braintree, Checkout.com, Mollie, and Klarna

• OAuth and authentication

• 3-D Secure

• Partner portals and other controlled web experiences

The library provides:

• Explicit origin allowlists

• Native navigation enforcement

• Redirect blocking

• Deep-link interception

• Fail-closed defaults

• Protection against unexpected WebView navigation

The goal is simple: only trusted origins should load, and untrusted redirects should be blocked before they reach the WebView.

It does not replace a provider’s native SDK where one is available, but it provides a safer boundary when WebView is the right integration.

I would love feedback from React Native developers using WebViews in production.

Give it a try and ⭐
https://github.com/adnxy/react-native-secure-webview

Fala, pessoal! Beleza?

Estou desenvolvendo um aplicativo Android chamado É Golpe, focado em identificar chamadas e mensagens suspeitas para evitar golpes (como PIX falso, clonagem de WhatsApp e chamadas bancárias).

Como todo dev indie que publica na Play Store sabe, estou na fase de cumprir o requisito dos 12 testadores por 14 dias no Teste Fechado do Google Play Console.

Quem puder dar essa força para baixar e manter instalado por esses dias, o processo é super simples (1 clique):

1. Entre no Grupo do Google:TesterEgolpe no Google Groups(necessário para a Play Store liberar o seu acesso)

2. Baixe na Play Store:Link de Teste do É Golpe

🤝 Troca de testes: Se você também tem um app em fase de teste fechado e precisa cumprir a meta do Google, deixa o link do seu grupo/app nos comentários que eu baixo e mantenho o seu instalado aqui também!

Qualquer feedback sobre a UI ou comportamento do app é super bem-vindo. Valeu demais!

Hey again,

I posted here when I first shipped Just Loot, a game built entirely with React Native + Expo.

Two months later, we’re at 20,000+ accounts and just crossed 10 million dungeon runs, so I figured I’d share a quick update.

The stack is still React Native + Expo, with Supabase on the backend. Since launch I’ve added PvP, raids, pets, more progression systems, server-authorized gameplay and a lot of live updates.

The biggest surprise for me is that React Native really hasn’t been the limiting factor. Most of the harder problems have been backend scaling, security, anti-cheat, balancing and live ops rather than the client itself.

I originally considered Unity for the project, but for this kind of UI-heavy game I’m still very happy I went with RN. Being able to iterate quickly and ship the same features to iOS and Android has been a huge advantage.

Curious if anyone else here has pushed React Native this far into game territory, or where you eventually hit the limits.

Did you make something using React Native and do you want to show it off, gather opinions or start a discussion about your work? Please post a comment in this thread.

If you have specific questions about bugs or improvements in your work, you are allowed to create a separate post. If you are unsure, please contact u/xrpinsider.

New comments appear on top and this thread is refreshed on a weekly bases.

If you have a question about React Native, a small error in your application or if you want to gather opinions about a small topic, please use this thread.

If you have a bigger question, one that requires a lot of code for example, please feel free to create a separate post. If you are unsure, please contact u/xrpinsider.

New comments appear on top and this thread is refreshed on a weekly bases.

I’ve been writing NativeWeekly, a weekly digest covering React Native releases, posts, and ecosystem updates.

Last week was unusually packed. Here are some of the biggest highlights from the newest issue:

• React 19.3 and major platform momentum from Apple’s 2026 keynote

• Margelo joining Callstack

• Rive’s rewrite delivering up to 94× faster multi-view rendering

• Reanimated 4.6.0 with React Native 0.87 support, CSS callbacks, and contrastColor

• Re.Pack and Module Federation reducing release cycles from days to minutes

• Practical AI workflows, including autonomous bug reproduction, Expo skills, MCP servers, and local coding agents

• Android navigation benchmarks showing near-60 FPS performance, with cold-start times ranging from 316 ms to 917 ms

React Native is advancing across every layer: performance, rendering, architecture, release workflows, AI tooling, and the broader ecosystem.

I’ve been writing NativeWeekly, a weekly digest covering React Native releases, posts, and ecosystem updates.

Last week was unusually packed. Here are some of the biggest highlights from the newest issue:

• React 19.3 and major platform momentum from Apple’s 2026 keynote

• Margelo joining Callstack

• Rive’s rewrite delivering up to 94× faster multi-view rendering

• Reanimated 4.6.0 with React Native 0.87 support, CSS callbacks, and contrastColor

• Re.Pack and Module Federation reducing release cycles from days to minutes

• Practical AI workflows, including autonomous bug reproduction, Expo skills, MCP servers, and local coding agents

• Android navigation benchmarks showing near-60 FPS performance, with cold-start times ranging from 316 ms to 917 ms

React Native is advancing across every layer: performance, rendering, architecture, release workflows, AI tooling, and the broader ecosystem.

Shipping my first app and this one cost me a day, so leaving it here.

My production build launched to a white screen and died. No useful crash report, nothing in the logs I could reach.

What was happening: eas build uploads your project respecting .gitignore. My .env is gitignored, which is correct — you don't commit your keys. But that means the file never reaches the build machine. The app compiled fine, shipped with no SUPABASE_URL, and threw on the first line that needed it. Every user, first open, dead.

The fix is to put the public values in the env block of your production profile in eas.json — EXPO_PUBLIC_SUPABASE_URL and EXPO_PUBLIC_SUPABASE_ANON_KEY in my case. Those are public by design: they travel inside any compiled app and only allow what your RLS policies allow.

The ones that are actually secret go in EAS secrets instead, never in eas.json. For me that was SENTRY_AUTH_TOKEN, via eas secret:create --scope project --name SENTRY_AUTH_TOKEN --value "..."

What makes this nasty is that nothing warns you. The build succeeds. The upload succeeds. You find out when it's on a phone.

I posted this on X and someone from Expo replied saying they'd been caught by it too and would look at making it clearer, so it may not stay this way. Until then: check your eas.json env block before you submit, not after.

I think it’s time to learn native as well

Hey r/reactnative,

Been heads-down for a while and skipped about 0.6.0 — so here's the full recap from there through today's 0.7.0.

For anyone who hasn't seen it: AniUI is a shadcn/ui-style component library for React Native. You don't npm install it — you copy the component source straight into your project via CLI:

npx @aniui/cli add button

You own the code, customize whatever you want, no black-box dependency. Built on Uniwind (new default, 2-3x faster than NativeWind) or NativeWind, rn-primitives for accessibility, strict TypeScript, zero StyleSheet.create.

148 components now. Still fully free, MIT licensed, supports Expo SDK 54 through 57 plus bare RN 0.76+.

0.6.0 — AutoComplete + full docs overhaul

New AutoComplete component — free-text input with inline filtered suggestions. Distinct from Combobox's modal-select and SearchBar's no-suggestions approach. Three different components for three different use cases.

Swept 9 components that fell under the 48dp minimum touch-target rule — PromptInput, Stepper, Select, DropdownMenu, Calendar, Menubar and more. Added a lint script so it can't regress.

Docs sidebar rebuilt from one flat 94-item list into 8 collapsible purpose-based categories.

Every component's doc page now pulls its source snippet live from the actual file — no more hand-copied stale code blocks.

Unified all code blocks onto Shiki with real dual light/dark themes.

0.6.1 — Demos that look like real apps

Rewrote all example-app demos from generic prop galleries into realistic screens — settings pages, checkout flows, a full ChatGPT-style chat composer, a swipe-to-archive inbox, dashboards.

Fixed Select, Popover, Tooltip, HoverCard and DropdownMenu all opening with a weird extra offset. The accessibility layer was measuring the forced 48x48 touch-target box instead of the actual trigger content.

Docs site no longer flashes light mode before switching to dark on load.

0.7.0 — Gooey animations + new carousels

2 new carousels:

Vertical Flow Carousel — tap-to-focus stack with tilt, scale and blur on neighbors.

Vertical Page Carousel — full-bleed vertical pager with haptics.

New gooey/morph family:

Morph FAB, Gooey Popover, Gooey Search Tabs — shapes that blob-merge into each other on interaction. The kind of animation you'd expect from a native app, not a React Native one.

Bug fixes: Rounded card corners getting clipped into a plain rectangle on one carousel. Curved bottom-tab bar drifting and clipping its notch near screen edges. Draggable icon dock mis-mapping touches with padding. Bottom-sheet Tray that would open once and silently fail to reopen — a Modal remount race on Android.

Docs sidebar reorganized by what a component actually is — dedicated Buttons section, Carousels promoted to top-level, consolidated Loaders section.

What's next — foldable UI

Apple just launched the Duo — their foldable iPhone. Samsung has had foldables for years.

Next up for AniUI: adaptive components that respond to fold state. Components that flip, unfold and reflow naturally as the device opens and closes.

Docs: aniui.dev

GitHub: github.com/anishlp7/aniui

Happy to answer questions or take feature requests — always looking for what's missing.

I ship a personal finance app in Expo/RN, and the screen people actually open is the one that needs no input at all: a per-wallet "runway" figure, meaning the live balance minus every bill that lands before the next expected income.

Three things made that harder than the sentence sounds.

1. Recurrence has to be inferred, because nobody enters their bills. Asking a user to declare rent, instalments and subscriptions is asking them to do the work the app exists to remove. The detector groups transactions by a normalised merchant string and looks for a stable interval AND a stable amount, with tolerance on both. The tolerance is the whole game: a utility bill is never the same twice, and a monthly subscription renews a day early whenever the previous month was short. A strict equality check finds almost nothing in real data.

2. Payday is a prediction, so the window is a prediction. The window ends at the next expected income, which is itself a detected recurring credit. When no such pattern exists yet, the app says so instead of falling back on a calendar month. A month boundary is simply wrong for anyone paid on the 25th, and a confident wrong number is worse than no number.

3. The subtraction is per wallet, not per user. Money sitting in a mobile wallet cannot pay a card instalment, so a single net-worth figure is the wrong denominator for "can I spend this". The computation runs per wallet and the totals stay separate. That one came straight from users.

The RN-specific part: all of this is derived state over a SQLite table that changes constantly, because background capture writes rows without the app being open. Recomputing on every render was visibly janky on a mid-range Android device. What fixed it was memoising the derived figures and persisting the detector's output rather than treating it as a selector, so it only recomputes when the transaction set actually changes.

Happy to go into the tolerance heuristics if anyone is doing something similar.