Xamarin Forms iOS AdMobViewRenderer VS2019 [英] Xamarin Forms iOS AdMobViewRenderer VS2019

问题描述

我的Android和iOS版本的应用程序都运行良好，然后我将VS2019更新为16.1.2，并带来了Xamarin 16.1

Things were working fine for both my Android and iOS versions of the app, then I updated VS2019 to 16.1.2 which brought along Xamarin 16.1

我可以在应用程序中向前移动，看起来一切都很好，但是当我向后移动(一步或PopToRoot)时，AdMobViewRenderer中的Element为null.有什么想法吗?

I can move forward in the app and it seems that all is well, but when I move backward (one step or PopToRoot), the Element is null in the AdMobViewRenderer. Any ideas?

我正在使用Xamarin.Firebase.iOS.Admob 7.27.0.3，因为那是一个可以正常运行且没有错误的版本.

I am using Xamarin.Firebase.iOS.Admob 7.27.0.3 because that is the one version that would work properly without error.

期望收到更新"答复，因此我更新到了最新的AdMob版本，并提出了以前遇到的本地链接失败"错误.我一次备份了一个发行版号(清理并清除了缓存目录)，并将错误数从60多个减少到59个.消除错误的唯一方法是回到7.27.0.3

In anticipation of the "update" reply, I updated to the latest AdMob version and came up with the previously experienced "native linking failed" errors. I backed down one release number at a time (with clean and clearing of cache directory) and reduced the number of errors from over 60 to 59. The only way to eliminate the errors was to go back to 7.27.0.3

然后我在Mac上的VS2019上打开了该项目，由于无法编译最新至7.27.0.3之间的任何admob版本号，因此体验更加糟糕.

Then I opened the project on VS2019 on my mac and the experience was even worse with the inability to compile with any of the admob version numbers between the latest and 7.27.0.3.

我还收到一条消息，即连接到Mac时，mono(mac的最新更新)版本可能与我的Windows版本不兼容.据我所知，Win上的VS2019已完全更新.

I also get a message that the version of mono (latest update for mac) may not be compatible with my windows version when connecting to the mac. As far as I can tell, VS2019 on Win is completely updated.

有什么想法或建议可以使Admob在iOS上正常运行，以便我可以构建和分发?Android可以正常工作.

Any ideas or suggestions to get Admob working for iOS so that I can build and distribute? Android works fine.

推荐答案

好吧，由于没有人回答这个问题，因此Microsoft做到了.他们发布了Visual Studio 2019(.3)的另一个更新，并修复了iOS上的Admob问题.它仍然没有解决的问题是，每当位置返回堆栈时，元素为null.有人对这个问题有建议吗?并且null元素终于被解决了.我不得不用MarcTron Admob插件替换旧的Admob插件.这不仅解决了iOS的元素问题，还解决了在iOS和Android广告单元ID之间进行手动切换的需求.MarcTron做得好！

Well, since nobody answered this question, Microsoft did. They issued another update for Visual Studio 2019 (.3) and that fixed the Admob problem on iOS. What it still hasn't fixed is the problem that element is null every time the location progresses back in the stack. Would anyone have a suggestion for that problem? And the null element has finally been resolved. I had to replace the old Admob plugin with the MarcTron Admob plugin. Not only did this resolve the element issue with iOS, it also solved the need to manually flip between the iOS and Android adunit IDs. Excellent job, MarcTron!

这篇关于Xamarin Forms iOS AdMobViewRenderer VS2019的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！