currently corona is using AdColony 3.3.5 (2018/06/27)
the latest AdColony is 3.3.11 (2019/07/15)
in this year span adcolony fixed and improved stability.
Can you please integrate the latest SDK (no api change, just rebuilding)
Jump to content
Could your engineering team also take a hard look at Chartboost -- which is way behind on the SDK version as well (I believe)?
This "paid" plugin (I've paid for it for many years) has had problems that I and others have commented on several times without any attention/resolution. See :
It would be great if updating this plugin would return it to reliability.
What version of Corona are you using @MartingK?
Engineering did add this note: "did some refactoring to prevent crashes" to the message regarding AdColony. It's possible printing the local SDK version was part of that refactoring. I dug through the source of the recent change and one of the things that was refactored was a hard coding of the SDK version number. This comment was in the old code that got changed:
"AdColony.getSDKVersion() doesn't return the correct version. Actually, from their docs: "Will return an empty String if AdColony has not yet been configured."
The printing of the SDK version was probably considered a hack, and we're going back to the way it should work.
"Adcolony: ios: 184.108.40.206 android: 3.3.11" is the exact quote that the engineer who updated the plugin gave me.
I shared a comment from the previous version where we hard coded 3.3.5 because the AdColony SDK does not reliably return the SDK version. I've not had a chance to talk with Engineering to find out why they chose to remove the hard-coded version number, but they did say they refactored some things to avoid crashes and suspect that the hard-coded version number was victim of that refactoring and hard coding information like that isn't a good engineering practice.
Until AdColony fixes their API to get the version number to actually reliably return a value, you likely will not be getting a value returned for that API.