Author Topic: Error in configuring android project  (Read 1512 times)


  • Community Member
  • Posts: 14
  • Hero Points: 0
Error in configuring android project
« on: August 21, 2019, 08:10:10 pm »
Any suggestions on what I need to do to configure my slickedit for android app builds?
I'm using SlickEdit Pro 2015 (v20.0.1.3 64-bit), running on Ubuntu 18.04.3 LTS

This is the first android app I've created with slickedit (I usually use it for C, C++, and PHP). When I try to create the project, I get the error message

Code: [Select]
Unable to execute android tool: Error code out of range: 0
I started vs from the command line. When I use the procedure shown below, I get this error in the console when the above error is shown:
Code: [Select]
The "android" command is deprecated.
For manual SDK, AVD, and project management, please use Android Studio.
For command-line tools, use tools/bin/sdkmanager and tools/bin/avdmanager
Invalid or unsupported command "create project --target debug --name haven --path /home/mgfrobozz/git/haven/ --activity havenActivity --package"

Supported commands are:
android list target
android list avd
android list device
android create avd
android move avd
android delete avd
android list sdk
android update sdk

I'm using this procedure:
Code: [Select]
Project Type: Java - Android Application
Set project name and directory
Click OK
Set app name and activity name
Set android sdk location to /home/mgfrobozz/Android/Sdk
Set build target to debug
Click OK
« Last Edit: August 21, 2019, 08:35:52 pm by MgFrobozz »


  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1373
  • Hero Points: 127
Re: Error in configuring android project
« Reply #1 on: August 21, 2019, 08:36:11 pm »
The Android support in v20 doesn't support the newer versions of the Android SDK.  (roughly since Android moved to Gradle based builds). 

The Android support was updated in v24, which is in beta now if you want to try it out.  We're at beta 2 right now.  There are several fixes for the Android support that are queued up for beta 3, so you could also wait for beta 3 if you don't want to risk running into a known problem.