- Newest
- Most votes
- Most comments
Hi @REDACTEDUSER
This unfortunately is a known issue if you have previously configured without the "Compile for Android" setting checked in Setup Assistant before. There is a workaround however; inside BinTemp delete "valid_configuration_platforms.json" and the "module_def" folder. You will need to run the configure command again after doing this, only this time android will be properly configured.
Let me know if you are still having issues.
Hi gFunc, yes "Compile for Android Devices" is enabled.
Here is all my settings
REMOVEDUPLOAD
My Environment Variable
PATH = W:\lumberyard\Android\sdk\tools;W:\lumberyard\Android\sdk\platform-tools;W:\lumberyard\Android\sdk;C:\Program Files\Java\jdk1.8.0_102\bin;C:\Program Files\Java\jre1.8.0_144\bin
AssetProcessor Setup And Work Correctly in dev/cache/VirtualRealityProject/es3 i see folder and assets.
android_settings.json
{
"DEV_KEYSTORE_ALIAS": "development_keystore",
"DEV_KEYSTORE": "_WAF_/android/dev.keystore",
"DISTRO_KEYSTORE_ALIAS": "distribution_keystore",
"DISTRO_KEYSTORE": "_WAF_/android/distro.keystore",
"BUILD_TOOLS_VER": "23.0.3",
"SDK_VERSION": "android-23",
"BUILD_ENVIRONMENT": "Development"
}
Hmm, did you also make sure to enable "Compile for Android Devices" inside of Setup Assistant?
This post is closed: Adding new answers, comments, and votes is disabled.
Relevant content
- Accepted Answerasked 7 years ago
- asked a year ago
- asked 5 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago