A month or so ago, I followed the Expo/ ExpoKit upgrade instructions here: Expo SDK 34 is now available. Expo SDK v34.0.0 is out today and is… | by Eric Samelson | Exposition. I didn’t test on iOS 13 (stupid me!) because I didn’t have a test device and didn’t want to blow up my build environment. I released the app, somebody tried it on iOS13, and it crashed. So, I broke down and installed Xcode 11 beta 7 and tried things out. I forgot to copy the error down, but it was a dead-ringer for the attribute issue fixed here: [ios13] Add support for iOS 13's unused attribute marker · expo/expo@bc370a7 · GitHub.
So, I ran expo init to create a new blank project and ejected it, installed pods, built it, and it worked great. I looked at the differences between my project at the new blank project, and the tag for the ExpoKit pod was “2.12.4”, where mine was “2.12.0”. So I changed that reinstalled my pods, still didn’t fix it. I then noticed in packages.json that the blank project had https://github.com/expo/react-native/archive/sdk-34.0.1.tar.gz for react-native, while I had 34.0.0 (which was from the upgrade instructions as I recall). I upgraded that, the reinstalled all my pods, and it worked!
Anyway, wanted to check to see if that jived with reality (did that iOS 13 fix really ship in 34.0.1 of the RN fork?) and to let folks know in case they’re running into problems.
