AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Android sdk 269/25/2023 ![]() ![]() Resolved proguard issue that caused OpeningHours.Builder andĪ() to be stripped from the AAR,Īnd () to not be stripped from the AAR.Removed Maven dependency on Guava resulting in reduced app size.Improved model class validation (e.g OpeningHours.getWeekdayText() may not.Added support for AddressComponents to the Place object (with the exception.minSDKVersion is increased from 14 to 16.Dependency on Glide has been removed, resulting in a smaller APK size.User types in extra whitespace (e.g “Google ”). Helps to conserve on network requests by using previously cached responses when Removed, and trailing whitespace will be replaced with a single space. Autocomplete API behavior has changed: All leading whitespace will be.Added (String hint) to allow changing the.Indicating whether the place is currently open. Place.isOpen() and Place.isOpen(long utcTimeMillis) return a boolean.Place.getUtcOffsetMinutes() returns the UTC offset for a place, in.Changed from support library to AndroidX.Javadocs believe it is implemented by the Support Libraries. Our dependency on FragmentFactory is implemented by AndroidX, but our. ![]() Resolved issue where findCurrentPlace may crash when there are too many access.Resolved issue where the autocomplete widget would lose its state onĬonfiguration change, for example, from portrait to landscape layout.Some address components legitimately have no types. Resolved issue where empty AddressComponent types incorrectly threw.AutocompleteSupportFragment setters now return the instance so the settersĬan be chained in a builder-like fashion.AutocompleteSupportFragment.newInstance returns a new autocomplete.Added ability to create AutocompleteSupportFragment programmatically with a.Place Autocomplete now supports filtering by multiple countries.Supported prediction, based on the specified origin (LatLng) in programmatic Place Autocomplete response now returns the distance in meters from each.Place Autocomplete now supports plus codes.Fixes an issue where the autocomplete search box would unexpectedly clear.ĪpPlus code support in Place Autocomplete.Added getters to request builders and model builders, for better Kotlin.Fixed a bug where the Autocomplete widget was resetting the text query in.Volley dependency updated to 1.2.1 in observation of the sunset of JCenter.Autocomplete widgets now have debouncing when typing quickly.Interoperability and better static null checking for apps that use Java null Will cause warnings on null safety violations, and provides better Kotlin ( iconBackgroundColor and iconURL) to allow for rendering icons that The minimum supported OS for new versions of your app. In your application's build dependencies in order to control when you raise Will continue to work on devices running Android API Level 25 and below. Quarter of 2022 will only support devices running a minimum ofĪpp versions built with v2.x or lower of the Places SDK for Android Places SDK for Android versions released beginning in the third Places SDK for Android beginning in the third quarter of 2022. In response to changes in our internal dependencies, Android API Level 23,Ģ4, and 25 (Android 6, 7.0 and 7.1) will not be supported in new versions of the OctoFreezing support for API Level 23, 24 and 25 Will not be supported above Version 2.6.0. To use the Places SDK for Android directly before the release of If you are using the compatibility library to access Places SDK for Androidįeatures or data, we recommend that you follow the The equivalent Places SDK for Android compatibility library. Places SDK for Android Version 2.6.0 is the last version that supports Places.isOpen() assumes that the business is operational. If _STATUS was not requested or is unavailable, Value of CLOSED_PERMANENTLY or CLOSED_TEMPORARILY, Places.isOpen() returnsįalse. If the returned Place object contains _STATUS with a To ensure accurate results from the Place.isOpen() method, request the If you omit Locale, then it uses the device's locale. 122841340: When you call Places.initialize(Context, String, Locale) and the specified Locale is different from the device's locale, the autocomplete widget now localizes both the search hint and the search results based on the setting of Locale. ![]()
0 Comments
Read More
Leave a Reply. |