iOS 开发：通过 AdWhirl 将 Greystripe 广告添加到我的应用程序会导致崩溃
我的一个免费应用程序发出了足够多的广告请求，导致填充率非常低，因此我决定在我的应用程序中添加另一个广告网络以及 iAd 和 Admob。使用 AdWhirl，这是一个非常简单的过程。您将 Greystripe SDK 文件夹放入 XCode 中，并在 AdWhirl 代码中启用 Greystripe 适配器。就是这样！不幸的是，它崩溃了:)
Greystripe 广告横幅加载得很好，但是一旦它尝试解除分配，它就会在 AdWhirlAdapterGreystrip.m 文件中的以下代码中崩溃...
- (void)dealloc {
[innerContainer release]; //<--Crash here
[outerContainer release];
[super dealloc];
}
我根本不知道 AdWhirl SDK 代码，在我深入研究之前，我希望其他人已经看到过这个，或者能给我一些去哪里看的想法。
非常感谢您的智慧！
One of my free apps is making enough ad requests to cause really low fill rates, so I decided to add another ad network alongside iAd and Admob to my app. With AdWhirl, this is a very easy process. You drop the Greystripe SDK folder into XCode and enable the Greystripe adapter in the AdWhirl code. That's it! Unfortunately, it's crashing :)
The Greystripe ad banner loads fine, but as soon as it tries to dealloc, it crashes in the following code in the AdWhirlAdapterGreystrip.m file...
- (void)dealloc {
[innerContainer release]; //<--Crash here
[outerContainer release];
[super dealloc];
}
I don't know the AdWhirl SDK code at all and, before I dive into it, I was hoping someone else has seen this or can give me some ideas of where to look.
Thanks so much for your wisdom!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们适配器的当前发布版本在新的
stopBeingDelegate方法中存在错误，正如 Bastian 所说，这会导致错误的发布。要解决此问题，只需注释掉：
来自
AdWhirlAdapterGreystripe.m中的stopBeingDelegate方法，这也是 在 Google 代码中报告。如果您有机会，请“星标”此问题，以便 AdWhirl 将此修复合并到版本中。
全面披露：我为 Greystripe 工作;)
The current release version of our adapter has a bug in the new
stopBeingDelegatemethod, which as Bastian says, results in a bad release.To solve this just comment out:
from the
stopBeingDelegatemethod inAdWhirlAdapterGreystripe.mThis is also reported in google code. If you have a chance please "star" this issue, so AdWhirl will merge this fix into the release.
Full disclosure: I work for Greystripe ;)
通常这个位置的崩溃意味着innerContainer已经被提前释放了。或者从未被妥善保留。
Usually a crash in this location means that innerContainer was already released earlier. Or was never retained properly.