Thank you for your continued feedback with our latest release (3.2.0). We want to share with you some issues you’ve helped us identify, relevant workarounds, and what we are doing to ultimately resolve them.
1) Issue: Device build fails for Android on a Windows machine
This issue occurs because we packaged a dynamic linked version of Visual C++ libraries versus the static linked version. This means if you do not have the Visual C++ runtime libraries installed, your build will fail.
Workaround: Download and install the Microsoft Visual C++ runtime libraries.
2) Issue: Alloy created applications on 3.1.3 or earlier SDK must be upgraded to 3.2.0 SDK before being able to successfully build.
This issue occurred because Appcelerator changed where resource directories located in Titanium Studio.
Workarounds: You can either update your application to work with 3.2.0, revert back to Alloy 1.3.0, or you can use our beta version of Alloy 1.3.1 which fixes this issue.
npm install –g email@example.com
npm install –g firstname.lastname@example.org
3) Issue: Getting “Permission Denied” when running Android Emulator
This issue is when attempting to access native features such as camera or vibrate, you see “Permission Denied”. This is because the permissions are not in the androidManifest.xml.
Workarounds: Develop using a physical device or you could also use the CLI to perform a build-only device build and manually install the generated apk into the emulator
ti build -p android -T device --build-only
adb -e install build/android/bin/
We are currently working on 3.2.1 that will include resolution to these issues that will be released in the coming weeks. We apologize for any inconvenience that these issues may have caused you. If you have run into the problems stated above, please follow the suggested workarounds.