Releases: Azure/azure-storage-android
Releases · Azure/azure-storage-android
Android Storage Client Library 0.4.0
- Deprecated getSubDirectoryReference() for blob directories and file directories. Use getDirectoryReference() instead.
- Fixed a bug where maxResults was not verified to be positive for list operations.
- Deprecated AuthenticationScheme and its getter and setter. In the future only SharedKey will be used.
- Added support for EndpointSuffix which was previously not accepted in Account Strings.
- Fixed a bug where high precision Date values stored on Table Entites were forced to fit into milliseconds resulting in inaccuracies. Precision is limited to 1 millisecond by the Android Date class. If greater precision is required, the String should be used directly.
- Added TableRequestOptions.dateBackwardCompatibility, which supports reading Date values on Table Entities written using versions of this library prior to 0.4.0. See http://go.microsoft.com/fwlink/?LinkId=523753 for more details.
Android Storage Client Library 0.3.1
Fixed a bug where a NullPointerException was thrown instead of a NetworkOnMainThreadException if code was executed on the main thread.
Android Storage Client Library 0.3.0
- Added the NameValidator class which contains helpers that check to see if resource names are valid.
- Fixed a bug where the RequestUrl of a LogRecord was not correctly HTML4 decoded.
- Made FileRange class and ListFilesAndDirectories method in the CloudFileDirectory class public.
Release 0.2.1
Fixed aar packaging issue.
Release 0.2.0
- Added File Service support. The File Service and the associated SDK APIs are in preview.
- Added CloudAnalyticsClient and related methods to simplify Storage Analytics logging and metrics use case scenarios.
- Fixed a bug where an empty file would be left over during the downloadToFile error case.
- Updated StorageErrorCodeStrings class.
- Requests made using SAS credentials have the api-version query parameter appended to the URI.
- Fixed a null pointer exception that resulted when the first request was made with a blob created using the uri-only constructor (no sas creds appended).