AdWhirl 与 MillennialMedia 集成，未找到符号
我想在我的 adwhirl 中启用 MM 广告。我做了与 inmobi、admob、mobclix 等其他网络相同的操作，但是对于 MM，我收到此错误：
Undefined symbols for architecture i386:
"_UTTypeCreatePreferredIdentifierForTag", referenced from:
-[MMFileManager getMimeType:] in libMMSDK.a(MMFileManager.o)
"_UTTypeCopyPreferredTagWithClass", referenced from:
-[MMFileManager getMimeType:] in libMMSDK.a(MMFileManager.o)
"_kUTTagClassFilenameExtension", referenced from:
-[MMFileManager getMimeType:] in libMMSDK.a(MMFileManager.o)
"_kUTTagClassMIMEType", referenced from:
-[MMFileManager getMimeType:] in libMMSDK.a(MMFileManager.o)
ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status
我没有更改 adwhirl 适配器，只需将 MM sdk 拖到项目中即可。我的 admob 集成从未发生过这种情况。 请帮助我
i want to enable MM ad in my adwhirl. i did the same thing as other networks like inmobi, admob, mobclix etc, but with MM, i get this error:
Undefined symbols for architecture i386:
"_UTTypeCreatePreferredIdentifierForTag", referenced from:
-[MMFileManager getMimeType:] in libMMSDK.a(MMFileManager.o)
"_UTTypeCopyPreferredTagWithClass", referenced from:
-[MMFileManager getMimeType:] in libMMSDK.a(MMFileManager.o)
"_kUTTagClassFilenameExtension", referenced from:
-[MMFileManager getMimeType:] in libMMSDK.a(MMFileManager.o)
"_kUTTagClassMIMEType", referenced from:
-[MMFileManager getMimeType:] in libMMSDK.a(MMFileManager.o)
ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status
i didn't changed the adwhirl adapters, just drag the MM sdk into the project. this never happened for my admob integration.
plz help me
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
听起来您的项目中未包含 MobileCoreServices 框架。包含该框架，它应该可以工作。
It sounds like the MobileCoreServices framework isn't included in your project. Include that framework and it should work.
找不到符号可能有以下原因：
检查您的目标的“将二进制文件与库链接”部分，并确保无论用于 MM 的库已添加到列表中。
这表明您正在为 iOS 模拟器构建。有可能 MM 根本不提供在 iOS Simulator 中运行的代码，而仅在设备上运行。尝试进行设备构建。
Symbol not found can have the following causes:
Check your target's "Link Binary with Libraries" section and make sure that whatever library is used for MM is added to the list.
This indicates that you're building for the iOS Simulator. It is possible that MM simply does not provide code that runs in iOS Simulator, only on devices. Try doing a device build.