Glide 4.1.0

This is the August release of Glide.

Bug fixes

• Fixed a bug where options applied in GlideExtensions could be ignored if the extension option was applied to a RequestOptions object that had autoClone() enabled (b39a9db)
• Fixed an issue default options set in RequestManager could be ignored if autoClone() was enabled (d717e83)
• Fixed double logging parts of GlideExceptions (9d7b8d9)
• Fixed a bug where DiskCacheStrategy.ALL and DiskCachceStrategy.RESOURCE when used while loading a GIF might lead to a partial or invalid cache file (1594655)
• Fixed a concurrent modification exception in ViewTarget (cac7192)
• Fixed an error attempting to load files more than Integer.MAX_VALUE in length (#2240, 8fac123)
• Fixed an issue with using cross fades in RecyclerView (06aced3).
• Clarified nullability of properties in DataFetcher (#2203, thanks to @Tolriq)

Features

• Removed the BitmapPool by default from low ram devices on O+ and decreased the default BitmapPool size on O+ (bb5c391)
• Added support for Bitmap.Config.HARDWARE in Android O+.
  See note below for behavior changes. (d83de42)
• Expose the entry count to subclasses of LruCache (a2a695f, thanks to @loran)
• Target Android API 26 (cea1cce)
• Added support for loading a contact thumbnail by phone number (#2233, thanks to @dstefanox)
• Added a method to GlideBuilder so users can set default Transitions (#2182, 0b99260)
• Added a method to set network timeouts for Glide's default networking library (3e5527e)
• Automatically register Glide for ComponentCallbacks and ComponentCallbacks2 so applications no longer have to do so manually (6b137c2)
• Avoid restarting in progress or completed requests if the new request is identical to the old one (9d10097, 73a8e01, 0a44cf6, thanks to @Tolriq)
• Added a new shortcut method for applying multiple transformations (#2138, thanks to @realdeadfish)

Build changes

• Updated to Gradle 4.1 (0310656, thanks to @jaredsburrows)

API/Behavior changes:

1. After 9d10097, if you attempt to start a request that is exactly the same as the request already in progress for a given View or Target, your new request will be ignored and the old request will be allowed to complete. If you need to override this behavior, you can do so by manually calling clear() on the View or Target before starting your new load. Consider filing an issue if you encounter a problem with this feature.
2. After 06aced3, Glide will always use a TransitionDrawable to run the cross fade transition. Previously cross fade would use a ViewAnimation for the first image in a request to complete and only use TransitionDrawables for animating from thumbnails to full images. RecyclerView does not handle ViewAnimations run outside of its item animator so we've removed the use of ViewAnimation. As a result, if you use views like CircularImageView that can't handle animated Drawables, you may see a change in behavior. Consider using a ViewAnimation based Transition instead of a cross fade if you're not loading in a RecyclerView or file a new issue if you encounter a situation where neither cross fade nor a ViewAnimation will work.
3. After d83de42, setting DecodeFormat.ARGB_8888 or DecodeFormat.RGB_565 will cause Glide to attempt to decode Bitmaps using Bitmap.Config.HARDWARE. Hardware Bitmaps are more memory efficient, but can't be drawn in software and don't expose their pixels so methods like getPixel() will throw an exception, as will attempting to draw a hardware bitmap to a Canvas. You can avoid using Hardware Bitmaps for an individual request by calling RequestOptions#disallowHardwareConfig. You can also disallow hardware configurations for your entire application by passing in RequestOptions into GlideBuilder in your AppGlideModule.