RobotiumRC: Can't get remoteResult after re-install another test APK

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Launch test APK named "APK1" and do some tests.
2. Uninstall APK1 and install another test APK named "APK2"(same app, different 
version, includes same activities.)
3. After install APK2, perform methods below,
DUtilities.launchTestInstrumentation();
solo.startMainLauncher();

What is the expected output? What do you see instead?
Expected result:
Lunch main activity of APK2 and keep working.
Actual result:
Throw exception - java.util.concurrent.TimeoutException: waitForRemoteResult 
Timeout before Result
Can't get remote result.

What version of the product are you using? On what operating system?
Win7, 32Bit, RobotiumRCRelease2012.12.12

Original issue reported on code.google.com by enduranc...@gmail.com on 13 Aug 2013 at 5:11

[GoogleCodeExporter]

Toby,

You have installed an old Release.  You should try using the latest 2013.07.12 
Release, and the Overlay as mentioned in the robotium-developers forum.

These can be found at:

https://sourceforge.net/projects/safsdev/files/Robotium%20RemoteControl/2013.07.
12/

The Release should be installed first.  The Overlay, if desired, goes on top of 
the existing 2013.07.12 Release per the Overlay Notes for 2013.08.09. 

I will likely be making a full release by the end of the week that will avoid 
having to do an Overlay (for now).

If you install the 2013.07.12 Release, please let me know if you still 
experience the remoteResults problem.

Carl Nagle
SAS Research & Developpment
Planning, Operations and Strategy
General Applications and Tools
carl.nagle@sas.com

Original comment by carl.na...@sas.com on 13 Aug 2013 at 1:54

• Changed state: Incomplete

[GoogleCodeExporter]

Hi Carl,

Does this means if want to test on android 2.x, i can't use this or other 
related methods ?

Is there anyway to use latest release but still can test on android 2.x ?

I noticed the latest release required API level 15+ 

Thanks
Toby

Original comment by enduranc...@gmail.com on 13 Aug 2013 at 3:23

[GoogleCodeExporter]

Actually, I had always considered that this release along with using robotium 
4.2 would be for testing Robotium 4.x apps and beyond.  However, I am 
researching how difficult (or easy) it will be to make the code work for API 10 
and up.

There are significant changes to Clipboard and Keyboard support that are NOT 
supported in API 10.  So letting the code run (not crash) at API 10 while 
supporting higher APIs like 15 is not trivial.  And we don't really want to 
simultaneously support multiple branches of development.

Perhaps, if I'm successful with this attempt, it could be ready by the week's 
end.

Carl Nagle
SAS Research & Developpment
Planning, Operations and Strategy
General Applications and Tools
carl.nagle@sas.com

Original comment by carl.na...@sas.com on 13 Aug 2013 at 5:45

• Changed state: Accepted

[GoogleCodeExporter]

We are still working on this (along with other issues).  We have also received 
some external code related to fixes for this issue from Ferenc Lombai that we 
are evaluating.

Original comment by carl.na...@sas.com on 21 Aug 2013 at 7:23

[GoogleCodeExporter]

We are nearing the point where we can make the mods for backward compatibility 
to API 10 (2.3.3) available.  But I wanted to throw out some info to one or 
more folks in this category.

The TestRunners would still be built with API 15 support.  Meaning, they get 
built with the Android API 15 JARs (or higher).  But they could be run at older 
API levels like API 10.  Of course, features and functions that are NOT 
available on the device at API 10 will not work--but should not crash the 
application, either.

Original comment by carl.na...@sas.com on 22 Aug 2013 at 3:27

[GoogleCodeExporter]

Sounds great,it will be much easier to management. You guys are awesome. Thanks 
for updating.

Original comment by enduranc...@gmail.com on 22 Aug 2013 at 4:01

[GoogleCodeExporter]

Released 2013.09.09.

Original comment by carl.na...@sas.com on 31 Oct 2013 at 1:10

• Changed state: Fixed