升级您的 Android Google 移动广告 SDK 以确保广告持续投放
Upgrade your Android Google Mobile Ads SDK to ensure ads keep serving
我今天收到这条消息：
Hi AdMob Publisher, In early July, we sent out a notice to AdMob
Publishers who have apps running on SDK version 6.4.1 and lower, to
inform them about deprecating SDK versions and the need to upgrade by
September 15, 2016. We apologize for any inconvenience or unclarity
that the email may have caused to some developers. To ensure that you
have sufficient time to make the changes, we have extended the
deprecation date to October 17, 2016. We also reevaluated the SDK
versions being deprecated, so here is the updated information. What
will happen starting on October 17, 2016: • All support for non-Google
Play Services supported SDKs and Google Mobile Ads SDK version listed
here will be deprecated. • This means that all traffic from these SDKs
will be disabled. What you will need to do: In order to ensure that
your AdMob ads continue to serve after October 17, 2016, please
upgrade your apps to run on the minimum SDK versions listed here. If
you are using a Google Mobile Ads SDK version from Play Services that
is listed on this link, you are not required to take any action. If
you have any questions, please contact us on the developer forum.
Thank you, and stay tuned for more updates and tips. Cheers, The
AdMob Team
我使用的是 Play 服务版本 4.4.52-000。这个版本好吗？我需要更新吗？
单击电子邮件 https://firebase.google.com/docs/admob/android-legacy-release-notes
中提供的 link
"Prior to becoming part of Google Play services, AdMob had a
standalone SDK with the following versions and release notes listed
below ( Refer to link ).
On October 17th, 2016, AdMob will stop serving ads to the SDK versions
listed below. If your apps are still using any of these SDKs, follow
our Get Started to integrate with AdMob's Google Play services SDK."
您收到的关于 SDK 需要高于 v6.4.1 的说明指的是旧版独立移动广告 SDK，该 SDK 已于 2014 年 2 月弃用，并且有自己的版本控制系统。
如果您的 google_play_services_version > 4 ，则无需立即更新，但最好升级到最新版本的播放服务库。
编辑 2016 年 10 月 7 日：如果您使用的是此 link 中列出的来自 Play 服务的 Google 移动广告 SDK 版本，您不需要采取任何行动。
我认为大多数混淆是由于 Admob 独立 SDK 和 Google Play 服务的版本号之间的版本号造成的。
我今天收到这条消息：
Hi AdMob Publisher, In early July, we sent out a notice to AdMob Publishers who have apps running on SDK version 6.4.1 and lower, to inform them about deprecating SDK versions and the need to upgrade by September 15, 2016. We apologize for any inconvenience or unclarity that the email may have caused to some developers. To ensure that you have sufficient time to make the changes, we have extended the deprecation date to October 17, 2016. We also reevaluated the SDK versions being deprecated, so here is the updated information. What will happen starting on October 17, 2016: • All support for non-Google Play Services supported SDKs and Google Mobile Ads SDK version listed here will be deprecated. • This means that all traffic from these SDKs will be disabled. What you will need to do: In order to ensure that your AdMob ads continue to serve after October 17, 2016, please upgrade your apps to run on the minimum SDK versions listed here. If you are using a Google Mobile Ads SDK version from Play Services that is listed on this link, you are not required to take any action. If you have any questions, please contact us on the developer forum. Thank you, and stay tuned for more updates and tips. Cheers, The AdMob Team
我使用的是 Play 服务版本 4.4.52-000。这个版本好吗？我需要更新吗？
单击电子邮件 https://firebase.google.com/docs/admob/android-legacy-release-notes
中提供的 link"Prior to becoming part of Google Play services, AdMob had a standalone SDK with the following versions and release notes listed below ( Refer to link ).
On October 17th, 2016, AdMob will stop serving ads to the SDK versions listed below. If your apps are still using any of these SDKs, follow our Get Started to integrate with AdMob's Google Play services SDK."
您收到的关于 SDK 需要高于 v6.4.1 的说明指的是旧版独立移动广告 SDK，该 SDK 已于 2014 年 2 月弃用，并且有自己的版本控制系统。
如果您的 google_play_services_version > 4 ，则无需立即更新，但最好升级到最新版本的播放服务库。
编辑 2016 年 10 月 7 日：如果您使用的是此 link 中列出的来自 Play 服务的 Google 移动广告 SDK 版本，您不需要采取任何行动。
我认为大多数混淆是由于 Admob 独立 SDK 和 Google Play 服务的版本号之间的版本号造成的。