Frequently Asked Questions

Problem Definition:

When you attempt to package your application and you get the following error:

Solution:

1. Ensure you have followed the plugins Getting Started Guide
2. Download at least Android SDK 33 (Google Play Console may require a higher SDK)
3. Navigate to Project Settings / Platforms / Android SDK
4. Update SDK API Level to android-<X> where <X> is the SDK version you installed, eg. android-33

Problem Definition:

When you attempt to login to your Google Account using the Launch Google Sign In blueprint node, the failure delegate gets triggered with the following error:

This means that your Android application failed to authenticate with your Google Play Cloud project and there is some misconfiguration in the Google Play Console and/or your Google Cloud Project.

Double Check the Following:

1. You have followed the Getting Started Guide for the plugin
2. You are using the SHA-1 key from your App signing key certificate in the Google Play Console for your Android Credential
3. There are no spaces before or after your SHA-1 key, Package Name and Application Name in your your Android Credential
4. You have an OAuth consent screen setup
5. You are registered as a test user for your OAuth Consent Screen and Google Play Console
6. If you have made any changes to this configuration, they may take a while to propogate through

Problem Definition:

When you still get errors that the billing library version is out of date after installing one of my billing plugins. You would see a simmilar error to the below when uploading your packaged bundle to the Google Play Console. The versions numbers below may change in your error over time.

Solution:

1. Ensure you have followed the Getting Started Guide for the respective plugin
2. Ensure you have disabled any other billing plugins
3. Try upload again
4. If issue persists and you are using a Blueprint only project, convert it to a c++ project

Problem Definition:

Lets say you have a product for sale which you want to check if it has been purchased and activate / deactivate a feature in response to that. A common example of this is a "no-ads" product that can be purchased.

Solution:

1. Ensure your purchase is treated as a non-consumable product, so that it can only be purchased once
2. When you want to check if the purchase has been made, use the Query Purchases Blueprint Node
3. Enable / Disable ads depending on the result of the above query

Problem Definition:

When packaging your application and you get the error:
Error: *.uproject does not look like uproject file but no targets have been found!

Solution:

1. If you are using a Blueprint only project, convert it to a c++ project
2. You should be prompted to install Visual Studio
3. If not, you should install Visual Studio manually

Problem Definition:

When you open your application or when calling a specific blueprint node, if there is a crash, that means something is seriously wrong. In order to find the cause, you will need to retreive the logs from your device which will provide the cause of the crash.

The below solution takes you through how to use adb to retrieve the logs.

Solution:

1. If you have Android Studio, you should have adb installed by default. Confirm this by running adb in a command prompt.
2. Connect your device to your computer and run adb devices to ensure you can see your device.
3. If you cannot see your device, you may need to enable developer mode on your device and trust your PC
4. Run adb logcat -c to clear all current logs on your device to make room for new logs
5. Run adb logcat to begin streaming logs
6. Open your application and trigger the crash
7. Go back to your console and click CNTRL + C to stop streaming logs
8. The logs printed out should now contain information regarding your crash

Problem Definition:

When you package your application and you get a failure regarding the default debug keystore location as seen below.

This is related to your Android Installation and not specifically related to a plugin. Unfortunately, there can be many reasons as to why this can occur and can occur even after a random PC reboot. The below are some things you can try. Its always a good idea to make a backup of your project just in case before making any changes.

Potential Solutions:

1. Ensure your keystore is setup in Project Settings and stored in <PROJECT_NAME>/Build/Android
2. Ensure your project is setup for shipping / distribution
3. Try Updating Android Studio
4. Add a FOLDER_DOT_ANDROID environment variable and set it to .android
5. Ensure you have a debug.keystore in your .android folder located at C:/Users/<User>/.android
6. Ensure you have a debug.keystore in your .android folder located at <Android SDK Installation>/.android
7. Add ANDROID_HOME + ANDROID_SDK_HOME environment variables and set them to the location of your Android Installation
8. Delete your Binaries, Intermediate, Build, DerivedDataCache, Saved and Script folders then reopen your project
9. Restart your PC

Problem Definition:

When you package your application and you get a failure regarding the 'semantic analysis'.
BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 67

This is related to the compatiblity of your Gradle version and your Java version. You can take a look at the Official Gradle Java Runtime Compatibility Matrix to determine which Java version you should have installed.

Solution:

1. Determine what java version you are using to package your project
2. Upgrade/downgrade your java version to be compatible
3. Try Package again

Problem Definition:

When you package your application and you get a failure regarding the 'android:exported'.

Unreal Engine 4 did not update to comply with new Android 12 standards and requires you to specifically specify android:exported.

Solution:

1. Navigate to Project Settings / Platforms / Android / Advanced APK Packaging
2. Add android:exported="true" to your UE4.GameActivity <activity> node in Project Settings

Problem Definition:

When you package your application and you get a failure regarding the 'android:exported'.

Unreal Engine 5 now complies with Android 12 standards and automatically adds this for you, so there is no longer a need to manually add it in project settings.

Solution:

1. Navigate to Project Settings / Platforms / Android / Advanced APK Packaging
2. Remove android:exported="true" to your UE4.GameActivity <activity> node in Project Settings

Problem Definition:

After setting up your blueprint nodes, your OnSuccess / OnFailure delegates are not being triggered.

Solution:

1. Ensure you are running your tests on an actual mobile device
2. If running on your device directly doesnt work, try downloading from an internal testing branch in Google Play
3. Billing or Google Play Services: you may be required to have downloaded your application from the Google Play Store
4. Billing or Google Play Services: you may get inconsistant results when the version on the store differs to the one on your device