Thanks Rob.
Yes, keeping google.play.services in there was an oversight on my part. I guess it was the fact that AdMob is not actually listed in the list of their mediation partners that made me wonder and decide to test it.
In the end, AppoDeal seems so problematic on several fronts that I’m probably not going to test it any further (or be able to use it).
One of the problems is one that neither you nor I can “fix”. In fact, you addressed it in a different forum post. Including the single AppoDeal plugin adds 30.9 Mb to my app’s file size. A popular app of ours jumps from 78.0 Mb to 108.9 Mb with the addition of their plugin. Yes, I know the rationale for how great life will be with 100% fill rates and all these services being mediated (so their various providers’ code needs to be in the plugin). But a percentage (albeit not a major one anymore) of our users is sensitive to app file size – and this is the sort of bloat I normally only associate with the software company in Seattle.
One of the other problems is something your tech folks may be able to fix. I cannot make an iOS build with a fairly normal (for many developers) selection of plugins included along with the AppoDeal plugin. The builds always (over 3 different days of trying) time out. I even made some test builds using your Hello World example and they always times out without building with these fairly routine plugins:
[lua]
plugins =
{
[“plugin.appodeal”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true }
},
[“plugin.iCloud”] =
{
publisherId = “com.coronalabs”,
– supportedPlatforms = {iphone = true},
},
[“plugin.facebook.v4”] =
{
publisherId = “com.coronalabs”,
},
[“plugin.notifications”] =
{
publisherId = “com.coronalabs”,
},
[“CoronaProvider.gameNetwork.apple”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true},
},
[“plugin.flurry.analytics”] =
{
publisherId = “com.coronalabs”,
supportedPlatforms = { iphone=true}
},
},
[/lua]
The error looks like this in the console:
Sep 09 03:08:25.617 ERROR: XMLRPC: The request timed out.
Sep 09 03:08:25.617 WebServices: XMLRPC request failed
Sep 09 03:08:25.622 iOS build failed (11) after 240 seconds
Sep 09 03:08:25.848 ERROR: Build Failed: The request timed out.
If I take out all of the plugins except AppoDeal, your Hello World example will build with a build time around 261 seconds. (it almost times out by itself)
I’m guessing that your engineers are aware of how near the “timeout edge” this plugin actually is because of the recommendation (on your documentation) to use build 2016.2914 or later. I am using 2016.2931. I’m headed out of town later today on some vacation so I’m not certain I will be able to follow up on this thread quickly. But I thought your team should be aware of this build problem in case they can address it on your servers.
Steve
I am glad to answer all the questions about our service, what we do, why we do it and how :)