Hi Tony,
The next step will be to try building our sample Commercial Break app which has the basic build settings necessary. If you can build that, then we will know it’s not a build issue, but rather something related to your system or your project’s build settings.
https://github.com/coronalabs/plugins-sample-combre
Best regards,
Brent
Hi Brent,
The plugins-sample-combre app sample builds for iOS just fine. I tried copying my failing app’s build.settings to the sample project, and it still builds with no problem.
My app, however, still gets the same build error when the combre plugin is not commented out.
I am now thoroughly confused:
App build fails for iOS with combre plugin
App build succeeds for Android with combre plugin
App build succeeds for iOS without combre plugin
App build succeeds for Android without combre plugin
Sample app build succeeds for iOS with combre plug and same build.settings as fail case in other app
Any ideas what else to try?
Thanks,
Tony
Hi Tony,
Something just doesn’t add up here. You say that you can build with the sample’s build.settings AND with your project’s build.settings. But then if you take either of those outside of the sample, and into your project, it fails to build???
Brent
No, I have not tried to use the sample project’s build.settings in my project. My project will not run with the sample project’s build.settings because it needs those other plugins. I am not understanding why my project won’t build when the sample project builds fine with the same build.settings from my project that fails to build.
Yeah, I understand that the sample’s build.settings won’t work in your project, because it only has the “combre” plugin. I’m just baffled why your build.settings work inside the sample, but not inside your own project.
What version of Corona are you using? What version of iOS are you targeting in the build window? Is Xcode and everything else up-to-date?
Brent
Corona: 2016.2818
iOS Target: 9.2
Xcode: 7.2 (7C68) - The latest Xcode is 7.2.1, but I haven’t updated to it yet.
update:
I decided to try adding in the applovin plugin to my project to see if adding that plugin had the same problem and sure enough, I am getting the same build failure as when including the combre plugin.
Tests:
App build fails for iOS with combre plugin
App build fails for iOS with applovin plugin
App build succeeds for Android with combre plugin
App build succeeds for Android with applovin plugin
App build succeeds for Android with combre + applovin plugin
App build succeeds for iOS without combre plugin
App build succeeds for iOS without applovin plugin
App build succeeds for Android without combre plugin
App build succeeds for Android without applovin plugin
Sample app build succeeds for iOS with combre plug and same build.settings as fail case in App
Sample app build succeeds for iOS with appslovin plug and same build.settings as fail case in App
Sample app build succeeds for iOS with combre + appslovin plug and same build.settings as fail case in App
Hi Tony,
I don’t know what else I can do to assist you. The engineers report that there’s literally zero chance that this is caused by anything except your build.settings. I would, if anything, suggest that you start ripping out (or commenting out) entire sections that may not relate, i.e. all of the Android stuff (since your issue here is on iOS), all of the iCloud stuff, all of the tvOS stuff, all plugins that are not immediately needed, etc. If you want, even consider just putting your build.settings inside our “Hello World” sample (which obviously uses no plugins) and see if you can get a build to work. Sorry I can’t be of more help, but no other users are reporting build issues with these plugins, so the symptom is most likely related to your build.settings.
Best regards,
Brent
Well is there a build log that might help point me in the right direction here? Obviously, something about adding these plug-ins is causing the build to fail, but I am completely blind as to what. If I give you a build ID, can you check logs on your end? Here’s my latest:
Building ios app for tonygod@hotmail.com with 2016.2818
Using custom build id from app bundle: 00000 (AppSettings.lua)
BuildID: 56b3c049a3c61
ERROR: Unexpected empty response from build server
iOS build failed (5)
ERROR: Build Failed: ERROR: Unexpected empty response from build server
since my same build.settings file works with the combre sample app, i don’t see how adding it to the hello world app would help.
Thanks,
Tony
Hi Tony,
I checked into some details on this build. It appears that the build was possibly timing out or running out of memory, possibly because you’re using a huge amount of plugins. I would definitely ask you to consider why you’re using/needing ~3 different ad providers (it appears you’re using Fuse as well).
On a related note, your uncompressed app is over 200 megs. That’s getting a bit hefty IMHO.
In any case, we increased the memory limit, so please try building again and report back what happens.
Thanks,
Brent
Ok I found another variable to the equation:
If I uncheck “Enable Analytics and Monetization” my app build succeeds.
If I check “Enable Analytics and Monetization” in the stock combre sample app, the build fails with a link error:
BUILD ERROR: There was a problem linking the app. Check the console for more information. iOS build failed (12) ERROR: Build Failed: There was a problem linking the app.
So I think there is some kind of conflict between this setting and/or the Fuse plug-in and all these other plug-ins. See this thread for a related report from another developer with the Facebook plugin.
So, you weren’t actually implementing Fuse, but you were simply checking that box in the build window? Please leave it unchecked if you’re not explicitly using Fuse. I understand this is confusing, but we’re working on resolving/clarifying that soon.
Brent
I am using Fuse right now in production. I am testing out applovin and combre as possible back-ups or replacements for Fuse in the event that it is unavailable or otherwise unusable.
If it is not allowed/advisable to use multiple ad providers in Corona apps, I would like to see that stated somewhere in the documentation.
Hi Tony,
It’s not “disallowed” to use multiple providers, but if you’re testing out alternatives, I suggest you comment out the ones you’re considering replacing.
Take care,
Brent
If for no other reason, your builds will be much faster if you remove plugins you’re not really testing with. Every plugin you include needs to be packaged up as part of the build, and adds to the binary size as well as taking up network bandwidth.
Alright, let’s take a look at where we are:
You can confirm that there is an issue with the “Enable Analytics and Monetization” setting when used with the following plug-ins:
combre
applovin
Facebook?
You are working on resolving/clarifying the issue “soon”
Uncompressed apps over 200 megabytes are considered “a bit hefty”
my uncompressed source tree for the app is 70mb
There is a significant amount of binary bloat that occurs with each plug-in
each plug-in binary adds to overall app binary size
larger app binaries use more network bandwidth because Corona (free) requires builds to happen remotely
It is not “disallowed” to use multiple providers
It is suggested to comment out plug-ins that you are not using
From this, I surmise you are telling me you know about this problem and a fix is already being discussed.
Best regards,
Tony
Hi Tony,
Yes, let me summarize that we are aware of the issues between that checkbox and the build issue that you experienced. In the meantime, I still advise that for testing alternative ad provider plugins like Commercial Break, AppLovin, or Facebook Audience Network, you comment out Fuse, Vungle, etc.
Best regards,
Brent
Thanks, Brent. For now, I will uncheck the Analytics and Monetization checkbox (disable Fuse) when testing with combre, applovin, FAN. Why do you also recommend commenting out Vungle? Is it because of the size/network concerns or is there also a conflict of some kind?
I think I should just state that I don’t think many of us look at these as binary options. It just makes sense to diversify your ad portfolio and avoid keeping all of your eggs in one basket. I may be one of the earlier people to find this, but I know I am not the only one.
I received a message from Fuse this morning that says starting Feb. 11, the Fuse plug-in will need to be explicitly added to build.settings, so I am guessing that is the timeframe for this issue to be fixed?
-Tony
Hi Tony,
Did you figure out a solution to this? We’re having the same problem with trying to integrate Fuse / AppLovin and Appsaholic.
Thanks in advance!
Dean
Hi Dean,
No, I never successfully built my project with both Fuse and Combre plugins enabled. I ended up pulling the Fuse plugin in favor of Vungle and decided against using Combre because of plugin size and permission concerns.
Best regards,
Tony