https://blog.yusukeikoma.com/tags/expo/Recent content in expo on Ikoma's BlogHugoen-usWed, 30 Sep 2026 11:33:30 +0900https://blog.yusukeikoma.com/posts/fingerprint-runtime-version-changes-when-you-edit-extra/Wed, 30 Sep 2026 11:33:30 +0900https://blog.yusukeikoma.com/posts/fingerprint-runtime-version-changes-when-you-edit-extra/An over-the-air update is JavaScript that calls into a native binary you cannot change. Treat the runtime version as the ABI version of that binary. Experiments with @expo/fingerprint 0.20.13 show which edits change the hash (extra, version, build numbers, native modules) and which do not (JavaScript, pure-JS dependencies), and a skip list that silently drops a default.https://blog.yusukeikoma.com/posts/react-native-builtin-url-does-not-resolve-dot-dot/Sat, 26 Sep 2026 21:31:14 +0900https://blog.yusukeikoma.com/posts/react-native-builtin-url-does-not-resolve-dot-dot/A client library shared between a website and a React Native app usually fails on the boring parts of the Web platform, not on fetch. Reading React Native 0.87.1 and Expo 57 sources shows three layers of runtime, a URL class that returns ‘/b/c/d/../x’ where the web returns ‘/b/x’, and a fetch with no response stream unless Expo replaces it. A small client that checks what it needs, tested against four simulated runtimes.