I 've a build error once I am trying to create a production android build or production ios build for Stories.
I’ve expokit workflow, expo-cli 4.1.3 version, expo SDK 36
Steps which I did
expo eject(choosing expokit)
expo publish
cd android, ./gradlew clean assembleRelease
It respond the following error
** What went wrong:* Execution failed for task ‘:app:bundleReleaseExpoAssets’. > Process ‘command ‘./node_modules/expokit/detach-scripts/run-exp.sh’’ finished with non-zero exit value 1
I noticed also resources were not added to the folder
android/app/build/intermediates/merged_assets/release/out
we did not. In fact, this is the response we got back from the Expo support… We can’t produce a Production Build, and this level is support is simply unacceptable!
ExpoKit was deprecated almost two years ago, and is no longer supported. The last SDK version compatible with ExpoKit was SDK38, and we stopped supporting SDK38 in July 2021. There’s a chance you could get Bare workflow working but you would likely still need to upgrade your SDK version for builds to be submittable to app stores, as some SDK releases have included support for store policy changes.
There’s unfortunately not a great silver bullet here aside from upgrading your app - if you need help doing that, I’d recommend one of the consultants we ourselves work with. I’m happy to make a direct intro to help get the ball rolling faster.
Depending on what dependencies you are using you might be able to switch back to the managed workflow. With EAS Build you can even use libraries that need native code that is not included in the Expo SDK.
ExpoKit is no longer supported. So the real answer is to upgrade to a supported Expo SDK and migrate to the bare workflow (or the managed workflow). But in the mean time, @jeremiahlachica27’s answer looks like it might work.