LiveCode Forums.

that1guy wrote:So out of curiousity I installed LiveCode on a MacPro that is already setup for IOS development. I downloaded the Android SDK (left it in the downloads folder, and created the tools folder with the values from platform-tools).
Created a new key.
Tried to build a standalone app and I got the SAME error!

There was an error while saving the standalone application could not encode the class bundle.

This time the Virtual Devices does start an emulator when I click start.

Hope you are reporting these to support!

I know they are working on some Android fixes.

-- Mark

jclantonpboss wrote:Emulator is up and running fine. Now having same issue as That1Guy with getting LC to work with the Android Emulator or building Standalone Application on Windows 7. I keep getting the error 'Could not encode Class Bundle'.

Thanks in advance to anyone who has this one figured outl

I'm at the same point. One thought, a previous post mentioned you have to create a signing key. Does anyone have directions for doing that?

Thanks -- Mark

If anyone is still having trouble installing Android on the Mac to the point of selecting the Android SDK location from LC Preferences, email me offline at mark_smith at cpe.umanitoba.ca and I'll send you the directions I followed.

Cheers,

-- Mark

Ok, again kudos to Tech Support!

For the Windows 7 environment it turns out there is an issue with the jdk 1.7. If you uninstall 1.7 and switch to 1.6 jdk the problem is resolved in Windows.
But....
The same issue is still occurring on a new MacPro for Android development. Not sure why. The IOS setup is working just fine.
I ran java -version in Terminal and validated that it is using jdk 1.6. And I do have the keystore available.

that1guy wrote:Created a new key.

Brian, I forgot to ask earlier... where is the process documented for creating a new android key? (I just must have missed seeing it somehow)

Thanks

Glad to see you got it running on Windows... lets keep our fingers crossed for the Mac.

-- Mark

I used this to generate my key

Windows: START»CMD
$ keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -validity 10000

Windows: Mac: Terminal
$ keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -validity 10000

It is fairly straight forward. Just open a CMD window and navigated to your Java sdk folder then go one level lower to the bin folder.
The trick that they havent stated anywhere is that you get prompted to supply the alias and password when creating an Android standalone. Had no idea it would be important.
So to make it easier I made it the same as my key.
Just a helpful hint

that1guy wrote:The trick that they havent stated anywhere is that you get prompted to supply the alias and password when creating an Android standalone. Had no idea it would be important.
So to make it easier I made it the same as my key.
Just a helpful hint

Good to know (and I am always forgetting my damn pw's so good tip!)

Thanks

RunRev have 'fixed' the issue with having to have an Android Standalone key and trying to remember passwords etc.

In Standalone App Settings | Android | Signing | Sign for Development Only.

Then I don't have the distraction of having to have a key
and entering passowords everytime I build a standalone
until I want to start selling and distributing via the market, etc.

Not sure if its the same when developing on Apple OS.

hth

BarrySumpter wrote: In Standalone App Settings | Android | Signing | Sign for Development Only.
Not sure if its the same when developing on Apple OS.
hth

Hi Barry, it is the same (so I am not playing with the pw thing yet). Here's a screen shot of my IDE, Android and iPhone sims all running the same program at the same time. Now, if I had VMWare Fusion or Parallels running....

-- Mark

Yeah, I'm using vmWorkstation Win WinXp Pro to emulate me MBPro.
Works well.
Unless you leave it long enough to time out.

OK. You certainly cant say I dont give up easily. Tech Support again was fantastic and supplied a different dx file to go in the tools folder. Well I am fairly new to macs and no matter how I tried to download it the file came down as a shell program. Removing the file extension didnt help and I could not force it to run as an application.
Soooooo
I went to the Android3->Tools folder. Copied the DX file out of there and placed it in the Android8->tools folder.
And it was able to compile.
Have I've been doing development so long that this kind of installation didnt even phase me?? I know plenty of other people who would have thrown their systems in the garbage by now.
HA!

that1guy wrote:OK. You certainly cant say I dont give up easily. Tech Support again was fantastic and supplied a different dx file to go in the tools folder. Well I am fairly new to macs and no matter how I tried to download it the file came down as a shell program. Removing the file extension didnt help and I could not force it to run as an application.
Soooooo
I went to the Android3->Tools folder. Copied the DX file out of there and placed it in the Android8->tools folder.
And it was able to compile.
Have I've been doing development so long that this kind of installation didnt even phase me?? I know plenty of other people who would have thrown their systems in the garbage by now.
HA!

That1guy... how come your signature line says you are developing on Dell/Windows 7 and you're fooling with macs But you win the prize for perseverance Who would have thought that would work? There is a thread at this location http://forums.runrev.com/viewtopic.php?f=53&t=8789 that may be helpful in the future dealing with installing Mac files (at least ones that need to be chmod'ed)

Good work and congrats for getting it working. Now you can spend your time writing some real software

that1guy wrote:OK. You certainly cant say I dont give up easily. Tech Support again was fantastic and supplied a different dx file to go in the tools folder. Well I am fairly new to macs and no matter how I tried to download it the file came down as a shell program. Removing the file extension didnt help and I could not force it to run as an application.
Soooooo
I went to the Android3->Tools folder. Copied the DX file out of there and placed it in the Android8->tools folder.
And it was able to compile.
Have I've been doing development so long that this kind of installation didnt even phase me?? I know plenty of other people who would have thrown their systems in the garbage by now.
HA!

Finally this way works for me too. I sent an email to Tech Support and they responded very fast with the above mentioned dx file. After changing the file rights to make it executable the Android emulator and compiling for Android is running well now.

Yes, these instructions worked - move the tools in the SDK, move the dx file from Android-3 to 8, etc. A little distressing that only dedicated hackers can make this work.

For a tool marketed for it's easy of entry, THIS IS RIDICULOUS. Five plus hours wasted just trying to get this to work...and it still doesn't! And why do I have to scour the web to learn about this problem when important issues like should appear on LC's start screen & give me a link to fix it!?!?!

I've followed the suggestions (make a self-signed cert, copy platform-tools into android-8 folder*, copy the android-3 dx file into the android-8 tools, downloaded the DX file from another post & make it executable....argh!!!!) but LC fails to find the JDK Path & won't test because it "could not compile application class".

I'm running OSX 10.5.8 with java version "1.5.0_30". (And btw, the original dx fails upon execution because it can't find the dx.jar file. With android-3 & the rev supplied dx, it does find the lib/dx.jar file & is executing properly.)

So I'm still dead in the water & utterly frustrated. Any more suggestions? Sorry for the rant, & TIA!!!


* Be sure to copy, not move, the platform-tools folder. If you move it, you will get the "not a valid android sdk" error.