"Installing file to device. Error" when compile

[AntAnt]

Hi there, first days working with Basic4Android and my first projects work fine with a device (an android smartphone).
When I try to compile/run using the emulator (by AVDmanager) it doesnt work and I have the "Installing file to device. Error" message.
Withing the same basic4android projects I can open "designer" and log the emulator: it works.

I'm working with android api 14

My "configure paths"
- C:\Programmi\Java\jdk1.7.0_25\bin\javac.exe
- C:\android\platforms\android-14\android.jar
- (no additional libreries path)

Did somone have a similar issue or anyhow knows what could I try to fix it? Thanks in advance

A.B.

 

[Erel]

Try to delete this AVD (emulator instance) and create a new one.

I recommend you to use a real device instead of the emulator...

 

[AntAnt]

Hi Erel, thanks for your msg. I finally found out the issue.
It was stupid thing.. but got me stuck sighs. I just had to increase the timeout (from Tools/Ide Options).
I had 30 seconds and it was not enough.
The compiler tricked me as it asked "wanna stop or going ahead" and I thought it could work just picking to go ahead, but that way (after a while) I kept to have the "installing file device error".
Now I have 10 minutes/timeout and it works. Wonder if there's a sort of bug about the "retry" option after a timeout.
Thanks again.

 

[pere]

Hi there,
I've the same issue as AntAnt explain. This happens randomly also using real device via B4A-Bridge. With the timeout to 120 seconds improves ratio.
When works the next big issue is the device screen message: "Unfortunately, PROGRAMM_NAME has stopped"
I have now a new icon on the device screen. Each time I'm trying to run the App this message appears. Only an OK button to close the popup.
Same situation if I use a real device but not using b4A-Bridge. I mean directly for USB.
My first application still works fine and recompile well each time but this second app started from the beginning fails.
Also, a copy to a new directory of the working first App, with only the icon and "Package name" changed, still the same message: "Unfortunately, PROGRAMM_NAME has stopped" popup failure.

What may I do?

Thanks all

 

[Erel]

You should check the logs and find the error message.

 

[pere]

Please see attached screen capture of my log.
Now with more concrete situation: is the same B4A code but in different directory of the same PC. One reports logs (OK) and when fail (Unfortunately Stops) there are no logs.

Hope this helps!

Thanks.

 

[Erel]

Errors of non-b4a apps will appear in the unfiltered logs. The most common cause of such errors is an invalid icon file or a very large file. Try to change the icon.