I tried to compile my app with Appodeal 5-6 times but I get a link error "libappodealPlugin was built for newer iOS version (7.0) than being linked (6.0)
What version of Corona SDK are you using?
What version of macOS are you using?
What version of Xcode are you using?
What version of Corona SDK are you using? CoronaSDK 2016.2931
What version of macOS are you using? OS X El Capitan Version 10.11.6
What version of Xcode are you using? Version 7.3.1(7D1014)
I just tried and didn’t get that message. Can you post the entire console log?
Rob
I’m also getting an error when trying to build with the appodeal plugin.
Daily build 2931
MacOS El Capitan 10.11.4
Xcode 7.3.1
The error mine says is “Build failed: there was a problem linking the app.”
Can you post your entire console log fro the build run please?
Hey Rob,
Is this what you wanted from the console window?
https://dl.dropboxusercontent.com/u/3371101/appodeal%20error.rtf
I couldn’t upload to pastebin because it was too big, hope the rtf is ok.
Perfect. I’ll send this to the engineering team. I wouldn’t expect a response until next week though.
Rob
Rob, here is my console log from my build , its also too large to pose.
https://www.dropbox.com/s/s9wjtrrrwuwjykt/appodeal_link_error.txt?dl=0
Does Appodeal have any gotcha’s?? Can you still you use Admob as backup and can you still use flurry with appodeal?
I’m unaware of any Gotcha’s other than Appodeal has SDK’s built in to their SDK for the ad providers they support. Since they use Admob too, I don’t see why you would want to burden yourself with coding up multiple ad providers. You should get a 100% fill rate and great eCPMs from Appodeal.
I’ve not heard an issues with Flurry and Appodeal.
Rob
@burnsj002, are you just seeing warnings about the mis-matched SDK or is it actually erroring out? The log got cut off and I couldn’t see the final build results.
If the build is completing, then you can ignore the warnings. Engineering says they are harmless.
Rob
Rob, check the file in drop box again. I saved it with the entire console build this time.
But yes I get errors on the build.
At least one of the issues that you have I had. On iOS, you can not include GoogleGameServices since Appodeal already includes its own version (and a much newer version).
The rest of the errors I saw are just warnings.
Thanks for the logs.
It looks like this is a case of plugin intercompatibility between appodeal and x plugin.
I am investigating this and will report back.
Thank you
Danny please make sure they don’t break it. It works perfectly for me on Android, Amazon and iOS. It is like a dream and the best working ad plugin so far. 100 fill rate and the iOS version is using a recent version of Admob so it even supports SDK less mediation. This is technically not a defect since you can remove the duplicate plugin and it works.
Well, I was finally able to compile my App with Appodeal plugin without any link errors :D Agramonte was right. I removed GoogleGameServices & Flurry plugins and it works fine now.
Just curious does the Google Analytics plugin cause link problems with Appodeal?
From what I can tell it works with Google Analytics on iOS. I don’t think it works on Android with GoogleGameServices and this is why I have been using the old all lua plugin.
From my investigation so far, this only affects iOS. So you should use the relevant Google related plugins on Android as you were previously.
Hi Danny;
I am running into the same sort of build errors reported above by burnsj002 and naveen_pcs. The problem is in building for iOS and I am using Corona Build 2931. Here is a quick rundown:
a) First time I tried to build, the conflict was between duplicate symbols in Vungle Plugin and AppoDeal Plugin. Here is a snippet of the last lines of the error message from the console:
(VungleAdLegacy.o)
/Users/steve/Desktop/Just 2 Builds/Just 2 Words.app/.build/plugin.appodeal/libappodealPlugin.a(VungleAdLegacy.o)
duplicate symbol _OBJC_METACLASS_$_VungleAdLegacy in:
/Users/steve/Desktop/Just 2 Builds/Just 2 Words.app/.build/CoronaProvider.ads.vungle/libads-vungle.a(VungleAdLegacy.o)
/Users/steve/Desktop/Just 2 Builds/Just 2 Words.app/.build/plugin.appodeal/libappodealPlugin.a(VungleAdLegacy.o)
ld: 3577 duplicate symbols for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
BUILD ERROR: There was a problem linking the app.
Check the console for more information.
b ) First thing I tried was reversing the position of plugins in build.settings in case that might change build order and solve problem. Didn’t solve problem. Same error.
c) Second thing I tried was building app with ONLY 2 PLUGINS – Vungle and AppoDeal. Didn’t solve problem. Same basic run of “duplicate symbol” errors. I you want something simple and reproducible, just try to build for iOS with just these 2 plugins.
d) So I tried removing Vungle from build.settings while leaving my other plugins (I have a fair number) in the app. I then got the same sort of “duplicate symbol” conflicts between AppoDeal and appLovin. It wouldn’t build.
e) So I removed appLovin from build.settings. I then got the same sort of “duplicate symbol” conflicts between AppoDeal and fbAudienceNetwork. It wouldn’t build. Here’s the final snippet of that error:
libFBAudienceNetwork.a(FBAdBodyView.o)
duplicate symbol _OBJC_IVAR_$_FBAdBodyView._nativeAd in:
/Users/steve/Desktop/Just 2 Builds/Just 2 Words.app/.build/plugin.appodeal/libappodealPlugin.a(FBAdBodyView.o)
/Users/steve/Desktop/Just 2 Builds/Just 2 Words.app/.build/plugin.fbAudienceNetwork/libFBAudienceNetwork.a(FBAdBodyView.o)
ld: 2679 duplicate symbols for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
BUILD ERROR: There was a problem linking the app.
f) I stopped trying to build for iOS at this point.
As an aside (possibly important), I looked back at some correspondence I received from “Danny” in Tech Support (you??) back on February 19th. That week, I had reported a bug (case #45046) with the brand new fbAudienceNetwork Plugin that had the same sort of “duplicate symbols for architecture armv7” error resulting in “BUILD ERROR: There was a problem linking the app.” You folks solved that one in a matter of days. You may want to look at your solution.
And finally, there is still an error of this same sort between the fbAudienceNetwork Plugin and the CoronaAds Plugin on iOS. I pointed this out back in the CoronaAds Beta program and, to my knowledge, it remains a deal breaker – you can’t build for iOS with those two plugins. As a result, I am not using CoronaAds :-(.
Hope this info helps your folks track down the error
Steve
Hey Steve.
I’ll answer your questions point by point to help you understand why these things are happening.
A ):
Appodeal does mediation for several providers, including Vungle. To do this, they include the Vungle SDK in their own static library (SDK). This means that you can’t use Vungle and Appodeal together separately. The simplified technical side of this answer is that since Vungle’s SDK’s static library is contained inside Appodeals static library, if you try to build using both plugins, the linker barfs at duplicate symbols because it’s finding Vungle’s symbols in the Vungle plugin and in the Appodeal plugin.
Generally the goal behind using a mediation provider is to let them do the mediation for you. They don’t intend that you also use them alongside other ad plugins that they provide mediation for already.
So the only solution to this is to use Appodeal and let it do the mediation for you, or use Vungle and do the mediation yourself. Personally I would use Appodeal, as it has advanced algorithms to get you the most ad revenue. They have spent an inordinate amount of time on these algorithms, and they are very good.
B ): The order of plugins defined in build.settings makes no difference to the build process. Just for clarity.
**C): **Same answer as A.
**D): **Same answer as A, Appodeal also does Applovin mediation.
E): Same answer as A, Appodeal also does Facebook Audience Network mediation.
**F): **CoronaAds also does mediation, so that is why you can’t use Facebook Audience network alongside it. Answer is more or less the same as the first section of A.
To answer your “aside”, unfortunately that was a completely different issue that was caused by an accidental inclusion of a library on the build server. Not related to this case i’m afraid.
Summary :
The way to look at Appodeal isn’t “i’ll use this alongside other ad providers for my project”, but should be seen as “i’ll use this as my ad provider for my project and let it handle the hassle of mediation for me”.
I hope that clears things up for you. If you have any more questions or would like clarification on what I have said, just let me know.