My experince trying to port Corona iPhone app to Android

@MBD

I would be grateful if you could try and download my app from this URL http://market.android.com/search?q=pname:uk.co.garysims.android.thunderclap

Please tell if the download works and what version of Android you are using (as on my 1.6 device I can’t download my app from the Market).

Much appreciated!

Gary
PS. With regards to signing, I just used the keytool as described in the documentation and it worked first time with no problem. Sorry I can’t add any more light… [import]uid: 4415 topic_id: 1398 reply_id: 6282[/import]

Downloaded and installed just fine Gary.

Nexus one, Froyo 2.2

[import]uid: 9046 topic_id: 1398 reply_id: 6283[/import]

Can’t find your app on the market.

G1 with 1.6 on it. [import]uid: 5712 topic_id: 1398 reply_id: 6289[/import]

@MBD, @MikeHart

Many thanks to both of you… So this has confirmed by suspicion… The app was built for 1.6 using Corona 2.0 and does indeed work on 1.6 (if you download and install the pkg from http://android.garysims.co.uk ). But in the market place it is only showing up for 2.x (I guess, MBD used 2.2).

Any comments anyone? Any ideas?

Is it possible that somehow the package is marked for 2.x… How do I check?

Thanks,

Gary [import]uid: 4415 topic_id: 1398 reply_id: 6299[/import]

Unfortunately I have one - you might need to stop using the Corona SDK until they get it right for Android. My one and only app I built using Corona (lua) works fine on iphone, and device testing android, but I’ve got all sorts of issues getting the app into the Google marketplace as well. I can make, test, and sign my same app using the regular Google SDK in a matter of hours but it took me two days using Corona and it’s still not published.

Corona team:
I’m a fan! Really! I like what you are doing here!
But the cross development platform plays much nicer with an iphone than it does an Android. I think you guys either need to focus more on the Android side and beef it up as solid as the iphone side, or have a way where we can use the Corona SDK outside of the Corona emulator. That way we can build, test, and release using a dedicated GUI such as eclipse.

I simply can’t waste a bunch of time pouring over a document you published and following protocol, only to have the app give me fits in the end.

Our goal when purchasing the license was to have a dual platform solution that had a unified language, but so far I have to give Corona a 2 out of 5 stars.
Richard [import]uid: 9046 topic_id: 1398 reply_id: 6309[/import]

Richard, you’re the only person reporting this problem, and we have not seen it in our internal testing. We also suggested a workaround which is to re-sign manually, while this is not ideal it will allow you to publish.

Android documentation is no picnic to decipher, and there are a huge number of bugs and workarounds we’ve fixed over the last few weeks that are due to problems in the OS. Couple that with the large number of devices to test on, and to add to the fun, there are also differences and bugs in specific devices. I’m not trying to make an excuse here; I’m just pointing out that what we’re doing is not easy.

Rest assured we’re working to resolve your issue. [import]uid: 54 topic_id: 1398 reply_id: 6313[/import]

@garysims, we add the following to AndroidManifest.xml:


Where version is set according to the SDK specified at build time. So if you picked 1.6, we set the version to 4. The second line specifies OpenGL ES 1.1, which should be available in all 1.6 and higher devices.

Android market filters are documented here:

http://developer.android.com/guide/appendix/market-filters.html

An app built for 2.0 or 2.2 will not install on a 1.6 phone. So if you are able to install it, then it was built for 1.6, and the problem is in the market filters.

We’ll continue to look into this. [import]uid: 54 topic_id: 1398 reply_id: 6315[/import]

It appears you’re not the only one having problems with market filtering:

http://www.google.mw/support/forum/p/Android+Market/thread?tid=2156a1d8ddb8ba47&hl=en&start=120

[import]uid: 54 topic_id: 1398 reply_id: 6316[/import]

Hi Eric,

did you read in your posted link what Jerry Brady posted on 07/21/10 about the permission settings? Could that be the case why 1.6 SDK Corona apps don’t show up with 1.6 devices anymore?

Michael [import]uid: 5712 topic_id: 1398 reply_id: 6325[/import]

I was able to finally get an app signed with my private key - only after I created a new one with a less secure password. My original key that worked fine in Eclipse and the android SDK used a “strong” password with special characters, uppercase and lowercase characters and a few numbers. After talking more with Eric I realized that more than likely the Corona SDK didn’t like the strong password.

This could come back and bite you guys so until Corona fixes it, make sure you are using a keystore password that has little to no special characters in it.

Now I’m fighting the icon issue and hopefully will have a Corona app in the marketplace by sundown!

Richard

[import]uid: 9046 topic_id: 1398 reply_id: 6330[/import]

@MBD, what is the “icon issue”? [import]uid: 54 topic_id: 1398 reply_id: 6333[/import]

@TheGiant, regarding your earlier comment “if i use “zoomEven” the fishies will not hit the edge of the screen”, this is probably because of the way dynamic content scaling works. This scaling mode maps a content rectangle (such as 320x480) into the display, maintaining aspect ratio, which means if the display is a different aspect ratio there are some pixels in it that aren’t mapped from the content area. What happens then depends on the code – and fishies moves the fish within the original content area. [import]uid: 54 topic_id: 1398 reply_id: 6334[/import]

@ MikeHart, I’m trying to find what “Jerry Brady posted on 07/21/10 about the permission settings”. Can you find it by any chance?

[import]uid: 54 topic_id: 1398 reply_id: 6336[/import]

If only your selfmade forum software here had a quoting functionality. This is what here wrote:
In the end, we had the existing “android:required=false” parameter set in our manifest, but what caused our market issues was the failure to include “android:required=false” to every other permission we had in our manifest that wasn’t available before API level 5.

For us those were: android.permission.AUTHENTICATE_ACCOUNTS and android.permission.MANAGE_ACCOUNTS.

So, my recommendation for anyone having trouble is to carefully audit the hardware features you need and your manifest permissions and ensure you are explicit about how you define them. [import]uid: 5712 topic_id: 1398 reply_id: 6341[/import]

Hi everyone!

I’m actually developing a little app for Android-Devices. Like you showed above, I’m preloading all sounds and I’m using
ogg’s.

I’ve tried several times and I’m always getting the same error in the terminal after this line of code:

local test = media.newEventSound( “test.ogg” )

I’m getting this error : WARNING: Mac error(-1500) while creating event sound for file(/Users/…/Desktop/…/test.ogg)
WARNING: Failed to create event sound(test.ogg)

The ogg sound file is exactly in the folder of my app and has the name “test.ogg”. The sound file is not damaged or something, i played it in iTunes and VLC.
What should I do? Is there a problem with the ogg’s and my mac?

Thanks for your help.
[import]uid: 8154 topic_id: 1398 reply_id: 8387[/import]

@Ultima94, sorry for the slow response. OGG is an Android-only format. It is not supported on iOS or Mac at this point. We are looking into ways to support this and other cross-platform formats. See the AudioPlayer sample code for an example of how to support different platforms. [import]uid: 54 topic_id: 1398 reply_id: 9400[/import]

I am trying to find out if the resume issue has been addressed. You mentioned The resume issue is FB#269

How do I find out if this has been resolved in the latest build? [import]uid: 2949 topic_id: 1398 reply_id: 53793[/import]

Wow this is a really old thread. According to FB, 269 was resolved over a year ago.
[import]uid: 7563 topic_id: 1398 reply_id: 53819[/import]