I have one android application and this application uses Google admob GoogleAdMobAdsSdk-4.1.0 version. Now i wants to update my google admob SDK.
This is the message on google admob site Here.
We are deprecating all SDK versions that were released in 2010 or earlier. For Android, this includes any SDK released on or before November 9, 2010. If your code references com.admob.android.ads.*, then you will need to update your SDK.
I am just try to replace this GoogleAdMobAdsSdk-4.1.0 version to GoogleAdMobAdsSdk-6.3.1 .
But i am getting error regarding import about com.admob.android.ads.* this.
Please let me know the solution regarding this
Thanks
com.admob.android.ads.* references old AdMob SDKs released in 2010 or earlier. If your app was only using GoogleAdMobAdsSdk-4.1.0, you should only have references to com.google.ads.*.
To can check the docs for how to set location. You'll use com.google.ads.AdRequest#setLocation(location). However, AdMob recommends that you only pass location in your AdRequest if your app already makes use of location, since it requires adding extra permissions in your app.
Related
Hi today google send me this email about all my application that use Google Place picker in ios and android.
*Today we're launching upgraded Places SDKs for Android and iOS. They are pay-as-you-go and billed at the same rate as our Places API and Places Library in the Maps JavaScript API. You can visit the Android and iOS migration guides to install the new SDKs.
Effective January 29, 2019, the upgraded Places SDKs for Android and iOS will replace the existing versions of the Places SDKs - please read our documentation for more information. The existing Places SDKs (including the Place Picker feature) can continue being used by current customers of these SDKs until July 29, 2019. In order to avoid service disruption, please start using the upgraded SDK versions before July 29, 2019.
We have identified that your projects listed below are using Places API and will be impacted by this change:
#
We have noticed that you do not have a billing account with a valid form of payment. Please update your billing account and associate it to your project(s) by July 29, 2019 to avoid service interruption.
We understand this announcement may have an impact on your implementations. If you have any questions, or require further assistance, please contact Google Maps Platform Support.*
Does this means that by by July 29, 2019 all my apps that use Place Picker will not function correctly because Google decided to remove it?
What am i suppose to do? Really confused again. Thanks Google!
My app heavily depended on the PlacePicker and It was free. Though there is a migration guide, but the new APIs are not free and have an upper cap on free usage. SO I built a Place picker that lets you pick places from a map using Geocoder and its free Check it out: https://github.com/suchoX/PlacePicker
As far as I can tell, the placepicker UI that they provided will no longer be available. You will have to find a replacement for the UI or come up with something on your own. You can still use the SDK to get autocompletion in order to simulate what the placepicker was doing. Everything that made the placepicker UI work is still there, they are just deprecating and no longer supporting the UI.
It says what you are supposed to do in the email google sent you. From yesterday, you have up to July 29, 2019 to implement and start using the updated SDK versions just for the Places API in place of the old. Once you have done this release it. Make sure you do this for all your apps that are effected by this update. If you don't do this, your apps can possibly still function but that feature will not.
EDIT:
On this page you can see the Deprecation notice
When you click the Android Migration we can see that you can install the compatibility library to continue using the Place Picker during the deprecation period. After this the place picker will no longer work.
Looks like you have to find another way to do what the place picker is currently doing for you.
Place Picker old version will be turned off from jul 29 2019 but migration option available
Migration Guide here
I'm a new Android developer, I recently encountered a problem on updating my app to Android 5.0. Same issue here: Android 5.0 (L) Service Intent must be explicit in Google analytics
According to that solution, I'm gonna updating from google analytics V2 to V4 (google play service). But the painful part is seems for every page, I need to change the tracking code. There are around 30 pages(activities and fragments) in my app, this is really not scalable, and easy to make regression bugs.
I was wondering is there any better way to do the migration? Thanks.
I created a small class, it's have same siganture of v2 in the body it's call a v4 methods, you can check it at my
gist
I'd like to implement banner-ads in my new app and stumbled across two possibilitys of doing this.
The first one is using the Android SDK: com.google.ads.*
The second one is using Google Play Services: com.google.android.gms.ads.*
I googled a lot and read the documentation but I found no resources which state the differences between both solutions.
What is the difference between both and which one is the best if I simply want to add banner-ads in my app?
Direct to the point,
The main difference is that if you use Google Play Services one then you will use Google play service APIs. If you use other modules of Google Play like maps, location, gcm, play games then you can use com.google.android.gms.ads.* but if you don't use other Services then use com.google.ads.*
Their behavior is same...
As Selvin did not post his comment as an answer I'll answer this question by myself:
Use the Google Play Services com.google.android.gms.ads.*
Don't use the Android SDK for Ads because it is deprecated:
Deprecated. On August 1, 2014, Google Play will stop accepting new or
updated apps that use the old standalone Google Mobile Ads SDK v6.4.1
or lower. You must upgrade to the Google Play version of the Mobile
Ads SDK by then.
Google Mobile Ads SDK
Is the Google Play Services SDK R15 available to download anywhere? The "ChromeCast SDK" was "released" Monday, according to hundreds of news sites. Those same news sites claim Android app developers are "hard at work implementing ChromeCast functionality." Is the SDK appearing in anyone's SDK Manager?
How are Android app developers implementing ChromeCast functionality when the SDK isn't available and the API has changed dramatically? The DayFrame developers supposedly already updated their app to the new API, which seems suspicious to me...
Edit - As per the announcement post, SDK15 is now available.
As per the Chromecast Android API reference:
These APIs are currently not available for development. They require Google Play services 4.2, which began rolling out to devices worldwide on February 3rd. Once the update to devices is complete, the corresponding Google Play services library (revision 15) will be available for you to begin using these APIs.
Certain developers have been given early access to the SDK directly from Google to allow early development, but general availability of SDK R15 is still to come. You can still read through the Developers Guide and the Android Sender App Development Guide and prepare your application, design, and resources appropriately, but the actually integration of the SDK and testing cannot occur until Google releases it officially after the full rollout of Google Play Services 4.2.
I have a DfpAdView that I'm using according to the documentation here:
https://developers.google.com/mobile-ads-sdk/docs/dfp/fundamentals#android
I've been using the GoogleAdMobAdsSdk-6.4.1. I just updated Google Play Services to version 13, and it seems that the AdMob SDK has been integrated into Google Play Services in this version. However, DFP is not supported as mentioned here:
https://developer.android.com/google/play-services/ads.html
Note: The SDK doesn’t currently support DFP, Ad Exchange or Search Ads for Mobile Apps but support is coming soon.
I have to use GooglePlayServices for the Maps SDK, but it breaks the required DFP ad that I'm using. Do I need to remove the DFP ad in favor of something else, or do I change the build order so that the AdMob jar takes precedence over the GPS library where package/class names conflict (is that possible?)
The best solution for now (if you are using DFP and one of the other Google Play services) is to excise the Admob classes from the Google Play Services library and use the Admob-6.4.1 SDK.
Not ideal, but I suspect DFP support will be delivered soon.
Alternate is t hold off on upgrading to the new GPS library until DFP support is available. Depends on your urgency.