Hi Peach,
I got another Bug … now with Inneractive on Galaxy Nexus.
http://www.2t4u.com/images/ia_bug_ansca1.jpg
On Nexus ONE the Ad Size seems OK
on Galaxy Nexus… too small.
Have to mention (forgot in the Bug report, still can’t change my text there)
the config.lua for that app defines a width = 768 and height = 1024 !!
Anything I can do about.
Filled also new Bug Report: #11691_8id1k08s on bug.anscamobile.com
greets
chris
[import]uid: 4795 topic_id: 20767 reply_id: 320767[/import]
Also UPDATE to my previous reported bug.
Default.png on Android .
They Delay till to place showAd() with a interactive Ad needs even to b
2 Seconds, not just 1 second… otherwise the app crash!
[import]uid: 4795 topic_id: 20767 reply_id: 81678[/import]
You are defining your screen to be larger than your target device, which was not the intent of the width and height values in config.lua and may produce unexpected results.
The config.lua parameters were design to scale up a screen to fit a larger device and that is how it’s tested. Normally you set width = 320 and height = 480 and Corona will scale up the display objects to fit a larger screen.
Designing your app for a larger screen and expecting it to work on a smaller screen is not something that was intended or even tested. We need to look and see if that can be supported.
Things like this are very hard to test for since their are hundreds of devices and thousands of API combinations that can cause things like this to occur. If you file a bug report with a test project demonstrating the problem, we will look at the issue and see what can be done to resolve the issue.
[import]uid: 7559 topic_id: 20767 reply_id: 81722[/import]
I was just reading that corona does auto fit the Size, based on the data set in config.lua
Also there was several other user demos with higher resolutions.
Anyhow, it made sense for me, that it may slow down the app a bit, when i set a higher Resolution in the beginning, but I could live with it and did not had to handle with lots of different ImageSizes (what finally even made the app smaller)…
also it worked till now without exception (that does speak for you) 
Its only for that one feature (InnerActive Ads) where I did not found a solution.
Should u still need a Source , let me know and I have to create one.
Otherwise, its just some 768x1024 in the config.lua and a a standard interactive Banner called.
[import]uid: 4795 topic_id: 20767 reply_id: 81729[/import]
If I have two cases to work on and one has an included project that demonstrates the problem and the other one doesn’t, guess which one I’m going to test?
Besides, I’ve had two many cases where the user said just do this and this and you will see the problem, and I didn’t see the problem. [import]uid: 7559 topic_id: 20767 reply_id: 81730[/import]
hi tom…
just in the meantime… could u reproduce the problem.
If not… no problem I will create a InnerActive demo and include a config with
768x1024. I am just as you also very busy… and keep prio focusing on my own bugs that my users report me (most time without any source
greets
chris
[import]uid: 4795 topic_id: 20767 reply_id: 83173[/import]