ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #expo
Expo SDK 50 Managed Workflow EAS Pricing Change for Low-Traffic Apps The goal is to lower operating expenses for a low-traffic Expo managed-workflow app while preserving support for occasional updates. Expo SDK 50 introduced EAS Build pricing tied to build minutes and device count, which can dominate costs when builds run frequently. The managed workflow als
Push notification testing in development builds Goal: verify that a development client built with expo-dev-client can receive a remote push notification via Expo’s push service without configuring production APNs or FCM credentials. Constraints: iOS remote push requires a physical device, Android channel behavior may differ between Expo’s service and direct
Goal: guarantee that a retry triggered by a transient network error does not cause the Expo Updates client to write the same JavaScript bundle more than once to local storage. The current mechanism relies on comparing the hash returned by the server with a locally stored hash and using a persistent store (expo‑updates) to skip re‑download when the hashes mat
In Expo, when fetching data, we need to cancel requests if the component unmounts or if a timeout occurs to avoid memory leaks and stale state. The fetch API supports AbortController, but integrating it with React Native's lifecycle and setting a timeout introduces uncertainty about proper cleanup and race conditions. Constraints include ensuring that the ab
I am designing a release process around expo-updates and need to understand the documented fallback behavior when an OTA update fails to load at launch. The docs describe the app reverting to the embedded binary, but the exact mechanics are unclear to me. Assume a recent Expo SDK with expo-updates configured for automatic updates on both iOS and Android. My
Goal: Determine whether Expo Router preserves the original time zone of JavaScript Date objects when they are transmitted through route parameters in development and production builds. In development, the Expo CLI server uses the JavaScript Intl API reflecting the host machine’s time zone, while production bundles on iOS and Android rely on native OS APIs fo
Goal The objective is to guarantee that a schema migration either completes fully or leaves the database unchanged, even when a migration script throws an exception partway through. Current Constraints Expo’s expo-sqlite exposes the native SQLite API. It does not automatically wrap migration blocks in BEGIN / COMMIT / ROLLBACK transactions. When a migration
This investigation examines how Expo's Image component enforces remote image dimension constraints and renders placeholder assets when local storage quotas are exceeded in development builds. The documented capability to cap maximum image dimensions via Image.resolveAssetSource interacts with remote asset resolution, yet the precise point at which the cap is
Goal: Use Expo‑SQLite’s executeSql with LIMIT and OFFSET to paginate a local table while another process may insert or delete rows. Constraint: The module forwards raw SQL to SQLite without providing snapshot isolation, so OFFSET values are calculated on the live table state. Uncertainty: It is unclear whether concurrent modifications cause page boundaries t
android
sqlite