"PropertyRequiredException: Issuer cannot be empty, js engine: hermes" error on Android APK
Hi everyone,
I built my Expo app using EAS and built it as an APK, however when opening the app on my Android physical device/emulator it crashes immediately.
On Expo Go the app works fine on both iOS and Android, and when building the app as a development build it works fine on both platforms. The build of the APK obviously succeeds but when I try to run it it just crashes immedietly. Below are the adb logs.
In the logs it is specified that the error is coming from "KindeSDK", I am assuming I may have something wrong with how my environment variables are being set during the build? I am currently building the app using EAS with a .env file with the required Kinde values
3 Replies
Sorry to hear you are hitting an issue with your build with Expo
Do you know if your environment variables are changing during the build process?
Verify .env File Inclusion: Make sure that your .env file is included in the build process. Sometimes, the .env file might not be picked up correctly during the EAS build. You can try explicitly specifying the environment variables in your build configuration.
Deep Link Configuration: Ensure that the deep link configuration is correctly set up in your android/app/build.gradle and AndroidManifest.xml files. This includes adding the necessary meta-data tags and ensuring the correct URL scheme.
Manual Linking: If you are using react-native-keychain and react-native-inappbrowser-reborn, ensure they are correctly linked in your android/settings.gradle and android/app/build.gradle files. Sometimes, these packages may not be automatically linked correctly, resulting in runtime errors.
Clean Build: Sometimes, cleaning the build cache can resolve issues. You can try the following commands to clean the cache:
Let me know if this doesn't solve the issue for you and I can get one of our Expo experts to have a look.
I solved the issue by adding the environment variables to my "eas.json" under the "env" property for my build profiles.
Great to hear you solved it, I will let the team know about the issue you hit