Could I get some help with successfully deploying to Android?

I don’t know to be honest. I simply tried to export the Card sample to Android and it blew on this line: “RunUAT.bat ERROR: AutomationTool was unable to run successfully” (same as above)

Then I created a completely empty project (after I posted the comment) and that didn’t work. After that I added a path reference to “platform-tools”, and that seemed to do the trick. All Environment variables etc… are correct so I am unsure why that helped. Then I also had to activate the devmode on my Galaxy S4+ (GT-9506) (but that is another topic) and fixed the VendorID in “adb_usb.ini”, and restarted the adb service just to get it on the phone. But that is yet another topic :slight_smile: but maybe those two points could be mentioned in the docs, could save some people a bit of time.

Anyway, it seems the project need to be created in a certain way, in order for it to be exportable to Android. I just don’t know what those criterias are (yet) because you can’t just take any project and export. Secondly, and perhaps more important, is that no exported Project seems to work properly. None of them start at once, I have to repeatedly press the name on the program and maybe it starts. Most of the time it starts a process in the background and switch back to the normal screen. And it doesn’t matter what I try to export. It all behaves the same way. Even Tappy Bird behaves like this. But perhaps you are already aware of that issue?

But my digression aside :slight_smile: the export works now.

Hmm, needing to add platform-tools into your path is definitely a bug, but I can’t find anywhere in the code that runs adb without a full path :frowning:

As for your device, I mention making sure that “adb devices” shows your device, as that is what we use to find the device. Every device is different with different drivers - we can’t document what you need to do for your particular one to make the PC be able to talk to it.

You should be able to take any project and Package or One Click Deploy to Android (it may crash from memory or whatever, but should never fail to package it up). In which case “adb logcat” or other Android tools can get the log, and then you can report those errors :slight_smile:

So, basically, no, we aren’t aware of the issues you are having…

Josh