Re: Play Store App Download History
Arnau Cyr
Google tracks your activity across its services, including the Play Store. Your searches on the Play Store are stored and show up as recent searches. While this feature saves time, you may not always want to be reminded of your previous searches. Google also keeps a record of every app you ever downloaded on your smartphone or affordable Android tablet. However, you can get rid of your search queries and download history whenever you want. This guide walks you through how to delete your Google Play Store history.
Deleting your Google Play Store search history is a good idea if you don't find it useful. While you can delete your Google search history from your desktop, you'll need an Android device to delete your Play Store history. Also, there isn't a way to deactivate the search history, so you must delete it manually after each new search.
Google keeps a list of the apps you downloaded from the Play Store, even if they aren't installed on your phone anymore. This history helps Google make your searches more relevant and faster if you ever want to reinstall an app. However, you can delete your app download history if you don't want to be reminded of your previous downloads.
Google also lets you modify the history to remove only certain apps. You can always install these removed apps by searching for them in the search bar. Follow the steps below to delete your Google Play Store app download history from your Android smartphone.
You can easily take control of your Google Play Store search history to keep your data safe. However, Google services go beyond the Play Store. Follow these steps to protect your digital privacy on Android. You can also check out the best Play Store alternatives if you're looking for apps and games that appeal more to your interests.
The play-services-appsearch library is now generally available. Thislibrary provides APIs to store structured data in the centralized AppSearchdatabase provided by Google Play services. This enables cross-app data sharingbased on the client-provided access control list (ACL) configuration.Cross-app sharing is opt-in and requires explicit developer configuration whenusing AppSearch APIs.
These Firebase artifacts did not supply their own binary and were only awrapper around their dependencies. We're making this change to give you morecontrol over the dependencies that you add to your app. For more informationabout this change and how to migrate to use the Google Mobile Ads Android SDK,seethis FAQ in theFirebase documentation.
Added new ranging capabilities for configurable slot durations andranging intervals. SeesupportedSlotDurations,supportedRangingIntervals,supportsRangingIntervalReconfigure,andhasBackgroundRangingSupport.
Using the Acceleration Service library (play-services-tflite-acceleration),you can run ML performance benchmarks on device and automatically determinethe best way to accelerate the ML workload. For more information, refer totheAcceleration Service documentation.
The latest update of the Google Play services TensorFlow Lite library(v16.0.0) is now available. With this release, the library is now generallyavailable. This library can be used as an alternative to the standaloneTensorFlow Lite library to reduce app size and receive automatic updates. Formore information, refer to theTensorFlow documentation.
Updated versions of thegoogle-services pluginfor Android (v4.3.12) and thestrict-version-matcher pluginfor Android (v1.2.4) are now available. For more information, see theFirebase Android SDK Release Notes.
The play-services-appindex library is now generally available. Thislibrary is a replacement for the firebase-appindexing library andsupports use cases for sharing structured documents as Indexablesand UserActions with Google Assistant.
The latest updates to play-services-base and play-services-tasks resolvethe issue that can lead toruntime NPEs (NullPointerException) when handlingTask results in Kotlin code. If you're using any ofthe library versions listed in the December 09, 2021release, you can avoid the runtime NPEs by explicitlydepending on v18.0.1 of play-services-base and play-services-tasks. Addthe following to the dependencies section of your build.gradle:
The latest updates to the play-services-base, play-services-basement, andplay-services-tasks libraries include the strict nullability annotationchanges described above, as well as these additional changes:
The release includes a new map renderer that is available for opt-in use,which provides improved performance and stability, as well as support forCloud-based maps styling. For more information about this and other updates,see the productrelease notes.
This library includes methods to manage app set ID, which is a unique ID that,on a given device, allows you to correlate usage or actions across a set ofapps owned by your organization. For more information, refer to this guide.
If you use ads-identifier v17.1.0 or higher, then you don't need to declarethe permission again in your app manifest to access the advertising ID.However, if your app shouldn't access the advertising ID, you must remove thepermission using.
The developer preview release of the play-services-appset library is nowavailable. This library is designed to support use cases such as analytics orfraud prevention in a way that respects user privacy.
This library includes methods to manage app set ID, which is a unique ID that,on a given device, allows you to correlate usage or actions across a set ofapps owned by your organization. For more information, refer to thisguide.
The ads-identifier API reference documentation has been updated withinformation about an upcoming change to the advertising ID when a user enableslimit ad tracking as well as a requirement on a new Google Play servicespermission.
The Stream Protect SDK is now available for use with latency-sensitivedownstreaming Android TV applications. This SDK requires device firmwaresupport and currently only runs on Chromecast with Google TV. For moreinformation, refer to theStream Protect SDK reference documentation.
In preparation for enforcing strict nullability, we added @RecentlyNonNulland @RecentlyNullable annotations to several SDKs that previously did notexplicitly define nullability. This change will cause warnings on null safetyviolations.
Added @NonNull and @Nullable annotations in the API surface whichmay break Kotlin apps that did not previously handle null values ina safe way (seeKotlin documentation about Null-safety).
Added support for the disruptive upgrade feature. This feature isenabled by default. The client can disable it withAdvertisingOptions.Builder#setDisruptiveUpgrade(boolean)andConnectionOptions.Builder#setDisruptiveUpgrade(boolean),which prevents the originally connected Wi-Fi network from beingdisabled or disconnected during the upgrade progress.
Added the following declaration to the AndroidManifest.xml to supportPackage visibility filteringon Android 11 (API level 30) and above. After updating tocom.google.android.gms:play-services-maps:17.0.1, you can remove thefollowing line from your own AndroidManifest.xml:
The Fused Location Provider (FLP) now suppresses initial inaccuratelocations by default. This behavior allows for improved location accuracywhile minimally increasing latency. Developers who prefer to have fasterresults instead of more accurate results can call the newLocationRequest#setWaitForAccurateLocation()method.
ThrowsGooglePlayServicesIncorrectManifestValueExceptionor GooglePlayServicesMissingManifestValueExceptioninstead of IllegalStateException when AndroidManifest.xml lacks theappropriate metadata tag for using Google Play Services. This may indicatean issue with how the app was built.
Write-access now only lets an app read data it has written. To continuereading data written by other apps from the Google Fit platform, updateyour code to request read-access scopes for the relevant data types.
Updated versions of thegoogle-services pluginfor Android (v4.3.4) and thestrict-version-matcher pluginfor Android (v1.2.2) are now available. For more information, see theFirebase Android SDK Release Notes.
In preparation for enforcing strict nullability, we've added@RecentlyNonNull and @RecentlyNullable annotations where the base andbasement SDKs previously did not explicitly define nullability. Thisprovides better Kotlin interoperability, as well as better static nullchecking for anyone using Java null checking frameworks. Similaradditions of @RecentlyNonNull and @RecentlyNullable will beincrementally rolled out in releases of com.google.android.gms artifacts.
reCAPTCHA Enterprise APIs,which provide clients with a numeric score, indicating the likelihood that auser is a real person and not part of an automated attack. For moreinformation, refer to thisintegration guide.
For example,GoogleApiAvailability#makeGooglePlayServicesAvailablenow returns a @NonNull Task so that the Kotlin compiler treats it asnon-null instead of aplatform type.However, the Activity parameter passed to it is not marked @NonNull(even though it is effectively non-null) so that this change does not breakKotlin code that passes in an Activity?.
Issue - We have received reports that the v21.1.0 release of theFirebase Android SDK for Cloud Firestore can trigger an uncaught exception.Consequently, this issue also affects the Firebase BoM v22.2.0 release. Makesure to update to the next version of the Cloud Firestore SDK or Firebase BoMto get the fix.
Google Analytics for Firebase, Firebase App Indexing, FirebaseAuthentication, Cloud Firestore, Cloud Functions for Firebase (client),Firebase Cloud Messaging, Cloud Storage for Firebase, Firebase DynamicLinks, Firebase Invites, Firebase ML Kit, Firebase Performance MonitoringFirebase Realtime Database, Firebase Remote Config, Firebase A/B Testing,and Firebase Instance IDs SDKs
d3342ee215