Tedious and involved, but ultimately the details are uninteresting. A lot of the steps from the managed -> ExpoKit migration had to be repeated, but we got there in the end.
One interesting detail is that we were able to upgrade to the latest, supported version of react-native-firebase. This library was perhaps the most complicated and fragile element of the ExpoKit-based setup, and it was the one I was most worried about breaking. Now, without ExpoKit's web of conflicting native dependencies, installation and configuration was far simpler.
ExpoKit is huge, and we don't use most of it. This change not only makes our app size smaller, but removes potentially problematic elements such as the Facebook SDK, Admob, and so on. We have the flexibility to add any piece back as a separate module.
How Has This Been Tested?
Built and published new versions to TestFlight and Google Play beta. Smoke tested several parts of the app, particularly areas that required specific changes with the migration; e.g. deep linking (Patreon auth), background audio, push notifications, etc.
Description
Tedious and involved, but ultimately the details are uninteresting. A lot of the steps from the managed -> ExpoKit migration had to be repeated, but we got there in the end.
One interesting detail is that we were able to upgrade to the latest, supported version of react-native-firebase. This library was perhaps the most complicated and fragile element of the ExpoKit-based setup, and it was the one I was most worried about breaking. Now, without ExpoKit's web of conflicting native dependencies, installation and configuration was far simpler.
Background:
Motivation and Context
ExpoKit is huge, and we don't use most of it. This change not only makes our app size smaller, but removes potentially problematic elements such as the Facebook SDK, Admob, and so on. We have the flexibility to add any piece back as a separate module.
How Has This Been Tested?
Built and published new versions to TestFlight and Google Play beta. Smoke tested several parts of the app, particularly areas that required specific changes with the migration; e.g. deep linking (Patreon auth), background audio, push notifications, etc.