That would likely be on the Apple side of things.
Rob
That would likely be on the Apple side of things.
Rob
That’s what I suspected. Thanks.
MAS1
The tracking in the iAds dashboard is working ok now as well? We’re still waiting for our last update to go through, will let you know how we get on…
Yes - the dashboard tracking is working.
Caveat - one time when testing (this was an adhoc build right before uploading to Apple) an iAd banner did not respond to clicking. It only happened the one time and I couldn’t reproduce it. I doubt very much the error was in my code - the plugin more likely. For anyone using iAds I recommend testing thoroughly!
I have RevMob and Vungle and when performing the adhoc build testing I tapped the iAd banner at startup, either side of app suspension and either side of RevMob and Vungle ads (where I hide then show the banner).
I also had a good old test on live iAd banners and the “tap and nothing happens” problem did not occur. I didn’t do too much of this testing on the live iAds in case it flagged up as fraudulent at Apple’s end!
Good luck!
MAS!
In answer to the question about whether plugins are tied to daily builds, the answer is that they are not. I confirmed this in an email chain with Walter and David a few months ago. It’s also alluded to in this blog post (last paragraph of point #4): http://www.coronalabs.com/blog/2013/09/25/wednesday-faqs-using-corona-plugins/. Regardless of what daily build you’re using, you’ll always get the latest plugin. As we’ve seen on this thread, this creates a very dangerous situation for developers, where plugins can be (and are being) updated without us knowing, potentially introducing bugs. The worst would be if a plugin happens to be updated and introduce a bug right between your final developer build and your release build!
When speaking with Walter and David, they acknowledged this was a risk and mentioned they’d look into publishing some sort of release notes when plugins are updated. At least, then, we’d have some visibility into what might need to be retested.
Andrew,
Thanks for taking the time to post that information - very illuminating. And yes, rather worrying not being able to “roll back” to a previous plugin that is known to work. Thanks again.
MAS1
FYI, I’ve just emailed Walter and David and asked them specifically to reply on this thread to clarify the situation.
(I should also mention that I started experiencing the exact same iAds issue as has been described on this thread.)
Andrew - yes we agree that it is very dangerous to not have any version control for plugins - as you say one minute everything may be working fine then when you make the final build to submit something breaks - then unfortunately you don’t know it is broken until 4-5 days later once that version has been approved and is live in the store! Not ideal.
In our case this has been very costly - for more than 10 days now we have been running our two main aps with no working ads just after we ran a major promotion on them.
We have lost around $10-15k because of this issue so far and I’m sure we are not the only ones so this is a really serious issue from our point of view.
Hi guys - we are aware of these issues. So 2 points/questions:
I understand that the issue should be fixed with the latest version of the plugin. But can anyone here confirm that you are still seeing the issue?
We are working on a way to have release notes for plugins. That is a first step towards making the overall system more robust.
Hi David, thanks for joining the thread.
On (1), I’m still experiencing the issue where the first iAd banner always displays at the top of the screen, regardless of the parameters passed to ads.show(). Subsequent banners display in the right position. I’m using Daily Build 1227, and I just did the build a few minutes ago.
On (2), I think I speak for everyone when I say that release notes for plugins would be a tremendous help to the community.
I am also still experiencing the same issues as Andrew where the first iAd banner shows at the top of the screen and then all subsequent iAd banner requests display in their correct position (bottom of the screen for me). I am using Daily Build 1228 and just tried as a couple minutes ago.
Thanks,
-Clark
David, dchan, it would be helpful to know whether you acknowledge and can reproduce the bug we’ve been describing (first iAd banner placement always appears at the top of the screen, regardless of the coordinates passed to ads.show(); subsequent banners are positioned correctly), and when we can expect the fix to be available.
One of us can submit a bug report if need be, but since a number of us are reporting the same issue, it should be clear that the bug exists and is easy to reproduce.
Last, if possible, it would be helpful to know what the purpose of the changes to the plugin were and whether there’s any possibility of rolling back to the previous version.
Thanks.
Guys - Danny will be looking at this in the next couple of days. He is currently working on something else that has priority over this, but we will try to get to this asap.
Thanks David for providing some clarity on the timing. Of course, I’ll just reemphasize that this is essentially a showstopper issue for any developer in the community releasing an app with iAds banners, so (I hope) it should be considered a rather high priority.
Agreed, this is pretty much a top priority for us when we have lost nearly two weeks of earnings for an issue that was essentially out of our control.
Although perhaps not ideal I have posted a fix (in this thread) for the “1st iAd banner appears at the top when it should be at the bottom” problem.
MAS1
Hey,
Can one if you guys post a complete project with the build.settings, config.lua, and main.lua where the iAds banner shows up at the top of the screen? I am unable to recreate it with my test case. Also please post the device you’re running it on and the build of Corona you’re using. Thanks.
Thanks Danny. I’m isolating it into a simple complete project now and will post something shortly.
Hi Danny,
Here is a simple project exhibiting the bug. Through experimentation, I was actually able to find that the bug is a bit more interesting. Specifically, it appears that, on the first banner display, the ad is aligned so that the top is equal to y value provided in ads.show(). Subsequent displays align the ad so that the bottom is equal to the y value provided.
build.settings:
settings = { orientation = { default = "portrait", content = "portrait", supported = { "portrait" }, }, plugins = { ["CoronaProvider.ads.iads"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone = true } } } }
main.lua
-- Load the ads module local ads = require("ads") -- Display a red background so it's easier to see the display area edges on an iPhone 5 if we're not using a tall launch image local bkg = display.newRect(0,0,display.contentWidth,display.contentHeight) bkg:setFillColor(64,0,0) -- Initialize iAds with a callback that dumps the ad events to the console local callback = function(event) for k,v in pairs(event) do print(k,v) end end ads.init( "iads", "com.company.appname", callback ) -- Experiment with different values for y local y = display.contentHeight -- Create a small circle centered at this y so we can compare to where the banner is displayed display.newCircle(display.contentWidth/2, y, 20) local showBanner = function() print("Attempting to display banner") ads.show( "banner", { x=0, y=y } ) end -- Set the provider to iAds ads:setCurrentProvider("iads") -- Show the first banner showBanner() -- Every 10 seconds, hide the banner and display it again timer.performWithDelay(10000, function() print("Hiding banner") ads.hide() timer.performWithDelay(1000, function() showBanner() end) end, -1 )
There is no need for a config.lua to exhibit the bug.
I built this project using Daily Build 1227 and ran it on an iPhone 5 running iOS 7.0.4.
If you run the code exactly as above (just replace the bundleID in ads.init()), you’ll see the first banner display on top and subsequent banners display on the bottom. If you change it so that y=300 or 500, you’ll see that the first banner is aligned with the top at y=300 or 500, and subsequent banners are aligned with the bottom at y=300 or 500.
Let me know if you’re able to reproduce the bug using this code.
Thanks.
Yes I can reproduce this issue thanks. While working on this you can try using Mas1’s hack to work around the issue.