We would like to change the mobile application name from CommCare to our
application name. Is this possible and if yes, could you please let us know
how to configure it ?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
If you are compiling a custom build with your own signing certificate this
is possible, yes. You can change the app.name property in the
build.properties file before compiling to change what the midlet name is.
-Clayton
···
On Wed, Jul 4, 2012 at 6:43 AM, Sathishkumar Thangavel < tsathish@thoughtworks.com> wrote:
Hi,
We would like to change the mobile application name from CommCare to our
application name. Is this possible and if yes, could you please let us know
how to configure it ?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
We are using the build from http://build.dimagi.com:250/. Is the source
available somewhere for us to make change and compile?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
···
On Thu, Jul 5, 2012 at 7:48 PM, Clayton Sims wrote:
Sathish,
If you are compiling a custom build with your own signing certificate this
is possible, yes. You can change the app.name property in the
build.properties file before compiling to change what the midlet name is.
We would like to change the mobile application name from CommCare to our
application name. Is this possible and if yes, could you please let us know
how to configure it ?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
In order to put applications on a phone after compilation you'll need a
signing certificate if you want to be able to set Application Permissions
(access file system without prompting the user, etc), though. We provide
that service for our compiled version of CommCare, but can't sign custom
compiled versions since we can't be liable for the code in them.
-Clayton
···
On Thu, Jul 5, 2012 at 10:08 PM, Sathishkumar Thangavel < tsathish@thoughtworks.com> wrote:
Hi Clayton,
We are using the build from http://build.dimagi.com:250/. Is the source
available somewhere for us to make change and compile?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
On Thu, Jul 5, 2012 at 7:48 PM, Clayton Sims csims@dimagi.com wrote:
Sathish,
If you are compiling a custom build with your own signing certificate
this is possible, yes. You can change the app.name property in the
build.properties file before compiling to change what the midlet name is.
We would like to change the mobile application name from CommCare to our
application name. Is this possible and if yes, could you please let us know
how to configure it ?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
In order to put applications on a phone after compilation you'll need a
signing certificate if you want to be able to set Application Permissions
(access file system without prompting the user, etc), though. We provide
that service for our compiled version of CommCare, but can't sign custom
compiled versions since we can't be liable for the code in them.
We are using the build from http://build.dimagi.com:250/. Is the source
available somewhere for us to make change and compile?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
On Thu, Jul 5, 2012 at 7:48 PM, Clayton Sims csims@dimagi.com wrote:
Sathish,
If you are compiling a custom build with your own signing certificate
this is possible, yes. You can change the app.name property in the
build.properties file before compiling to change what the midlet name is.
We would like to change the mobile application name from CommCare to
our application name. Is this possible and if yes, could you please let us
know how to configure it ?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
You can obtain a code signing certificate from anyone that offers the
appropriate Certificate Authority on the phones you're working with. Our
certificate is from Thawte.
-Clayton
···
On Sun, Jul 8, 2012 at 11:47 PM, Sathishkumar Thangavel < tsathish@thoughtworks.com> wrote:
Thanks Clayton,
Where can we find the certificate if we want to go ahead with your build
of commcare?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
On Fri, Jul 6, 2012 at 8:46 PM, Clayton Sims csims@dimagi.com wrote:
In order to put applications on a phone after compilation you'll need a
signing certificate if you want to be able to set Application Permissions
(access file system without prompting the user, etc), though. We provide
that service for our compiled version of CommCare, but can't sign custom
compiled versions since we can't be liable for the code in them.
We are using the build from http://build.dimagi.com:250/. Is the source
available somewhere for us to make change and compile?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
On Thu, Jul 5, 2012 at 7:48 PM, Clayton Sims csims@dimagi.com wrote:
Sathish,
If you are compiling a custom build with your own signing certificate
this is possible, yes. You can change the app.name property in the
build.properties file before compiling to change what the midlet name is.
We would like to change the mobile application name from CommCare to
our application name. Is this possible and if yes, could you please let us
know how to configure it ?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
We would like to go ahead with your build for this release. To use your
service what is the procedure that we need to follow.
···
> In order to put applications on a phone after compilation you'll need a
>>> signing certificate if you want to be able to set Application Permissions
>>> (access file system without prompting the user, etc), though. We provide
>>> that service for our compiled version of CommCare, but can't sign custom
>>> compiled versions since we can't be liable for the code in them.
>>>
>>> -Clayton
>>>
>>>
The builds are named and listed as "CommCare 1.0", "CommCare 1.1", etc.
"CommCare Trunk" is the newest version (2.0) which is pending release soon.
You can download the Jad/Jar file for your platform under the "Artifacts"
for the specific builds.
-Clayton
···
On Wed, Jul 11, 2012 at 1:39 AM, sathish wrote:
Hi Clayton,
We would like to go ahead with your build for this release. To use your
service what is the procedure that we need to follow.
In order to put applications on a phone after compilation you'll need a
signing certificate if you want to be able to set Application Permissions
(access file system without prompting the user, etc), though. We provide
that service for our compiled version of CommCare, but can't sign custom
compiled versions since we can't be liable for the code in them.
But when we build the application in Release Manager, commcare-hq expects
the keystore to be present in order to sign the application jar file. Is it
something you could provide?
Regards,
Sathish
ThoughtWorks | Chennai
···
On Wed, Jul 11, 2012 at 8:10 PM, Clayton Sims wrote:
Sathish,
You can obtain the latest builds of CommCare from our build server at
We would like to go ahead with your build for this release. To use your
service what is the procedure that we need to follow.
In order to put applications on a phone after compilation you'll need a
signing certificate if you want to be able to set Application Permissions
(access file system without prompting the user, etc), though. We provide
that service for our compiled version of CommCare, but can't sign custom
compiled versions since we can't be liable for the code in them.
Ah, you're correct. Sorry, I had forgotten that part of the process.
Unfortunately we cannot provide a signing certificate, since they are
issued per-organization. If you want to sign applications you will need to
obtain a code signing certificate. If desired, you could create a "Remote
Application" on the cloud www.commcarehq.org that would submit to your
server instead of www.commcarehq.org, which is the only way to create an
app signed by our certificate.
You can also simply skip the signing process, but that will result in the
app not being able to have certain permissions set to "Always allowed", and
thus will display a prompt to the user each time the permission is
requested.
-Clayton
···
On Wed, Jul 11, 2012 at 11:59 AM, Sathishkumar Thangavel < tsathish@thoughtworks.com> wrote:
Thanks Clayton,
But when we build the application in Release Manager, commcare-hq expects
the keystore to be present in order to sign the application jar file. Is it
something you could provide?
Regards,
Sathish
ThoughtWorks | Chennai
On Wed, Jul 11, 2012 at 8:10 PM, Clayton Sims csims@dimagi.com wrote:
Sathish,
You can obtain the latest builds of CommCare from our build server at
We would like to go ahead with your build for this release. To use your
service what is the procedure that we need to follow.
In order to put applications on a phone after compilation you'll need a
signing certificate if you want to be able to set Application Permissions
(access file system without prompting the user, etc), though. We provide
that service for our compiled version of CommCare, but can't sign custom
compiled versions since we can't be liable for the code in them.
Remote application option is a really good option for us. But we want to
know how update version of mobile app works with remote app or normal app
for that matter. We want to know how to get the latest release of the app
installed on mobile phones.
Regards,
Sathish
···
On Friday, July 13, 2012 1:29:20 AM UTC+5:30, Clayton Sims wrote:
>
> Sathish,
>
> Ah, you're correct. Sorry, I had forgotten that part of the process.
> Unfortunately we cannot provide a signing certificate, since they are
> issued per-organization. If you want to sign applications you will need to
> obtain a code signing certificate. If desired, you could create a "Remote
> Application" on the cloud www.commcarehq.org that would submit to your
> server instead of www.commcarehq.org, which is the only way to create an
> app signed by our certificate.
>
> You can also simply skip the signing process, but that will result in the
> app not being able to have certain permissions set to "Always allowed", and
> thus will display a prompt to the user each time the permission is
> requested.
>
> -Clayton
>
> On Wed, Jul 11, 2012 at 11:59 AM, Sathishkumar Thangavel < tsathish@thoughtworks.com> wrote:
>
>> Thanks Clayton,
>>
>> But when we build the application in Release Manager, commcare-hq expects
>> the keystore to be present in order to sign the application jar file. Is it
>> something you could provide?
>>
>> Regards,
>> Sathish
>>
>> ThoughtWorks | Chennai
>>
>> On Wed, Jul 11, 2012 at 8:10 PM, Clayton Sims wrote:
>>
>>> Sathish,
>>>
>>> You can obtain the latest builds of CommCare from our build server at
>>>
>>> http://build.dimagi.com:250
>>>
>>> The builds are named and listed as "CommCare 1.0", "CommCare 1.1", etc.
>>> "CommCare Trunk" is the newest version (2.0) which is pending release soon.
>>>
>>> You can download the Jad/Jar file for your platform under the
>>> "Artifacts" for the specific builds.
>>>
>>> -Clayton
>>>
>>>
>>> On Wed, Jul 11, 2012 at 1:39 AM, sathish wrote:
>>>
>>>> Hi Clayton,
>>>>
>>>> We would like to go ahead with your build for this release. To use your
>>>> service what is the procedure that we need to follow.
>>>>
>>>>
>>>>> In order to put applications on a phone after compilation you'll need
>>>>>>> a signing certificate if you want to be able to set Application Permissions
>>>>>>> (access file system without prompting the user, etc), though. We provide
>>>>>>> that service for our compiled version of CommCare, but can't sign custom
>>>>>>> compiled versions since we can't be liable for the code in them.
>>>>>>>
>>>>>>> -Clayton
>>>>>>>
>>>>>>>
>>>
>>
>
Remote application option is a really good option for us. But we want to
know how update version of mobile app works with remote app or normal app
for that matter. We want to know how to get the latest release of the app
installed on mobile phones.
Everytime you make a build it grabs the latest version of the application
from the repository.
Cory
···
On Tue, Jul 17, 2012 at 10:24 PM, sathish wrote:
Regards,
Sathish
On Friday, July 13, 2012 1:29:20 AM UTC+5:30, Clayton Sims wrote:
Sathish,
Ah, you're correct. Sorry, I had forgotten that part of the process.
Unfortunately we cannot provide a signing certificate, since they are
issued per-organization. If you want to sign applications you will need to
obtain a code signing certificate. If desired, you could create a "Remote
Application" on the cloud www.commcarehq.org that would submit to your
server instead of www.commcarehq.org, which is the only way to create an
app signed by our certificate.
You can also simply skip the signing process, but that will result in the
app not being able to have certain permissions set to "Always allowed", and
thus will display a prompt to the user each time the permission is
requested.
But when we build the application in Release Manager, commcare-hq
expects the keystore to be present in order to sign the application jar
file. Is it something you could provide?
Regards,
Sathish
ThoughtWorks | Chennai
On Wed, Jul 11, 2012 at 8:10 PM, Clayton Sims csims@dimagi.com wrote:
Sathish,
You can obtain the latest builds of CommCare from our build server at
We would like to go ahead with your build for this release. To use
your service what is the procedure that we need to follow.
In order to put applications on a phone after compilation you'll need
a signing certificate if you want to be able to set Application Permissions
(access file system without prompting the user, etc), though. We provide
that service for our compiled version of CommCare, but can't sign custom
compiled versions since we can't be liable for the code in them.
Sorry, I am not very clear about it. There will be two repositories now if
I use remote app(our actual server and commcare-hq cloud). Where exactly it
will look for new version and where will the jar downloaded from.
We played a little and it seems to us that it first looks for version
update in cloud app and then downloads from our app(when we try to launch
the downloaded app it says 'application from untrusted supplier..'
something like that!). Is this the correct observation?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
···
On Wed, Jul 18, 2012 at 9:30 PM, Cory Zue wrote:
Remote application option is a really good option for us. But we want to
know how update version of mobile app works with remote app or normal app
for that matter. We want to know how to get the latest release of the app
installed on mobile phones.
Everytime you make a build it grabs the latest version of the application
from the repository.
Cory
Regards,
Sathish
On Friday, July 13, 2012 1:29:20 AM UTC+5:30, Clayton Sims wrote:
Sathish,
Ah, you're correct. Sorry, I had forgotten that part of the process.
Unfortunately we cannot provide a signing certificate, since they are
issued per-organization. If you want to sign applications you will need to
obtain a code signing certificate. If desired, you could create a "Remote
Application" on the cloud www.commcarehq.org that would submit to your
server instead of www.commcarehq.org, which is the only way to create
an app signed by our certificate.
You can also simply skip the signing process, but that will result in
the app not being able to have certain permissions set to "Always allowed",
and thus will display a prompt to the user each time the permission is
requested.
But when we build the application in Release Manager, commcare-hq
expects the keystore to be present in order to sign the application jar
file. Is it something you could provide?
Regards,
Sathish
ThoughtWorks | Chennai
On Wed, Jul 11, 2012 at 8:10 PM, Clayton Sims csims@dimagi.com wrote:
Sathish,
You can obtain the latest builds of CommCare from our build server at
We would like to go ahead with your build for this release. To use
your service what is the procedure that we need to follow.
In order to put applications on a phone after compilation you'll
need a signing certificate if you want to be able to set Application
Permissions (access file system without prompting the user, etc), though.
We provide that service for our compiled version of CommCare, but can't
sign custom compiled versions since we can't be liable for the code in them.
The recommendation I was offering was that you build the application purely on the HQ cloud as a remote application which submits to your
actual server instead of CommCare HQ's Cloud. You won't be able to execute
any builds (with appropriate permissions) from your local server until they
are signed by a proper signing certificate, so this would be a way for you
to use your server to host data, but use the CommCareHQ Cloud server to
create the jar and jad files.
-Clayton
···
On Wed, Jul 18, 2012 at 1:12 PM, Sathishkumar Thangavel < tsathish@thoughtworks.com> wrote:
Hi Cory,
Sorry, I am not very clear about it. There will be two repositories now if
I use remote app(our actual server and commcare-hq cloud). Where exactly it
will look for new version and where will the jar downloaded from.
We played a little and it seems to us that it first looks for version
update in cloud app and then downloads from our app(when we try to launch
the downloaded app it says 'application from untrusted supplier..'
something like that!). Is this the correct observation?
Regards,
Sathish
Sathishkumar T | +919840437701 | ThoughtWorks | Chennai
On Wed, Jul 18, 2012 at 9:30 PM, Cory Zue czue@dimagi.com wrote:
Remote application option is a really good option for us. But we want to
know how update version of mobile app works with remote app or normal app
for that matter. We want to know how to get the latest release of the app
installed on mobile phones.
Everytime you make a build it grabs the latest version of the application
from the repository.
Cory
Regards,
Sathish
On Friday, July 13, 2012 1:29:20 AM UTC+5:30, Clayton Sims wrote:
Sathish,
Ah, you're correct. Sorry, I had forgotten that part of the process.
Unfortunately we cannot provide a signing certificate, since they are
issued per-organization. If you want to sign applications you will need to
obtain a code signing certificate. If desired, you could create a "Remote
Application" on the cloud www.commcarehq.org that would submit to your
server instead of www.commcarehq.org, which is the only way to create
an app signed by our certificate.
You can also simply skip the signing process, but that will result in
the app not being able to have certain permissions set to "Always allowed",
and thus will display a prompt to the user each time the permission is
requested.
But when we build the application in Release Manager, commcare-hq
expects the keystore to be present in order to sign the application jar
file. Is it something you could provide?
Regards,
Sathish
ThoughtWorks | Chennai
On Wed, Jul 11, 2012 at 8:10 PM, Clayton Sims csims@dimagi.comwrote:
Sathish,
You can obtain the latest builds of CommCare from our build server at
We would like to go ahead with your build for this release. To use
your service what is the procedure that we need to follow.
In order to put applications on a phone after compilation you'll
need a signing certificate if you want to be able to set Application
Permissions (access file system without prompting the user, etc), though.
We provide that service for our compiled version of CommCare, but can't
sign custom compiled versions since we can't be liable for the code in them.