How to generate .apk file of the app built using ionic framework?

I have netbeans installed in the system … Is it ok ?

yeah but that has nothing to do with the topic^^… you can choose your ide or editor on your own

Okie … then what should I do now ? I have found out in some forum that we need to set the extract to path in file /home/administrator/.profile.txt … Is it the right way ? I have downloaded and placed the Android SDK file in some file location …

you need to set the environment variable:

export ANDROID_HOME=pathToAndroid
export JAVA_HOME=pathToJava

pathToAndroid is the path to the android-sdk-file right ?
pathToJava : ? JAVA SDK ?
where to paste these above 2 lines in the *.profile.js ? My *.profile.js looks like the below

~/.profile: executed by the command interpreter for login shells.

This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login


see /usr/share/doc/bash/examples/startup-files for examples.

the files are located in the bash-doc package.

the default umask is set in /etc/profile; for setting the umask

for ssh logins, install and configure the libpam-umask package.

#umask 022

if running bash

if [ -n “$BASH_VERSION” ]; then
# include .bashrc if it exists
if [ -f “$HOME/.bashrc” ]; then
. "$HOME/.bashrc"

set PATH so it includes user’s private bin if it exists

if [ -d “$HOME/bin” ] ; then

i does not know anything about a profile.js

you can set the variables in your bashrc.
but you can simple run both export-commands in a shell to set them temporary for testing purpose.

And yes pathToAndroid = path to android SDK
pathToJava = path to Java SDK

Okie my .bashrc file looks like the below … where should I add the above 2 codes ( At the beginning or at the end ) ?

~/.bashrc: executed by bash(1) for non-login shells.

see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)

for examples

If not running interactively, don’t do anything

case $- in
i) ;;
*) return;;

don’t put duplicate lines or lines starting with space in the history.

See bash(1) for more options


append to the history file, don’t overwrite it

shopt -s histappend

for setting history length see HISTSIZE and HISTFILESIZE in bash(1)


check the window size after each command and, if necessary,

update the values of LINES and COLUMNS.

shopt -s checkwinsize

If set, the pattern “**” used in a pathname expansion context will

match all files and zero or more directories and subdirectories.

#shopt -s globstar

make less more friendly for non-text input files, see lesspipe(1)

[ -x /usr/bin/lesspipe ] && eval “$(SHELL=/bin/sh lesspipe)”

set variable identifying the chroot you work in (used in the prompt below)

if [ -z “${debian_chroot:-}” ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)

set a fancy prompt (non-color, unless we know we “want” color)

case “$TERM” in
xterm-color) color_prompt=yes;;

uncomment for a colored prompt, if the terminal has the capability; turned

off by default to not distract the user: the focus in a terminal window

should be on the output of commands, not on the prompt


if [ -n “$force_color_prompt” ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it’s compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)

if [ “$color_prompt” = yes ]; then
PS1=’${debian_chroot:+($debian_chroot)}[\033[01;32m]\u@\h[\033[00m]:[\033[01;34m]\w[\033[00m]$ ‘
PS1=’${debian_chroot:+($debian_chroot)}\u@\h:\w$ '
unset color_prompt force_color_prompt

If this is an xterm set the title to user@host:dir

case “$TERM” in
PS1="[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a]$PS1"

enable color support of ls and also add handy aliases

if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval “$(dircolors -b ~/.dircolors)” || eval "$(dircolors -b)"
alias ls=‘ls --color=auto’
#alias dir=‘dir --color=auto’
#alias vdir=‘vdir --color=auto’

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'


some more ls aliases

alias ll='ls -alF’
alias la='ls -A’
alias l=‘ls -CF’

Add an “alert” alias for long running commands. Use like so:

sleep 10; alert

alias alert=‘notify-send --urgency=low -i “$([ $? = 0 ] && echo terminal || echo error)” "$(history|tail -n1|sed -e ‘’‘s/^\s*[0-9]+\s*//;s/[;&|]\s*alert$//’’’)"’

Alias definitions.

You may want to put all your additions into a separate file like

~/.bash_aliases, instead of adding them here directly.

See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases

enable programmable completion features (you don’t need to enable

this, if it’s already enabled in /etc/bash.bashrc and /etc/profile

sources /etc/bash.bashrc).

if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion

sry but please format it in a code block…

but you can simply add it at the beginning.
Keep in mind to use absolute paths to not destroy your system :slight_smile:

Okie bengtier … thanks for the reply … I have 1 more clarification … suppose if I dont give the export JAVA_HOME=pathToJava in the .bashrc file … is it not possible to extract the .apk file ??

do not know why you want extract the apk file… the topic is how to generate an apk…

and yes if you do not set this variables before ionic build android … the ionic cli can not find android and java sdk on your system

Okie I meant the same … is there any difference between extract and generate ?

Ok I will install the Java SDK ie; jdk and jre and revert back to u …

the java sdk should be enough :wink:

extract is if you want to unpack an existing apk-file.
generate/build is to create an apk-file

Okie … got it …

Hi bengtier … I have added the following 2 lines on the top of the .bashrc file … but still I am getting the following error … when I try to execute the build command in the terminal …

export ANDROID_HOME={homedirectory}/Documents/Android_SDK/adt-bundle-linux-x86-20140702
export JAVA_HOME={homedirectory}/Documents/Java_SDK/debian

[Error: Android SDK not found. Make sure that it is installed. If it is not at the default location, set the ANDROID_HOME environment variable.]
ERROR building one of the platforms: Error: {homedirectory}/hello/platforms/android/cordova/build: Command failed with exit code 2
You may not have the required environment or OS to build this project
Error: {homedirectory}/hello/platforms/android/cordova/build: Command failed with exit code 2
at ChildProcess.whenDone (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:139:23)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:818:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

Can I know where I am doing wrong ?

then your paths are not correct.

Android path should direct to the rot android-sdk installation folder. For me it is e.g. /opt/android-sdk
This is the root dir. it contains following folders:
add-ons, build-tools, platforms, platform-tools, tools

I think I have not installed Android SDK properly …

My Android_SDK folder contains only the add-ons, platforms and tools but not the build-tools and the platform-tools …

I have just downloaded from the internet and copy - pasted at the /home/documents folder directly without performing any installation steps …

I think I need to install it properly …

I will install it and get back to you …

For future readers, you can check out the buildonic package that will automate the build process for you.