H Haris Hafeez Active Member Licensed User Longtime User Jun 9, 2015 #1 Hi All, After updating to B4A, I'm not able to launch an app using Debug(Rapid) mode. The app crashes and doesn't launch and the IDE also shows an error message saying its unable to connect. Launching in other modes, Debug(Legacy) and Release works fine. Can someone shed some light and how to resolve this? Thanks.
Hi All, After updating to B4A, I'm not able to launch an app using Debug(Rapid) mode. The app crashes and doesn't launch and the IDE also shows an error message saying its unable to connect. Launching in other modes, Debug(Legacy) and Release works fine. Can someone shed some light and how to resolve this? Thanks.
Erel B4X founder Staff member Licensed User Longtime User Jun 9, 2015 #2 Can you try it with a real device? Upvote 0
H Haris Hafeez Active Member Licensed User Longtime User Jun 9, 2015 #3 Yes. It's the same result. An interesting fact here is that the Bridge does install the app and tries to launch it as well but the app launch fails because the IDE throws up the error message shown above. I'm using JDK 1.6.0_45(I know its old) and Android v22 jar. Upvote 0
Yes. It's the same result. An interesting fact here is that the Bridge does install the app and tries to launch it as well but the app launch fails because the IDE throws up the error message shown above. I'm using JDK 1.6.0_45(I know its old) and Android v22 jar.
Erel B4X founder Staff member Licensed User Longtime User Jun 9, 2015 #4 It is better to install and use a new version of Java (7 or 8). You can keep the old version as well if you like. Does it also happen with a new empty project? Upvote 0
It is better to install and use a new version of Java (7 or 8). You can keep the old version as well if you like. Does it also happen with a new empty project?
H Haris Hafeez Active Member Licensed User Longtime User Jun 9, 2015 #5 I am going to test this on my home machine and see if its a Java related issue. And yes, it does happen with an empty, new project as well. Upvote 0
I am going to test this on my home machine and see if its a Java related issue. And yes, it does happen with an empty, new project as well.
H Haris Hafeez Active Member Licensed User Longtime User Jun 11, 2015 #6 This only appears to be a problem with my work machine where I've got JDK1.6.x set up. The home machine has JDK1.7 and works fine with Debug(Rapid). Upvote 0
This only appears to be a problem with my work machine where I've got JDK1.6.x set up. The home machine has JDK1.7 and works fine with Debug(Rapid).
