You shouldn’t call chartboost.show() immediately after the chartboost.cache() call. If you do, you don’t give a chance for the listener to be called and you have no idea if an ad has been cached or not. You have to wait a while before calling show().
As a rule you’d call chartboost.cache() at the start/resume of the app, and when you reach a point in your code where you want to display an ad, you check if an ad is cached and only then call show() if there is one available.
Thanks for taking the time to leave a detailed reply. Looks like I’ll just have to try it and do some logging with analytics. I guess I got spoiled by admob, showing ads all the time. 
I implemented changes suggested by ingemar. Interstitials are showing up fine now, but I’m still having problems with more apps
I can select my own apps, but “Autofill with network advertising” is not working.
Any caching attempts result an error message in the logs
“Could not successfully update network info during initialization”
Immediately followed by a failed load event
phase=load
type=moreApps
name=chartboost
result=failed
Had similar issues, I made sure I created a campaign for more apps and added the ‘Campaign’ to the app Publisher MoreApps Settings (where you auto fill) under ‘Included Apps and Campaigns’
It’s not very intuitive, but it’s working now, I also was able to select which app genres and apps to block (like candy crush, casino, ect… that aren’t geared to my audience)
I believe @Ernest is correct regarding the Autofill issue.
About caching:
Are you by any chance caching interstitials and moreApps in very close succession? I recall having an issue where if I tried caching the two too close to together I’d get caching issues. Now I wait for 2 seconds between the cache() calls and I haven’t had any issues after that.
Hey guys sorry for the late reply.
Just wanted to weigh in on a few things.
Naturally we have no control over how Chartboost’s dashboard works, or if you have done all of the required steps to get your app properly set up on the Chartboost dashboard. This is a requirement to get your ads and such showing properly.
This is speculation, but I believe the more apps option of “fill from networK” will no longer work, as Apple has made it clear that they will not allow apps to promote other companies/peoples apps within your own. It probably should still work for android though, but we haven’t released the Android version just yet.
The Android version will be released next week, for definite. Barring no acts of god. It’s more or less there, just needs more testing and some spit and polish 
When the Android version launches, the new functions of hasCachedInterstital() and hasCachedMoreApps() will be available, meaning you can ensure that an ad is cached before attempting to show it, without having to rely on the callback, if you so wish.
Thanks
Please read the documentation here: http://gremlininteractive.com/corona-plugins-documentation/chartboost_plugin_corona_docs/
That is not the correct usage. You should ensure that the Ad is cached (via the callback event), and after set a boolean flag, before attempting to show the Ad. In the next release you will be able to call helper functions to check for an Ads cached availability.
“Caching” (in this context) means that it must first download the Ad (image(s)) along with it’s relevant metadata, in order to become “cached”.
Naturally it can’t always do this instantaneously (depends on network connection speed) so putting the cache() and show() calls right next to either other is pointless, as it won’t give you the results you are after (because the ad won’t be cached, so the call to show() will have to download the Ad+data again, in theory, making the Ad take even longer to show).
You have to wait for the Ad to “cache” before trying to show it.
Great I can’t wait to use it on my Android game!
Moreapps is working fine now. Thanks everyone!
Glad to hear it!
@all. Sorry that the plugin didn’t get released for Android last week as promised, however, it will be released on Monday.
Thanks
I am planning on doing an update today on my Android game so that is perfect timing! :lol:
I have a question.
Where Do I have to set up the charboost init.
In the main.lua.?
in the menu.lua?
in the game,lua?
local chartboost = require( “plugin.chartboost” );
–The ChartBoost listener function
local function chartBoostListener( event )
for k, v in pairs( event ) do
print( k, “:”, v )
end
end
– Your ChartBoost app id
local yourAppID = “sfsfsfsfffffffffffffsf”;
– Your ChartBoost app signature
local yourAppSignature = “fsfsfsfsfsfsssssssssssssss”;
chartboost.init(
{
licenseKey = “ccccccccccccccccccccccc”,
testMode = false,
appID = yourAppID,
appSignature = yourAppSignature,
listener = chartBoostListener ,
}
);
The plugin is out now. It was out yesterday but I didn’t get chance to announce it.
You can call chartboost.init() wherever you like, but it’s important to only call it once per app start. You can of course call it again if it couldn’t connect first time due to any network errors (lack of connectivity etc)
Can I use the plugin with Amazon?
Yes. We have also updated our store entry and Chartboost docs to reflect this.
Thanks
I need some help, beacuse using my Android device I get a “failed” result every time I try to show something.
Using the sample code from GitHub, I get a valid login.
status: valid
type: check
name: license
But when I try to show an ad:
phase:load
type: interstitial
name: chartboost
result:failed
It doesn’t matter if I set to true testMode or not, I only get a failed response.
Anyone knows what could be going on? :unsure:
I do.
As said before, it is extremely important to have your Chartboost dashboard configured correctly.
In a nutshell, you need to follow these steps:
So you should do something like this:
-- Your ChartBoost app id local yourAppID = "your\_app\_id\_here\_for\_ios"; -- Your ChartBoost app signature local yourAppSignature = "your\_app\_sig\_here\_for\_ios"; -- Change the appid/sig for android (required by Chartboost) if system.getInfo( "platformName" ) == "Android" then yourAppID = "your\_app\_id\_here\_for\_android"; yourAppSignature = "your\_app\_sig\_here\_for\_android"; end
Add a test device (Android in this case) to your test devices section in the Chartboost dashboard.
Create a publishing campaign.
Add the test device (that you previously added in step 2) to a device list (via csv file) here: https://dashboard.chartboost.com/companies/device-lists
Add the device list to the campaigns “inclusion” section near the bottom of the campaign form.
You should now see consistent ads, provided everything was done correctly.
These instructions apply to iOS and Android. Completing them all for both platforms ensures that you will get the best possible testing experience.
Cheers
Yeah Gremlin that was it, I had the app added to my dashboard, BUT I didn’t created a campaign for it. :wacko:
It is not complicated, but it is easy to overlook a step and consequently lose some time trying to get it fixed. 
My feedback for you is that you should copy&paste your previous post inside the plugin documentation for newbies like me. Or simply just copy&paste the short version; the one yourself wrote here on a previous page of this thread:
- Please make sure you have added your iOS device to the Chartboost portal, otherwise ads may not show: https://dashboard.chartboost.com/companies/test-devices
- Please make sure you have set up a publishing campaign for your app, or ads may not show. https://dashboard.chartboost.com/campaigns/publishing
Thank you for the awesome support, I couldn’t be happier of my purchase! :lol:
No problem, glad to help
I agree that this would save me time to add this to the docs, I just haven’t found the time to do that yet…
it’s on my todo list however.
Cheers.
Just testing the new chartboost plugin on Android some things I noticed
chartboost.hasCachedInterstitial() returns a function not a bool and I still fail to load the interstitial if it’s not loaded
also I noticed when the interstials were working (they stopped working a moment ago for some unknown reason when more apps started to work) When they animate out they have very sharp angles, coming almost straight out of the viewport and not looking as good as in the lua SDK or iOS version.
will test on iOS soon, I hope it’s not broken on there either