Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use ads-identifier library instead of play-services-ads to fetch advertising ID
See original GitHub issueSummary
Right now the SDK uses the big play-services-ads library to fetch the advertising ID. However, Google has introduced the much smaller and better scoped ads-identifier library for exactly that task: https://developer.android.com/training/articles/ad-id
Motivations
The new Advertising ID library is smaller and better scoped. Especially apps which don’t already display Google Ads would benefit from switching to the Advertising ID library. Also, using the new library now is Google’s recommended approach to fetch the Advertising ID on Android.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My bad. I ran into a combination of strange Gradle dependency issues and misread your proposal. I did investigate and yeah, it looks like
AdvertisingIdClientis the only actual library class we are using. I ran into some other deprecated libraries likecom.google.android.gms.common.GooglePlayServicesUtilthat I’ll investigate more into. I’ve seen the new package you are referring to inandroidx...and I’ll be testing that again.@ubuntudroid This’s a really good point! We will take a look.