Ben,
That information was a big help. I just tried it on a Galaxy Nexus 4.0.2 and was able to reproduce the issue. Now, inneractive told me that their newest SDK does in fact work on Android 4.x devices, so I’ll give the newest SDK a go next week. [import]uid: 32256 topic_id: 23577 reply_id: 103579[/import]
Hi Joshua,
Could you add the updated InMobi SDK too. There’s a newer version of that as well. Hopefully these new updates will improve Fill Rates too. [import]uid: 38820 topic_id: 23577 reply_id: 103697[/import]
Tried CoronaSDK build 2012.797. I don’t get a black box anymore. Now it works but there is a extra long white filled rectangle and it crashes when I hit the power button. Meh… [import]uid: 38820 topic_id: 23577 reply_id: 103897[/import]
We haven’t done anything we inneractive on Android yet. Are you referring to iOS? [import]uid: 32256 topic_id: 23577 reply_id: 104055[/import]
I didn’t see it said iOS. I just looked quick and tried the build last night. I just looked again now and noticed you’re right it’s for iOS. whoops my bad. LOL [import]uid: 38820 topic_id: 23577 reply_id: 104067[/import]
No worries. The inneractive iOS update takes care of the UDID issue and I think it has media ad support. The new inneractive SDK should support media ads too.
I’m also expecting another inneractive SDK update sometime in May that will address a device ID issue that Amazon has been known to reject apps for. [import]uid: 32256 topic_id: 23577 reply_id: 104080[/import]
Bump [import]uid: 38820 topic_id: 23577 reply_id: 105278[/import]
If you are “bumping” for a status report, then here it is. We’ve integrated the newest inneractive SDK for Android and it still has this issue on Android 4.x. We’re currently working with inneractive to resolve this issue. [import]uid: 32256 topic_id: 23577 reply_id: 105332[/import]
Hi Joshua,
Not sure it is related or not, but I have seen specific display issues (position problems and white box backgrounds) when trying to use native.showWebPopup on apps when they are built with the Windows version (late versions). The same code works fine when built with the Mac version.
This reared it’s head while looking at the Lunar Ads. Their sample app had the issue, which they could not see. They sent me an apk to test and the problem is not there, but when I build the code on Windows the web popup is out of place and white boxes appear.
It looks like a suspiciously similar problem.
Ben [import]uid: 28534 topic_id: 23577 reply_id: 105438[/import]
Hi Ben,
I tried displaying native display objects such as a TextField, TextBox, and WebPopup on the same Android 4.0.3 device and I didn’t see any display issues. Were you seeing this in Corona or some other SDK such as with Lunar Ads? [import]uid: 32256 topic_id: 23577 reply_id: 105530[/import]
Hi Joshua,
Yes it is using the standard sample app code that Lunar Adds provides. As far as I can see it is just standard Corona Lua code.
The position problem comes about when you attempt to use specified positions rather than the default.
Halign = “center”,
Valign = “top”,
For example using instead:
x = 0,
y = 0,
Both the above will still show unwanted white box areas though.
Doing it this way will compile and run fine if it was built with the Mac version but it will not do the right thing if compiled with the Windows version of Corona.
Perhaps it would be a good idea to grab the Lunar sample so you have a code sample that shows this different Mac v Windows build behaviour. [import]uid: 28534 topic_id: 23577 reply_id: 105617[/import]
Back to the original topic, we’ve found a show stopper issue in the newest inneractive SDK that is currently preventing us from integrating into Corona. So, we’ll have to continue to use the old version until that is resolved.
That said, we did find a solution for the graphics glitches that occur on Android 4.x devices. It turns out that hardware accelerated rendering for Web Views, which is what the inneractive ad banners are made of, have known issues on Android 4.x and the work-around is to revert to software rendering… which is the default for older versions of Android OSes. We will go ahead and make that change later this week. Don’t worry, the rest of the Corona app will still be hardware accelerated. [import]uid: 32256 topic_id: 23577 reply_id: 105632[/import]
Ben,
Would you mind sending us a bug report in regards to your Lunar Ads issue please? You can do so by clicking the “Report a Bug” link at the top of this web page.
I’m thinking the issue that you are mentioning is unrelated to the inneractive ad issue. I say this because you site different app behaviors if you build on Windows compared to Mac. What’s interesting is that the app build is actually done on our servers, which are Linux, and not on your local machine… so I’m thinking the issue here is that this is a text encoding problem in your Lua files. That’s a common issue when people use Window’s Notepad for editing Lua files because that application likes to add a BOM (Byte Order Mark) to the head of the file which really screws up the Lua interpreter. In any case, we can discuss this further via the bug report and work on resolving the issue. Thanks! [import]uid: 32256 topic_id: 23577 reply_id: 105633[/import]
Hi Joshua,
I posted the bug report Case 14164.
However, I have just received a reply email from Corona support saying that support would NOT be make because the problem manifests in a 3rd party tool/service. Really? Why did you ask me file a bug report?
This is just basic Corona lua code and more importantly it is a difference in behaviour from a Corona Windows build v a Corona Mac build.
It is also the same erratic white box behaviour seen with Inneractive.
I sure hope you are providing support for Richard at moonbeam who is trying to fix the problem with Corona Windows v Mac builds.
Ben
[import]uid: 28534 topic_id: 23577 reply_id: 105793[/import]
Everyone,
The inneractive Android 4.0 graphics glitches issue is now fixed and the fix will be made available in daily build #811 tomorrow. This also fixes the fullscreen ad issue where it was not being displayed fullscreen. [import]uid: 32256 topic_id: 23577 reply_id: 105828[/import]
Ben,
Your bug report never made it to my inbox. I looked at the bug report just now (thanks for giving me the case number) and yeah, you did make it sound like a 3rd party Lua library issue instead of a Corona issue. I’ll re-open it and we can discuss it from there. Thanks! [import]uid: 32256 topic_id: 23577 reply_id: 105829[/import]
Hi Joshua,
Update:
Post was removed as it was installing over the top that did not update correctly.
Seems ok now.
Ben [import]uid: 28534 topic_id: 23577 reply_id: 105977[/import]
Hi Joshua & anyone else with the same issue.
The latest daily (819)has now fixed the white box issue with Windows builds Case 14164.
Thanks,
Ben [import]uid: 28534 topic_id: 23577 reply_id: 107816[/import]
Everyone,
The newest daily build fixed a web popup rendering issue on Android 4.x devices. It turned out to be the same issue that was affecting inneractive ad banners, which uses web views to display ads. So, thanks to everyone for notifying us of this issue and helping us isolate it. It helps make Corona a better product for you and everyone else too. [import]uid: 32256 topic_id: 23577 reply_id: 107948[/import]