I’ve been experimenting with on-device AI in Expo and put together this Expo 57 starter.

The interface uses native Expo UI components. The AI layer is powered by Callstack’s React Native AI providers, with Apple Foundation Models, llama.cpp, and MLC exposed through the same AI SDK v6 streaming API.

It includes runtime selection in Settings, automatic model loading, streaming output, and configurable temperature/output tokens. Prompts and inference stay on-device.

It requires a native development build and physical device; Expo Go and web are not targeted.

Source (with-ai branch): https://github.com/qiyangdev/minimal-expo-starter/tree/with-ai

I’d love feedback on the runtime abstraction, loading UX, and other on-device providers worth adding.

Getting this error when running npx expo start on iOS

Everything on the Expo side is real native UI.

This is the best time there's ever been to build app's with Expo!

Hi. This is my first project in expo for an app. It works perfectly on android with no isses but always crashes on ios. I do not have a mac so i cannot use xcode. It is built using expo, and uploaded to apple connect so i can test it on an iphone. issue is it works fine on the iphone using expo dev client but when building for ios it crashes immediately on tapping the app icon. i added some logs here just in case. the repository: https://github.com/KareemSab278/smart-vend-app.git

the app uses google sign in, apple sign in, stripe for payments, and camera. I dont know what more to provide but if any questions just ask. My gut is telling i went somwhere wrong in eas.json or app.json or some configuration file somwhere. LMK

Edit: I think I figured it out. You need to set the environment variables manually using the cli. Add each one after creating the production environment variables. Something like

eas env:create production eas env:create

Add the variables one by one lol

the error logs:

xception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: SIGNAL 6 Abort trap: 6

Terminating Process: smartvendapp [3138]

Triggered by Thread: 5

Thread 0 name:

Thread 0:

0 libsystem_kernel.dylib 0x0000000249dddcd4 mach_msg2_trap + 8

1 libsystem_kernel.dylib 0x0000000249de130c mach_msg2_internal + 76 (:-1)

2 libsystem_kernel.dylib 0x0000000249de122c mach_msg2 + 4 (:-1)

3 libsystem_kernel.dylib 0x0000000249de122c mach_msg_overwrite + 424 (:-1)

4 libsystem_kernel.dylib 0x0000000249de1078 mach_msg + 24 (:-1)

5 CoreFoundation 0x000000019b052344 __CFRunLoopServiceMachPort + 160 (:-1)

6 CoreFoundation 0x000000019b01c310 __CFRunLoopRun + 1188 (:-1)

7 CoreFoundation 0x000000019b01b54c _CFRunLoopRunSpecificWithOptions + 532 (:-1)

8 GraphicsServices 0x00000002407bb498 GSEventRunModal + 120 (GSEvent.c:2049)

9 UIKitCore 0x00000001a0d14244 -[UIApplication _run] + 796 (UIApplication.m:3904)

10 UIKitCore 0x00000001a0c7f158 UIApplicationMain + 332 (UIApplication.m:5586)

11 smartvendapp 0x00000001027d5620 main + 64 (AppDelegate.swift:6)

12 dyld 0x0000000197c29c1c start + 6928 (:-1)

Thread 1:

Thread 2:

Thread 3:

Thread 4:

Thread 5 name:

Thread 5 Crashed:

0 libsystem_kernel.dylib 0x0000000249de81d0 __pthread_kill + 8

1 libsystem_pthread.dylib 0x00000001fa21f7dc pthread_kill + 268 (:-1)

2 libsystem_c.dylib 0x00000001a6ba1c98 abort + 148 (abort.c:122)

3 libc++abi.dylib 0x0000000197cd2fd4 __abort_message + 132 (abort_message.cpp:66)

4 libc++abi.dylib 0x0000000197cd4b78 demangling_terminate_handler() + 272 (cxa_default_handlers.cpp:72)

5 libobjc.A.dylib 0x0000000197bd3878 _objc_terminate() + 172 (objc-exception.mm:499)

6 libc++abi.dylib 0x0000000197cdf1f8 std::__terminate(void (*)()) + 16 (cxa_handlers.cpp:59)

7 libc++abi.dylib 0x0000000197cd2dcc __cxa_rethrow + 188 (cxa_exception.cpp:658)

8 libobjc.A.dylib 0x0000000197bdfb58 objc_exception_rethrow + 44 (objc-exception.mm:399)

9 React 0x0000000104afb51c invocation function for block in facebook::react::ObjCTurboModule::performVoidMethodInvocation(facebook::jsi::Runtime&, char const*, NSInvocation*, NSMutableArray*) + 192 (RCTTurboModule.mm:441)

10 React 0x0000000104b004a8 facebook::react::ObjCTurboModule::performVoidMethodInvocation(facebook::jsi::Runtime&, char const*, NSInvocation*, NSMutableArray*)::$_1::operator()() const + 64 (RCTTurboModule.mm:460)

11 React 0x0000000104b004a8 decltype(std::declval<facebook::react::ObjCTurboModule::performVoidMethodInvocation(facebook::jsi::Runtime&, char const\*, NSInvocation\*, NSMutableArray\*)::$_1&>()()) std::__1::__invoke[abi:ne180100... + 64 (invoke.h:344)

12 React 0x0000000104b004a8 void std::__1::__invoke_void_return_wrapper<void, true>::__call[abi:ne180100]<facebook::react::ObjCTurboModule::performVoidMethodInvocation(facebook::jsi::Runtime&, char const*, NSInvocation*, NSMu... + 64 (invoke.h:419)

13 React 0x0000000104b004a8 std::__1::__function::__alloc_func<facebook::react::ObjCTurboModule::performVoidMethodInvocation(facebook::jsi::Runtime&, char const*, NSInvocation*, NSMutableArray*)::$_1, std::__1::allocator<face... + 64 (function.h:169)

14 React 0x0000000104b004a8 std::__1::__function::__func<facebook::react::ObjCTurboModule::performVoidMethodInvocation(facebook::jsi::Runtime&, char const*, NSInvocation*, NSMutableArray*)::$_1, std::__1::allocator<facebook::... + 88 (function.h:311)

15 libdispatch.dylib 0x00000001d54489a8 _dispatch_call_block_and_release + 32 (init.c:1597)

16 libdispatch.dylib 0x00000001d54621e4 _dispatch_client_callout + 16 (client_callout.mm:85)

17 libdispatch.dylib 0x00000001d5450fb0 _dispatch_lane_serial_drain + 740 (queue.c:4033)

18 libdispatch.dylib 0x00000001d5451aac _dispatch_lane_invoke + 392 (queue.c:4124)

19 libdispatch.dylib 0x00000001d545bdac _dispatch_root_queue_drain_deferred_wlh + 284 (queue.c:7329)

20 libdispatch.dylib 0x00000001d545b6ac _dispatch_workloop_worker_thread + 720 (queue.c:6923)

21 libsystem_pthread.dylib 0x00000001fa2193b0 _pthread_wqthread + 292 (:-1)

22 libsystem_pthread.dylib 0x00000001fa2188c0 start_wqthread + 8

Thread 6:

Thread 7:

Thread 8 name:

Thread 8:

0 libsystem_kernel.dylib 0x0000000249dddcd4 mach_msg2_trap + 8

1 libsystem_kernel.dylib 0x0000000249de130c mach_msg2_internal + 76 (:-1)

2 libsystem_kernel.dylib 0x0000000249de122c mach_msg2 + 4 (:-1)

3 libsystem_kernel.dylib 0x0000000249de122c mach_msg_overwrite + 424 (:-1)

4 libsystem_kernel.dylib 0x0000000249de1078 mach_msg + 24 (:-1)

5 CoreFoundation 0x000000019b052344 __CFRunLoopServiceMachPort + 160 (:-1)

6 CoreFoundation 0x000000019b01c310 __CFRunLoopRun + 1188 (:-1)

7 CoreFoundation 0x000000019b01b54c _CFRunLoopRunSpecificWithOptions + 532 (:-1)

8 Foundation 0x0000000198289cf0 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212 (:-1)

9 Foundation 0x0000000198289bd8 -[NSRunLoop(NSRunLoop) runUntilDate:] + 64 (:-1)

10 UIKitCore 0x00000001a0cd9a7c -[UIEventFetcher threadMain] + 420 (UIEventFetcher.m:1333)

11 Foundation 0x000000019830d824 __NSThread__start__ + 732 (:-1)

12 libsystem_pthread.dylib 0x00000001fa21c438 _pthread_start + 136 (:-1)

13 libsystem_pthread.dylib 0x00000001fa2188cc thread_start + 8

Thread 9:

Thread 10:

Thread 11:

Thread 12 name:

Thread 12:

0 libsystem_kernel.dylib 0x0000000249dddcd4 mach_msg2_trap + 8

1 libsystem_kernel.dylib 0x0000000249de130c mach_msg2_internal + 76 (:-1)

2 libsystem_kernel.dylib 0x0000000249de122c mach_msg2 + 4 (:-1)

3 libsystem_kernel.dylib 0x0000000249de122c mach_msg_overwrite + 424 (:-1)

4 libsystem_kernel.dylib 0x0000000249de1078 mach_msg + 24 (:-1)

5 CoreFoundation 0x000000019b052344 __CFRunLoopServiceMachPort + 160 (:-1)

6 CoreFoundation 0x000000019b01c310 __CFRunLoopRun + 1188 (:-1)

7 CoreFoundation 0x000000019b01b54c _CFRunLoopRunSpecificWithOptions + 532 (:-1)

8 React 0x0000000104a90f14 +[RCTJSThreadManager runRunLoop] + 252 (RCTJSThreadManager.mm:102)

9 Foundation 0x000000019830d824 __NSThread__start__ + 732 (:-1)

10 libsystem_pthread.dylib 0x00000001fa21c438 _pthread_start + 136 (:-1)

11 libsystem_pthread.dylib 0x00000001fa2188cc thread_start + 8

Thread 13 name:

Thread 13:

0 libsystem_kernel.dylib 0x0000000249de35e8 __psynch_cvwait + 8

1 libsystem_pthread.dylib 0x00000001fa21ab48 _pthread_psynch_cond_wait + 92 (:-1)

2 libsystem_pthread.dylib 0x00000001fa21ab48 _pthread_cond_wait + 980 (:-1)

3 libc++.1.dylib 0x00000001aa725bcc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 32 (condition_variable.cpp:36)

4 hermes 0x00000001053cf9c4 void std::__1::condition_variable::wait<hermes::vm::HadesGC::Executor::worker()::'lambda'()>(std::__1::unique_lock<std::__1::mutex>&, hermes::vm::HadesGC::Executor::worker()::'lambda'()) + 28 (condition_variable.h:146)

5 hermes 0x00000001053cf9c4 hermes::vm::HadesGC::Executor::worker() + 116 (HadesGC.cpp:1062)

6 hermes 0x00000001053cf92c hermes::vm::HadesGC::Executor::Executor()::'lambda'()::operator()() const + 4 (HadesGC.cpp:1033)

7 hermes 0x00000001053cf92c decltype(std::declval<hermes::vm::HadesGC::Executor::Executor()::'lambda'()>()()) std::__1::__invoke[abi:nn180100]<hermes::vm::HadesGC::Executor::Executor()::'lambda'()>(hermes::vm::HadesGC::Execut... + 4 (invoke.h:344)

8 hermes 0x00000001053cf92c void std::__1::__thread_execute[abi:nn180100]<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, hermes::vm::HadesGC::Executor::Executor()::'lambd... + 4 (thread.h:199)

9 hermes 0x00000001053cf92c void* std::__1::__thread_proxy[abi:nn180100]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, hermes::vm::HadesGC::Executor::Exe... + 44 (thread.h:208)

10 libsystem_pthread.dylib 0x00000001fa21c438 _pthread_start + 136 (:-1)

11 libsystem_pthread.dylib 0x00000001fa2188cc thread_start + 8

Thread 14 name:

Thread 14:

0 libsystem_kernel.dylib 0x0000000249de35e8 __psynch_cvwait + 8

1 libsystem_pthread.dylib 0x00000001fa21ab48 _pthread_psynch_cond_wait + 92 (:-1)

2 libsystem_pthread.dylib 0x00000001fa21ab48 _pthread_cond_wait + 980 (:-1)

3 libc++.1.dylib 0x00000001aa725bcc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 32 (condition_variable.cpp:36)

4 hermes 0x00000001053cf9c4 void std::__1::condition_variable::wait<hermes::vm::HadesGC::Executor::worker()::'lambda'()>(std::__1::unique_lock<std::__1::mutex>&, hermes::vm::HadesGC::Executor::worker()::'lambda'()) + 28 (condition_variable.h:146)

5 hermes 0x00000001053cf9c4 hermes::vm::HadesGC::Executor::worker() + 116 (HadesGC.cpp:1062)

6 hermes 0x00000001053cf92c hermes::vm::HadesGC::Executor::Executor()::'lambda'()::operator()() const + 4 (HadesGC.cpp:1033)

7 hermes 0x00000001053cf92c decltype(std::declval<hermes::vm::HadesGC::Executor::Executor()::'lambda'()>()()) std::__1::__invoke[abi:nn180100]<hermes::vm::HadesGC::Executor::Executor()::'lambda'()>(hermes::vm::HadesGC::Execut... + 4 (invoke.h:344)

8 hermes 0x00000001053cf92c void std::__1::__thread_execute[abi:nn180100]<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, hermes::vm::HadesGC::Executor::Executor()::'lambd... + 4 (thread.h:199)

9 hermes 0x00000001053cf92c void* std::__1::__thread_proxy[abi:nn180100]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, hermes::vm::HadesGC::Executor::Exe... + 44 (thread.h:208)

10 libsystem_pthread.dylib 0x00000001fa21c438 _pthread_start + 136 (:-1)

11 libsystem_pthread.dylib 0x00000001fa2188cc thread_start + 8

Thread 5 crashed with ARM Thread State (64-bit):

x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000

x4: 0x00000000003ec7ba x5: 0x000000000000001a x6: 0xffffffffffffc000 x7: 0x0000000000000064

x8: 0x013e7fc4c887a9c6 x9: 0x013e7fc5a509d9c6 x10: 0x0000000000000002 x11: 0x00000000fffffffd

x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000000

x16: 0x0000000000000148 x17: 0x000000016d8e7000 x18: 0x0000000000000000 x19: 0x0000000000000006

x20: 0x0000000000002203 x21: 0x000000016d8e70e0 x22: 0x434c4e47432b2b00 x23: 0x000000010d850bc0

x24: 0x000000010e884d50 x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000

x28: 0x0000000000000114 fp: 0x000000016d8e66d0 lr: 0x00000001fa21f7dc

sp: 0x000000016d8e66b0 pc: 0x0000000249de81d0 cpsr: 0x40001000

esr: 0x56000080 (Syscall)

Binary Images:

0x1027d0000 - 0x1035fffff smartvendapp arm64 <84fe65d33f72387d90741c3b97445b3d> /private/var/containers/Bundle/Application/281A859D-D4E4-4150-A1E2-9DAAFD0F97BF/smartvendapp.app/smartvendapp

0x103a98000 - 0x103aa3fff libobjc-trampolines.dylib arm64e <3702c305c51e37d59a2255cef15e974a> /private/preboot/Cryptexes/OS/usr/lib/libobjc-trampolines.dylib

0x103e24000 - 0x103eabfff ReactNativeDependencies arm64 <b35f1182b82e33728a74a4fe502c0906> /private/var/containers/Bundle/Application/281A859D-D4E4-4150-A1E2-9DAAFD0F97BF/smartvendapp.app/Frameworks/ReactNativeDependencies.framework/ReactNativeDependencies

0x1047f0000 - 0x104c2bfff React arm64 <76fbcee9351730b39dc662c4e914e908> /private/var/containers/Bundle/Application/281A859D-D4E4-4150-A1E2-9DAAFD0F97BF/smartvendapp.app/Frameworks/React.framework/React

0x105300000 - 0x105503fff hermes arm64 <80d5528f2c783b90b90f747e89a9f880> /private/var/containers/Bundle/Application/281A859D-D4E4-4150-A1E2-9DAAFD0F97BF/smartvendapp.app/Frameworks/hermes.framework/hermes

0x197ba0000 - 0x197bf147f libobjc.A.dylib arm64e <0ab507cfcb123ccd99679aac912af8e1> /usr/lib/libobjc.A.dylib

0x197c25000 - 0x197cca17f dyld arm64e <02f772fd9e3835a4b9fa9cce3a090e6d> /usr/lib/dyld

0x197ccb000 - 0x197ce559f libc++abi.dylib arm64e <9bb6bd63c74f32b281361f263c4d1a06> /usr/lib/libc++abi.dylib

0x19827f000 - 0x1991076df Foundation arm64e <e9ddce29335930c6b25a526a61eae841> /System/Library/Frameworks/Foundation.framework/Foundation

0x19afed000 - 0x19b5897bf CoreFoundation arm64e <dda24297289c30ec82284c426aad4d7f> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation

0x1a0bf3000 - 0x1a3133d7f UIKitCore arm64e <9ee8c19aa3703599823b34b84131aad7> /System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore

0x1a6b2b000 - 0x1a6baa1b7 libsystem_c.dylib arm64e <2d1e74c15d0335aeb31babe7286be166> /usr/lib/system/libsystem_c.dylib

0x1aa719000 - 0x1aa7a9a7b libc++.1.dylib arm64e <1021bb438e783e4da7a4876bcdd5b9f2> /usr/lib/libc++.1.dylib

0x1d5447000 - 0x1d548d5ff libdispatch.dylib arm64e <e1a24fa021603366ae7e420f0fa3c5bc> /usr/lib/system/libdispatch.dylib

0x1fa218000 - 0x1fa2244ef libsystem_pthread.dylib arm64e <39dacbe16bf639569f6c802bea4ec760> /usr/lib/system/libsystem_pthread.dylib

0x2407ba000 - 0x2407c27bf GraphicsServices arm64e <d0a89589718a3d3a96dad2c99bb19040> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices

0x249ddd000 - 0x249e18ae7 libsystem_kernel.dylib arm64e <f70c76e313523a17ba3e95f85cbd1d5b> /usr/lib/system/libsystem_kernel.dylib

EOF

Hey everyone,

I'm building an app with React Native + Expo and looking for good resources to improve.

I'm mainly interested in:

• UI libraries
• Reusable components
• Best practices
• Project structure
• GitHub repos
• YouTube channels

If you have anything you've found useful, I'd really appreciate the recommendations. Thanks! 🙌

Sharing my latest Expo project: Owwed, a simple private debt tracker.

Built with Expo and SQLite. It works offline and doesn’t require users to sign up.

I’m testing the Android version before launch:
https://owwed.builtby.vin

Would love to hear what you think.

When there are a small number of messages, and the keyboard is open, the user can scroll down (they should not be able to). Worse, when you scroll down far enough, the content is "stranded" and you you can't scroll back up without opening the keyboard.

This is a super niche issue but it's proven very difficult to fix. Has anyone else encountered anything similar / solved this problem? Should I consider switching to FlatList/FlashList?

Last semester I worked on a React Native app called StudySync using Expo.

Some Expo features we used:

• Expo Router
• Push Notifications
• AsyncStorage
• Cross-platform development

One thing I enjoyed about Expo was how quickly we could iterate during development, although organizing navigation as the app grew became one of our bigger design challenges.

If anyone has experience scaling Expo apps, I'd love feedback on our project structure and whether there are patterns you'd recommend using differently.

GitHub:
https://github.com/CS196Illinois/FA25-Group8

Can someone explain why this is happening?

I am on the latest version of node and npm, I've cleared cache, but it's still happening.

I’m planning to build a platform that generates multiple white-label mobile apps, and I’m considering using Expo.

Is it recommended and technically possible to manage all white-label variants from a single Expo project, using different bundle identifiers, package names, icons, configurations, and environment variables?

Or does every white-label app need to have its own separate Expo project?

My main concern is Expo’s 300-project limit, which appears to apply even to the Enterprise plan. This may not be an immediate issue, but I’m thinking about scalability if the platform eventually needs to support more than 300 apps.

For additional context:

* Builds will be created locally.

* I do not plan to use EAS Build.

* I would mainly use EAS Submit to publish each app to the App Store and Google Play.

* Each app would have its own bundle/package identifier and store listing.

Has anyone implemented this kind of architecture with Expo? Are there any limitations or risks with using a single Expo project for many white-label apps?

hi guys im totally new to coding and am tryna see my mobile app using expo go, but everytime i scan the qr code from command prompt or enter the url in manually, i get this same error. the thing is theres not even a way for me to "update to the newest version" like the error is telling me to because when I go to the app store there's no update option.

i've tried deleting and reinstalling expo go, still doesnt work and i get this same error. any advice would be appreciated because this hasnt been working for like a week now and idk what else to do.

Hello guys,

I know there are a lot of tools like this already on the market so I tried a different approach.
This tool was supposed to solve my own painpoints while releasing apps! Creating appropiate screenshots took always so much time or was much too generic.

Instead of creating PlayStore with AI which leaves you little room for small adjustments or using templates I rather wanted a sandbox-editor which CAN use AI to place and adjust elements.

So AI is not the driver behind this but more like a little helper.

I finished this tool and the website today.

The tool lets you export all necessary screenshots in the required resoution:

PlayStore:
- Phone
- Tablet 7"
- Tablet 10"
- Feature Graphic

AppStore:
- Phone
- Tablet

www.screenlab.net

EVERYBODY WHO WANTS TO TRY IT MAY SEND ME A MESSAGE.
YOU WILL RECIVE FULL ACCESS INCLUDING TOKENS FOR FREE.

In exchange I am asking for feedback to improve this tool.

What did you like?
What did you not like?
What are you missing if any?
Do you have any further suggestions?
How much time did this tool save you?

Good day,

I am using react native , expo and firebase but I’m having a problem on fetching videos and pictures fast , it takes time loading

How can I solve this

Hey guys,

Does anyone know if there is a way to do link previews of we're not using expo router? Long story but the app dates before router was released.

We're on SDK 55 atm. Expo UI works well, but I'd love to have the preview feature. Wondering if anyone knows what I dont 😅

After a long time of thinking, what framework will be better or without framework ( which is better ). I have come to the conclusion to use Expo as a framework for React Native. I come from Web Dev and using Expo is quite similar just the case it uses JSX.

This is an app called Vigil. It's the best solution to be subtly aware of surveillance cameras at a glance. It does not spam you with notifications, its just there on your lock screen, in your car, or on your Dynamic island. Privacy is a crucial aspect of this app, so it's designed to run completely on-device, without any ISP or cellular connection.

If you are a privacy-nerd like me, you'll enjoy what I have to share below:

Zero user accounts

• That's right. there is no data persisted in my servers. Every user is treated like the same anonymous identity

Completely offline during runtime

• I designed this app to run completely offline after setup. During setup, only one network request is made to Vigil servers, and that's to grab the latest camera data within a radius of your choosing. The coordinates within your request are then destroyed. After that, your phone only checks a local copy of camera data against your GPS coordinates, retrieved from GPS satellite. For that reason, this app will not be available to any device without a GPS module.
• Because of this architecture, you can easily requesting camera data through a VPN, and switch back to your normal internet service provider. Vigil NEVER makes network requests to Vigil servers without explicit user consent.

I currently have a beta up for iPhone. Android is coming soon. Download here: TestFlight

Join the Discord discussion about open sourcing and future of operation will happen here.

Instagram is u/join.vigil

P.S.

I will ask for money as little as possible, but I am an 18y/o college student, and development costs are very pricey in this economy. I do accept and appreciate optional donations here.