![]() ![]()
Up until about six months ago my work machine had a 256Gb drive, and that meant I couldn’t update XCode, and eventually couldn’t run RN iOS builds. JS gets mocked for the size of node_modules, but iOS development…ach. #EXPO ANDROID STUDIO REACT NATIVE FREE#Personal bugbear is that means ~30Gb free space is needed (about 5× the amount of space of the compressed download). ![]() So I assume you are on a Mac so you can run the build tooling (XCode). Other developers on team really like Expo, so that’s been the decider, and we managed to get around the issue of a few native libraries we had been using previously by finding alternatives within Expo-supported libraries.Īnd I haven’t even started yet to try an iOS buildĪh, hmm. Expo can be ejected, which still allows for the nice web UI and the link to the Expo app on a mobile device for quick development, but then it’s back to AS/Xcode, so I’m just not sure – the DX with Expo is great, but I’ve flip-flopped on this exact issue for about a year now, and I’m still not sure of the right answer. But I’m not 100% sure that long-term that’s as great an advantage as it seems. Not having to fire up Android Studio/XCode every time I want to build anything is amazing. The advantage of Expo from a dev PoV is huge. Whereas with a non-Expo RN app, I can just run a build, get an APK, and shove it on a phone. And some of that is down to my particular situation: where I work, we need control over the build process: we can’t just chuck it over the wall to Expo build servers. Problem is I have no idea what I’m doing. This shows the correct alias/password I’ve used. What I’ve already tried: expo fetch:android:keystore > A failure occurred while executing .$ActionFacade Execution failed for task ':app:signReleaseBundle'. ![]() FAILURE: Build failed with an exception. The error logs from Expo (relevant parts): > Task :app:signReleaseBundle FAILED #EXPO ANDROID STUDIO REACT NATIVE HOW TO#I followed React Native documentation on how to create a keystore via command line: keytool -genkeypair -v -storetype PKCS12 -keystore -alias -keyalg RSA -keysize 2048 -validity 10000Īnd provided the file path to the. Despite being clueless, I chose the latter, so I guess it’s my own fault… My reasoning was that I want the key/keystore on my computer, not on Expo’s servers, so I’m not tied to their services forever. When trying to create the build with Expo, I’m asked if I would like to let Expo handle it for me, or if I’d like to provide my own key. Plus, every attempt takes 15-20 minutes because I’m using Expo’s servers. The Google Play part (using the Play Console) isn’t that much of a problem, but I’m unable to even create a production bundle. Now I’m trying to deploy the app to Google Play and it’s a pain, I’ve been reading docs for two days and I’m completely lost. I’ve recently tried React Native for the first time, and the development process using Expo was delightfully easy. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |