Application force closes itself

[GoogleCodeExporter]

I am trying to use the code for v2.2.0 to use for my project. When I try to 
generate apks using Eclipse, and try to install it on the device or on an 
emulator, the application force closes itself. Could you let me know why would 
that occur? Also, if this is not how it is to be done, then what steps should 
be followed to correctly generate the apks. Thanks a lot.

Original issue reported on code.google.com by dharasha...@gmail.com on 13 Jun 2011 at 8:13

[GoogleCodeExporter]

You have 2 applications to build and to install on your device:
1) the RCS core: this is a RCS service that you may start via the RCS settings.
2) the RI application: when you create this project you should define the RCS 
core as a library in order to share the RCS API (client side).

Note: use a 2.x Android SDK.

Then for details, all is described at http://developer.android.com.

For other problems, give us the traces (logcat output). Thks.

Original comment by jmauffret@gmail.com on 14 Jun 2011 at 6:35

• Changed state: Done

[GoogleCodeExporter]

Thanks a lot for the answer. I will try to work it out that way.

Original comment by dharasha...@gmail.com on 14 Jun 2011 at 1:19

[GoogleCodeExporter]

I am trying to generate the apks from Eclipse and then installing it via 
command prompt on an emulator. It does not allow me to install the apks saying 
the install parse is failed. I am attaching the same in the file. I would 
really appreciate any help of yours in the same. Thanks.

Original comment by dharasha...@gmail.com on 14 Jun 2011 at 1:59

[GoogleCodeExporter]

I tried to install the apks. Now, when I initiate a one-to-one chat, the 
invitation fails each time for no apparent reason. Any help regarding the same 
would be appreciated.

Original comment by dharasha...@gmail.com on 15 Jun 2011 at 3:43

[GoogleCodeExporter]

Please give me your traces.

Original comment by jmauffret@gmail.com on 16 Jun 2011 at 2:42

[GoogleCodeExporter]

I am attaching a wireshark trace for the same. Thanks.

Original comment by dharasha...@gmail.com on 16 Jun 2011 at 2:50

Attachments:

• try6.pcap

[GoogleCodeExporter]

I am also attaching the logcat traces for the same.

Original comment by dharasha...@gmail.com on 16 Jun 2011 at 3:12

Attachments:

• trialtest1
• trialtest2

[GoogleCodeExporter]

Hi,I know the answer.

your from header of INVITE message is tel URI,this is the reason of 403 
forbidden.

See that class
package com.orangelabs.rcs.core.ims.service;
ImsServiceSession
public void createOriginatingDialogPath()
about on Line 123

// Create a dialog path
        dialogPath = new SipDialogPath(
                getImsService().getImsModule().getSipManager().getSipStack(),
                callId,
                1,
                getRemoteContact(),
                // TODO: remove format number when bug corrected on IMS
                PhoneUtils.formatNumberToSipAddress(ImsModule.IMS_USER_PROFILE.getPublicUri()),
                getRemoteContact(),
                route);

change 
PhoneUtils.formatNumberToSipAddress(ImsModule.IMS_USER_PROFILE.getPublicUri()) 
into ImsModule.IMS_USER_PROFILE.getPublicUri()

This is a bug.

Original comment by Splash.P...@gmail.com on 17 Jun 2011 at 4:35

[GoogleCodeExporter]

Thanks a lot for the help. Would definitely try that. 

Original comment by dharasha...@gmail.com on 17 Jun 2011 at 5:20

[GoogleCodeExporter]

In fact we have a TODO here due to a problem on our IMS+AS_IM which works only 
with a Tel-URI. Your correction is correct.

Original comment by jmauffret@gmail.com on 20 Jun 2011 at 9:39

[GoogleCodeExporter]

Thank you.

Original comment by dharasha...@gmail.com on 21 Jun 2011 at 2:09