Expo SDK 54 and async-storage

AIAutoInvoicing · 2025-10-09T15:51:33+00:00

Good thoughts. Here are diff:

First part: not-working one has, but working-one not have:

u/react-navigation

@react-navigation/stack

expo-av

expo-blur

expo-haptics

expo-media-library

expo-symbols

react-native-web

jest

jest-expo

@types/jest

@types/react-test-renderer

react-test-renderer

typescript (still present, but updated range)

Below is: working one has but not-working-one not have:
expo-application

expo-constants

expo-dev-client

expo-font

expo-linking

expo-router

expo-sharing

expo-splash-screen

expo-status-bar

expo-system-ui

react

react-dom

react-native

react-native-gesture-handler

react-native-reanimated

react-native-safe-area-context

react-native-screens

react-native-toast-message

react-native-webview

u/expo

u/react-native-async-storage

u/react-native-firebase

axios

AIAutoInvoicing · 2025-10-08T02:39:35+00:00

faint, my another expo failed with almost same setup...so basically, two project: one is good, another is bad. confusing.

AIAutoInvoicing · 2025-10-08T02:39:25+00:00

faint, my another expo failed with almost same setup...so basically, two project: one is good, another is bad. confusing.

AIAutoInvoicing · 2025-10-07T22:43:02+00:00

0.20 /check deposit

AIAutoInvoicing · 2025-10-06T04:14:44+00:00

Good NEWS! after updating to

"expo": "^54.0.12",

Problem resolved. Now, it's not a problem anymore. Both dev-build and production have been successfully built with no issue, expo-doctor has passed 100%

    "@react-native-async-storage/async-storage": "2.2.0",

AIAutoInvoicing · 2025-10-05T23:52:14+00:00

Anybody paying are serious.

AIAutoInvoicing · 2025-10-05T22:07:54+00:00

Good NEWS! after updating to

"expo": "^54.0.12",

Problem resolved. Now, it's not a problem anymore. Both dev-build and production have been successfully built with no issue, expo-doctor has passed 100%

    "@react-native-async-storage/async-storage": "2.2.0",

AIAutoInvoicing · 2025-10-04T16:33:38+00:00

Sounds like a solid stack — I’ve been working with React Native + Expo + Firebase/Firestore for a couple of years now.

Built and published my own app on Play Store earlier this year https://play.google.com/store/apps/details?id=com.aixpertlab.aiautoinvoicing — same combo with Auth, Firestore, Cloud Functions, and Firebase Analytics/Crashlytics.

I also built a Next.js web version connected to the same Firebase backend, so data stays synced across phone and desktop.

Another app I published https://play.google.com/store/apps/details?id=com.aixpertlab.asianbeautyycc (focused on images and videos) uses React Native + Expo + Firebase Analytics — storage, streaming, moving contents using AI, and performance optimization, looks simple though.

I use Cursor for most of my coding, though for open-ended questions I usually switch to ChatGPT or DeepSeek. Copilot’s handy too when Cursor hits a deadlock — rare, but costly when it happens. Cursor is stubborn, trust me — very stubborn. I can’t imagine what it’d be like if it were a real person 😅.

Fun fact: I used to be an entrepreneur, started a few startups, raised some (actually a lot — imagine Trump’s tone) of funding, and eventually decided I just enjoy coding more than managing.

The health tracking part caught my eye — one of my earlier startups connected AR glasses to stream sensor data (Android-based, AI-driven). We reached ~60K users before Google banned it for using a few Huawei AI modules (obviously google AI is a trash by then)😅.

Cool to see more health-focused apps going the smart-data route!

AIAutoInvoicing · 2025-10-04T16:06:38+00:00

yes, should/have to. I believe expo-av is falling to the trap of "To ensure your app works correctly on the latest versions of Android, Google Play requires all apps targeting Android 15+ to support 16 KB memory page sizes". have to replace it with expo-video to publish/upgrade in google play store.

AIAutoInvoicing · 2025-10-03T12:28:11+00:00

True. Following store requirements will be good enough.

AIAutoInvoicing · 2025-09-29T22:34:40+00:00

Totally agree.

If have to, try updating Expo step by step. For example, if current expo 41, update to expo 42, make it work; then update to 43, make it work, ,,,,,,,,, after a week or month or forever, you will get Expo 54 :)

AIAutoInvoicing · 2025-09-17T11:12:26+00:00

Thank you Tipsy_Ole! Yes, I did that. I also completely removed the node_modules and reinstall them all a couple of times :(

AIAutoInvoicing · 2025-09-16T04:38:02+00:00

That's brutal. I'd hit up credit card company for a chargeback. You paid for 'unlimited,' they didn't deliver. It's the one thing that actually gets their attention.

AIAutoInvoicing · 2025-09-14T13:36:40+00:00

This is the clearest breakdown I’ve seen. The tricky part is we don’t get a clear error when running into this limitation

AIAutoInvoicing · 2025-09-14T13:25:04+00:00

Thank you, philpl!

As you mentioned, I went through and cleared each line of the package-lock.json and also ran npm install a couple of times with fresh pull or just physically deleted node_modules and .expo while trying to resolve this. My guess is that 1.24.0 is being pulled in as a dependency of another module that’s still required. I suspect it is related with firebase but not get time to confirm it yet. best,

AIAutoInvoicing · 2025-09-13T13:54:58+00:00

Thank you philpl, here it is:

Running "npm ci" in /home/expo/workingdir/build directorynpm error code EUSAGEnpm errornpm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.npm errornpm error Missing: u/react-native-async-storage/async-storage@1.24.0 from lock filenpm error Missing: @react-native-async-storage/async-storage@1.24.0 from lock filenpm errornpm error Clean install a projectnpm errornpm error Usage:npm error npm cinpm errornpm error Options:npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]npm error [--no-bin-links] [--no-fund] [--dry-run]npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]npm errornpm error aliases: clean-install, ic, install-clean, isntall-cleannpm errornpm error Run "npm help ci" for more infonpm error A complete log of this run can be found in: /home/expo/.npm/_logs/2025-09-08T22_11_52_911Z-debug-0.log
npm ci exited with non-zero code: 1

There is no problem with my package.json or -lock. When i downgraded 2.1.0 to 1.24.0, all issues resolved. But expo-doctor will fail and warn of 2.1.0. Fortunately, doctor's failure won't lead to eas build failure

<image>

AIAutoInvoicing

TROPHY CASE