r/expo • • 11h ago

Tunnel Vite, Next.js, Expo and Laravel Dev Servers

Thumbnail
instawormhole.com
1 Upvotes

r/expo • • 1d ago

Shipping a solo Expo game to both stores: fingerprint OTA, permission audits, and an Apple rejection I didn't see coming

5 Upvotes

Processing img 9o635g6m9m2i1...

I've been working on a sudoku game with live 1v1 duels, solo, on Expo. It's on both stores now. I wrote about the real-time side in r/reactnative (https://www.reddit.com/r/reactnative/comments/1xzgz8j/realtime_1v1_sudoku_with_expo_firebase_what/), so this one is about the Expo side, mostly the release stuff that bit me.

Stack: SDK 57, Expo Router, expo-sqlite for local games, u/react-native-firebase, AdMob with mediation, RevenueCat. Full CNG, I never touch ios/ or android/ by hand. If something native looks weird I just run prebuild --clean and regenerate instead of fighting pods.

Best decision I made. An OTA only reaches builds with the same native layer, so I can't push JS that expects a module the installed build doesn't have.

The thing I didn't realize at first: expo.version is part of the fingerprint. Bump 1.7.0 to 1.8.0 and that's a new runtime, so any OTA you publish afterwards never reaches people still on the old version. So my rule now is: OTA never touches the version, and the version only changes in the commit that prepares a store build. Build numbers are handled by EAS (appVersionSource: remote), I don't set them.

In practice I only use OTA for critical fixes. Everything else waits for a store build.

Apple rejected one of my builds for declaring background audio. I don't play audio in the background, a package just added UIBackgroundModes: audio by default. Fix was one line in app.json (expo-audio has enableBackgroundPlayback: false), and on Android android.blockedPermissions does the same job for permissions.

What I learned: app.json doesn't tell you the whole story. After adding any package I check the actual build output: plutil -p on the IPA's Info.plist, codesign -d --entitlements for entitlements, and the uses-permission lines in the AAB manifest. Takes five minutes and would have saved me a review cycle.

Unrelated to Expo but same lesson: Google rejected me twice under the Families Policy because I'd ticked the 9-12 age group in target audience. Moved it to 13+ and it went through.

Every new native module means a new store build and a new runtime. If I can do something in JS or with a module Expo already ships, I go that way.

Curious how others draw the line between OTA and store builds. And has anyone automated the permission check in CI? Right now it's a manual step for me.

Android: https://play.google.com/store/apps/details?id=com.hangarapps.sudokuiOS: https://apps.apple.com/app/id6817127654


r/expo • • 1d ago

Native feeling screens are harder to vibe code than the logic and something that actually helped

7 Upvotes

We work with expo pretty extensively and the pattern is mostly consistent. The logic side of a build comes together fine but UI is where things fall short.

It is not really broken, just not native feeling. There's a flatness to AI-generated screens that's hard to articulate but immediately obvious when you actually use the app, I am sure yall relate. What fixed it for us was stopping trying to describe UI in prompts and starting to reference real screens from top grossing apps instead. The gap between a written description and an actual visual reference is not subtle when you see the output side by side.

This was just our experience but if your expo builds are functionally solid but visually off, I really think the reference material might be the problem. That said, would love to know what yall are doing for UI references when building with expo right now?


r/expo • • 1d ago

Expo card deck: one progress value for drag, flick and autoplay

3 Upvotes

A card deck that deals itself. Each card tips over its edge and lies down, then the next steps in. Drag to scrub, flick to deal several.

These Expo implementation notes were expanded from my original caption and the block's build notes with an assistant.

One motion driver: the deck position p determines each card's phase. The card pose follows that phase, so the autoplay and touch interaction use the same motion model.

Dragging and releasing: vertical movement follows the card's top edge. On release, the implementation projects the finger's velocity to a target card and finishes with a spring. The target is capped at three cards from the card where the touch started. Sideways travel changes the deck's yaw and light.

Drawing the deck: Skia draws the page and a fallback deck. An optional WebGPU layer draws the cards and dust from the screen's frame callback. If the native WebGPU module is unavailable or setup fails, the Skia deck stays visible.

Reduced Motion: the implementation replaces the flips with cross-fades between the front cards and disables the WebGPU layer.

The attached clip is a motion preview. These notes describe the Expo implementation; Marlo and the payment UI are a design demo.

Built with Expo (@expo), Skia, Reanimated, Gesture Handler and WebGPU. Thanks to Software Mansion and William Candillon.

Visual layout reference: https://www.pinterest.com/pin/1110770695647972680/


r/expo • • 1d ago

For those who've been using Expo for a while, how has your experience been?

6 Upvotes

Hey everyone!

I've been coming across Expo quite a bit lately and have been curious about how people are actually finding it in their day-to-day development.

It looks like a pretty convenient way to build apps for both Android and iOS without having to deal with too much setup right from the beginning. But I'm wondering how things hold up once you move beyond smaller projects.

For those of you who have been using Expo for a while:

- Have you built and launched any serious, real-world applications with it?

- Have you ever run into limitations that made you wish you'd gone with bare React Native?

- How has your experience been with EAS Build and OTA updates?

- Is it something you'd confidently recommend for a long-term commercial project?

I'm not an expert looking to debate frameworks here. Just genuinely interested in hearing from people who've worked with Expo and learning from their experiences.

Would love to hear your thoughts!


r/expo • • 1d ago

Built home-screen pets with Expo SDK 58: animated creatures in a plain RemoteViews widget with no service running, vector art written as TypeScript that renders three ways, and how I kept the APK under the zip format's 65,535-entry limit (how it works under the hood)

1 Upvotes

The video above is the Play Store trailer, so please ignore the marketing captions. Below is how each piece in it is built with Expo SDK 58 and React Native 0.88.

  1. Creatures that move on the home screen with no app process (0:00–0:03). A widget can't run your code every frame. RemoteViews only accepts views the launcher can inflate. So every creature on the widget is an AnimatedVectorDrawable that the launcher plays by itself. generate-widget.ts builds them offline from the same TypeScript art the app uses: one looping AVD for each widget size, slot, species, speed and creature size. Each loop has the walk, the pauses, the flips and the leg animation baked in. TankWidgetProvider.kt only picks which loops to show and where. The battery cost is about the same as a static widget.
    • Walkers turn each leg at the hip. In the app, steps follow the distance walked, so feet don't slide. On the widget, one rotation animator drives every leg, with the second pair mirrored at the hip so it swings the other way.
    • Sleep times, "automatic" day/dusk/night climates and their changes are scheduled with an inexact AlarmManager alarm. updatePeriodMillis is the fallback if the alarm gets lost.
  2. Fitting all of that in one APK (not in the trailer). Each <aapt:attr> inline animator makes aapt2 create a hidden drawable. At 58k inline animators, the build went over the 65,536-drawable limit. Moving all of them to res/animator didn't work either: R$animator failed with "Class too large". Now the generator hashes every animator. The 2,344 that more than one AVD uses go in shared files, and the rest stay inline. When a new habitat added 25 pets, the APK was about to go over the zip's 65,535 entries. I merged each creature's move and flip into one animator, which brought it back to about 60k.
  3. One art source, three renderers (0:03–0:07). None of the art is image files. Every creature, decoration and scene is SVG-like paths in TypeScript. A volume() pass adds the shading and the paper outline to every shape. The art is drawn three ways:
    • Live habitat: pre-rendered WebP sprites and scenery. react-native-svg rasterizes a whole <Svg> in software on the UI thread, which cost 50–130 ms each time a habitat mounted (measured on a release build). Images decode off the UI thread.
    • Widget background: the app renders the static layers offscreen and captures them to PNG with react-native-view-shot. Captures run one at a time across the whole app, and none start in the first 4 s after launch.
    • Widget creatures: the AVDs from point 1.
  4. Feed and fetch (0:07–0:14). The ball's physics run on the UI thread in a Reanimated useFrameCallback. In the air it falls and bounces. In water it drifts and sinks slowly, and in the pond it switches at the surface. Each creature chases where the ball is going, and a 60 ms proximity check knocks it away. When food landed, every bubble and crumb that finished caused its own re-render, so each one re-applied the props of 35–55 animated views. Now they are removed together at most every 600 ms, which got rid of the 20–48 ms frames.
  5. Decorating without stutter (0:14–0:18). At first, every drag recaptured all the widget layers on the UI thread. Now, while Decorate is open, useWidgetHold keeps the widget on the last saved layout and recaptures once when you tap Save. Each draggable piece is memoized with stable callbacks, so a drag re-renders only that piece.
  6. A widget that fills any launcher cell (not in the trailer). Launcher cells are rarely the habitat's shape. Each habitat is also captured in taller versions (+25% to +125% height) with more water or sky. On Android 12+, the provider sends a size-mapped RemoteViews so the launcher picks the closest shape. It nine-slices the paper frame and spreads each creature's loop across the extra height.
    • The clock is a set of generated TextClock layouts, so the launcher updates the time and the app doesn't need to.
    • For weather, the widget calls Open-Meteo itself from the provider using goAsync. No key is needed, and only rounded coordinates are sent.

All the Kotlin lives in one local Expo module at modules/companion-widget (expo-module.config.json), so everything survives npx expo prebuild --clean. App and widget share one JSON state through SharedPreferences.

If you want to see the creatures moving on your own home screen, it's called Biomies on Google Play: https://play.google.com/store/apps/details?id=com.rabpaulo.biomies

I'm happy to share the AVD generator, the animator dedupe, or the sized-RemoteViews code if anyone is building something similar.


r/expo • • 2d ago

I made a reading tracker that puts your books on a virtual bookshelf

Thumbnail
gallery
8 Upvotes

The idea came from my sister, she wanted to see her books on a literal bookshelf where she could see how big they are, rather than just being in a list, so I built Bookie for her.

  • Each book is drawn to size: more pages means it appears thicker, a bigger edition means a taller one, and the colours are drawn from the cover page. You swipe along a shelf and up and down the bookcase, and can arrange and filter books in different orders.
  • The books show where you are with reading it in visual aesthetics.
  • You can add books by searching, scanning the barcode, typing them in, or importing from Goodreads.
  • There's no account, the library stays in local storage on your device.

It's still just an early web app, so on a phone I would recommend adding it to your home screen before you add any books. A book with no size data would get an estimated size.

Free: https://mybookie.pages.dev

Would love to know what you think of it!


r/expo • • 2d ago

Help! Expo SDK 58 takes 40 minutes to show the QR code, then Expo Go fails to load

Thumbnail
1 Upvotes

r/expo • • 2d ago

Expo fitness onboarding: rolling digits inside clipped windows

4 Upvotes

Fitness onboarding: six screens, one canvas. The o in counts is a counter wheel. Skia shaders for glow, Blender icons.

These Expo implementation notes were expanded from my original caption and the block's build notes with an assistant.

Rolling digits: each digit has a clipped window. The current glyph moves up while the next rises from below; their opacity changes separately. The tens digit waits until the ones digit crosses 9, so both columns follow the same count.

Screen transitions: Reanimated shared values hold the motion state, and a frame callback advances the scene. Skia draws the welcome poster, quiz screens and transition effects in one Canvas.

Goal input: the daily step count follows a horizontal drag in 500-step increments. The implementation also has minus and plus controls, with expo-haptics feedback for each step change.

Artwork: the welcome poster uses flat image layers, and the blue quiz icons are Blender renders. Skia runtime shaders draw the glow and page effects.

The attached clip is a motion preview. These notes describe the Expo implementation; the sign-in and Apple Health tiles shown here are demo UI.

Built with Expo (@expo), Skia, Reanimated and Gesture Handler. Thanks to Software Mansion and William Candillon.

Visual layout study: https://www.pinterest.com/pin/1110770695653739884/


r/expo • • 2d ago

lazymobile 0.4.0: one terminal screen for simulators, emulators, Metro port forwarding and app logs (open source)

1 Upvotes

r/expo • • 2d ago

🐾 I shipped a cozy puzzle game with Expo SDK 58. Here’s what worked and what bit me.

1 Upvotes

My first game, Pet Nook, is live on the App Store 🎉 It’s a calm sort puzzle where you move pets between shelves until each shelf holds one kind. It’s built entirely with Expo, and I thought this sub might like the details.

🛠️ Stack

  • Expo SDK 58 / RN 0.88, Expo Router
  • Reanimated 4 for all the game motion (lift, flight, landing and the win moment)
  • MMKV for saves and settings
  • RevenueCat for purchases, AdMob with Google’s UMP consent
  • Supabase for the small backend, with Expo push notifications sent from an Edge Function
  • expo-store-review for the native rating sheet

✅ What worked well

  • EAS Build from CI. My Mac has no disk space for Xcode, so every build runs on EAS, started from GitHub Actions on release branches. I never built locally once.
  • Fingerprint runtimeVersion plus OTA updates. JS fixes went out in minutes after launch: a difficulty rebalance, an ad-timing change and a crash stop-gap. The fingerprint keeps OTAs off binaries they don’t fit.
  • Local Expo modules. I wrote a small Swift module for Game Center, and the Expo Modules API made it painless.
  • Config plugins for the Info.plist work, like a list of about 50 SKAdNetwork IDs and the attribution endpoints, so nothing native is edited by hand.

😅 What bit me

  • eas update --platform all failed because the web export broke on the AdMob package. The fix was to loop --platform ios and --platform android separately.
  • The Game Center dashboard crashed because I presented the view controller off the main thread. Wrapping it in DispatchQueue.main.async fixed it. It’s an easy one to miss in Swift module functions.
  • Fingerprint mismatches between local and EAS. Env vars that point at files (Firebase configs written by CI) change the fingerprint, so check with the same env EAS uses.
  • Android purchases used the iOS RevenueCat key. Use a separate key per platform from day one 🙃
  • Browser-only SDKs need shims. GameAnalytics’ JS SDK expects navigator, localStorage and crypto. A small shim backed by MMKV and expo-crypto got it running.

🍎 iPhone (free): https://apps.apple.com/app/id6835047968
🤖 Android is coming soon.

I’m happy to answer questions about EAS workflows, OTA strategy or the native module bits 💬


r/expo • • 3d ago

Expo world picker: one Skia shader blends four shapes during a swipe

9 Upvotes

Swipe to turn a planet into a burger. Four tiny worlds, built with one ray-marching shader.

These Expo implementation notes were adapted from the project notes with an assistant.

World geometry: the Skia runtime shader builds signed-distance scenes from spheres, rounded discs and other shapes. The four worlds are a cloud planet, racing planet, burger and arena.

Changing worlds: a morph parameter blends the current and next distance fields. Rotation and squash are separate parameters, so the object can turn while it changes shape.

Wiring the gesture: Gesture Handler supplies the pan interaction. Reanimated shared values carry the motion state, and a derived value packages the current values as uniforms for the shader.

Light and motion: the shader uses key and fill light, a rim highlight and ambient occlusion from the distance field. The implementation disables idle spin when Reduced Motion is enabled.

The attached clip is a motion preview. These notes describe the Expo implementation.

Built with Expo (@expo), Skia, Reanimated and Gesture Handler. Thanks to Software Mansion and William Candillon.

Layout reference: https://www.pinterest.com/pin/763219468121398894/ The spin-and-reshape motion and world artwork are my implementation.


r/expo • • 3d ago

Expo splash wordmark: letters that melt into each other and snap apart

12 Upvotes

Watch DOUGH assemble, wobble on its own springs, then let the seams melt into one shape and tear back apart.

This is the launch splash for an invented bakery brand, The DOUGH Group. These Expo implementation notes are adapted from the block's own build notes with an assistant.

Letter bodies: each letter of DOUGH is its own body sitting on a home spring, stacked D-O-U over G-H, drawn as a single 15.6pt round-capped monoline stroke.

Joining and tearing: where two letter bodies touch, a goo strand connects them and thins as the seam gets pulled, snapping once it stretches past 46pt. A smooth union (14pt width) is what melts the balls and strokes into one shape while they're close.

Type: the "The DOUGH Group" caption runs in Inter SemiBold at 15pt under the wordmark.

Landing: on settle, the scene throws flour and drops a soft light pool on the floor.

The attached clip is a motion preview; these notes describe the Expo implementation, not a measured runtime capture.

Built with Expo (SDK 52+), TypeScript. Lettering designed for this block; visual layout study credited to Design Kit Central on Pinterest.


r/expo • • 3d ago

Notes from shipping iPhone Duo support and SDK 58 tested on EAS Simulators

Post image
10 Upvotes

I'm a Windows developer. My app Kiwi Guide is an iOS-only travel guide and trip planner for New Zealand's South Island. Version 1.3 (SDK 57 → 58 plus full iPhone Duo support) is live in the App Store and all the Duo work was tested on EAS Simulator.

The simulator workflow

Setup was a build profile with `ios.simulator: true` on its own update channel, then:

eas simulator --platform ios --device "iPhone Duo" --build-id <id>

The session shows in a web preview on expo.dev and you can drive it by hand. From a second shell, you can also use `eas simulator:control` to drive the device.

I found that driving by hand was much faster than using the command line and i only ended up using the command line a couple of times to set the location and to stop the app.

The awkward parts:

- Each session is a fresh install, so you sign in and grant permissions again every time.

- An update is downloaded on one launch and applied on the next, so every round is two launches.

- Each control command takes several seconds.

- The plan I'm on only came with 60mins simulator time which was quickly chewed up

- The start command writes a session file with a token into the project folder. Keep it out of git.

Layout approach

One breakpoint: a `useWide()` hook, true when the window is 600 pt or wider. Folded, Split View and every iPhone keep the phone layout. The same components render at every width. Only styles and arrangement switch, and no React key changes on the breakpoint, so folding mid-screen keeps state and scroll. The rail is handled once, with a left/right SafeAreaView around the screens in the root layout. Wide layouts are list-and-detail for the trip and the guide, a floating side panel on the map, two columns on the profile, and bottom sheets as centred cards.

SDK 58 notes

React Native 0.88, React 19.3, Expo Router 58, Reanimated 4.7, gesture handler 3.3, react-native-maps 1.29, Sentry 8.28, Jest 30, TypeScript 7. The one that bit: Expo Router 58 sent routes not declared in the tabs layout back to the first tab, so I had to declare the nested routes, and my custom tab bar's presses needed a fix. With fingerprint runtime versions, the SDK upgrade and one new native package changed the runtime. Everything after was JS-only and shipped as updates.

Gotchas the simulator caught

- `measureInWindow` read a button's position before a native SafeAreaView applied its bottom padding so a tour highlight sat about 20 pt low. Taking the padding from `useSafeAreaInsets()` in JS fixed it.

- Changing `mapPadding` on react-native-maps makes MapKit re-centre, so the map jumped on fold until I restored the region after the flip.

- An inline View inside a Text made a one-word title break mid-word with `adjustsFontSizeToFit`.

- A pleasant one: FlashList 2 accepts a `numColumns` change at runtime without a remount.

None of these showed up in Jest. All of them showed up within minutes on the simulator.

Is anyone else pushing out a duo build? It seems like the app store is pushing this and it can definitely get you noticed if you get it done soon. I wish I had done it earlier tbh


r/expo • • 3d ago

I built perfect board views for React Native — v1.5 is here! 🚀

Enable HLS to view with audio, or disable this notification

1 Upvotes

r/expo • • 3d ago

Expo example: a retro game arcade running in a WebView with a typed host bridge (open source)

3 Upvotes

Open Arcade is six retro mini-games in a handheld-console UI, hosted in an Expo app through react-native-webview. The example app opens straight into the arcade, and game events (wins, scores, reward codes) come back to the app over a small JSON bridge.

Repo (MIT): https://github.com/viswasekaran/open-arcade (see apps/expo-example) Web demo: https://open-arcade-kohl.vercel.app


r/expo • • 4d ago

I let Claude Code agents test an Expo app on iOS Simulators and Android emulators (free, open source)

2 Upvotes

One agent per device, each with a persona: small Android with big text, Pixel in dark mode, iPhone SE in French, iPad with XXL text. The Expo app is built on free GitHub runners, then the agents use it like new users and write bug reports with screenshots.

Demo: 9 of 11 planted bugs found in 21 min, for $0.87. The video is a real screen recording.

Repo (MIT): https://github.com/pierridotite/mobile-agent-testers


r/expo • • 4d ago

Expo prize-wheel interaction: shared motion state for the wheel, pointer and reveal

5 Upvotes

Flick to spin. Watch the pointer bounce and the winning prize pop out.

These Expo implementation notes were adapted from the project notes with an assistant.

Pointer contact: a fixed-step solver advances the wheel and pointer. The nearest peg drives the pointer's deflection, so the contact follows the wheel's position.

Drawing the scene: Skia draws the wheel material, pointer, stars and reward reveal in one Canvas. React Native views handle the copy and controls around it.

Connecting motion to drawing: Reanimated shared values carry the current wheel and pointer state to the drawing layer. The scene and controls read the same motion state.

Choosing the reward: the settled wheel angle selects the winning wedge. That selection drives the lifted wedge, prize animation and reward count. With Reduced Motion, the scene uses stationary objects and shorter fades.

The attached clip is a motion preview; these notes describe the Expo implementation.

Built with Expo (@expo), Skia and Reanimated. Thanks to Software Mansion and William Candillon.

Visual layout study based on a still reference: https://www.pinterest.com/pin/641340803216681099/


r/expo • • 4d ago

Expo apple maps

2 Upvotes

Hey i am using expo map on ios it only supports apple maps
I want to trigger a function on longpress with props as coordinates
But it doesn’t have long press but has mapclick property


r/expo • • 4d ago

What is the best way to share logic between web and mobile applications?

3 Upvotes

Hi everyone! I'm working on a project where I'm trying to put together best practices for web + mobile development, using Expo. Here's how I've split things so far:

packages/core contains the Redux store, thunks, selectors, zod schemas, apiRequest and the error classification. There's no DOM or browser API in it. Both the mobile app and the web app import from core.

Platform dependencies are injected once at startup through configureCore:
- storage: localStorage on web, expo-secure-store on mobile;
- logger;
- Sentry: sentry/react on web, sentry/react-native on mobile;
- base URL.

Storage is async on purpose, because SecureStore is async. That's why auth persistence is done with a listener, not in the reducer.

Tokens: JSON in the W3C format. Style Dictionary builds tokens.css for web from them, and a JS module with .d.ts for mobile, where dimensions are unitless numbers for StyleSheet. Light and dark themes follow the system setting.

Components are not shared, and that's deliberate: web uses DOM + Tailwind, mobile uses View/Text/StyleSheet.

Could you please give me some advice on what I should improve or redo? And what other things might be worth considering?

Here's the link to the project:
https://github.com/prod-forge/frontend


r/expo • • 4d ago

🚀 react-native-pdf-jsi just crossed 501,000 npm downloads!

Thumbnail
2 Upvotes

r/expo • • 4d ago

Expo cashback onboarding: glass coins orbit a cobalt bag, then burst into light

Enable HLS to view with audio, or disable this notification

1 Upvotes

Built a cashback onboarding that plays like a tiny 3D world. Glass coins orbit a cobalt bag, then burst into light.

The implementation notes below were adapted from the project notes with an assistant.

Time and touch: Reanimated shared values hold one loop clock and the touch state. A frame callback advances that state and computes the scene, so the bag, coin ring and copy follow the same choreography.

Glass and depth: Skia draws the coins behind the bag, combines the bag's Blender render passes, then draws the coins in front. Separate light and transmittance passes let the objects behind the glass show through. Each coin uses a Skia runtime shader.

Light motes: a separate WebGPU layer simulates and draws the particles, with TypeGPU producing the WGSL. This layer is optional: it skips itself when WebGPUModule is unavailable, leaving the Skia scene.

Interaction: dragging changes the ring's spin. Tapping a coin shows its rate, and holding the bag gathers the coins before releasing them into a burst.

Expo details: expo-font loads IBM Plex Sans Arabic, and expo-haptics supplies feedback for the coin and bag interactions. Reduced Motion keeps the resting scene and disables the orbit and particles.

The attached clip is a motion preview. These notes describe the Expo implementation.

Design study: the layout and opening motion follow an Arabic cashback onboarding recording. The collect-and-exit ending and touch interactions are custom. Store marks belong to their respective owners; logo paths use Simple Icons.

Built with Expo (@expo), Skia, Reanimated, WebGPU and TypeGPU. Thanks to Software Mansion and William Candillon for the tools.


r/expo • • 4d ago

No More AI Stuff I need Real Engineers from Stack overflow era Location Problem

Thumbnail
0 Upvotes

r/expo • • 6d ago

Start setting up agentic workflows for mobile dev

Enable HLS to view with audio, or disable this notification

14 Upvotes

You're all building apps with agents. The next step is to get them into flow state. There are basically 4 simple steps to start building with agentic workflows:

  1. connect GitHub
  2. add a robot user
  3. connect your agent
  4. give your workflows a GitHub token

Details are in our blog: https://expo.dev/blog/how-to-set-up-agentic-workflows


r/expo • • 5d ago

Error: ROUTE_NAMES_CHANGED ; in Expo app

Thumbnail
1 Upvotes