NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #2075 most downloaded on NuGet
Transformations for FFImageLoading library. - BlurredTransformation - CircleTransformation, RoundedTransformation, CornersTransformation, CropTransformation - ColorSpaceTransformation, GrayscaleTransformation, SepiaTransformation, TintTransformation - FlipTransformation, RotateTransformation - Supports custom transformations (native platform `ITransformation` implementations) These transformations can be consumed from FFImageLoading and FFImageLoading.Forms (Xamarin Forms). Don't forget to add the package in all platform specific projects. This way the correct native implementation is injected.
Latest stable
2.3.6
Last release 8 years ago
no release in 18 months
Release timing varies
gaps range from 8 days to 5 months
Most releases are documented
notes for 34 of 51 stable releases
143 versions withdrawn
withdrawn after publishing
127 years old
195 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.3.5...v2.3.6
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.3.5...v2.3.6
CachedImage to always fill entire space available (different behaviour than Image). It's now fixed. You can get old behaviour with CachedImage.FixedOnMeasureBehavior = false; (static property)CachedImageRenderer.Init(enableFastRenderer: [true/false])Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.3.3...v2.3.4
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.3.3...v2.3.4
CachedImage to always fill entire space available (different behaviour than Image). It's now fixed. You can get old behaviour with CachedImage.FixedOnMeasureBehavior = false; (static property)CachedImage.FixedAndroidMotionEventHandler = false if experiencing any gesture recognizers problems on Android. (static property)CachedImageRenderer.Init(enableFastRenderer: [true/false])Nothing published for this version
Nothing published for this version
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.3.2...v2.3.3
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.3.2...v2.3.3
CachedImage to always fill entire space available (different behaviour than Image). It's now fixed. You can get old behaviour with CachedImage.FixedOnMeasureBehavior = false; (static property)CachedImage.FixedAndroidMotionEventHandler = false if experiencing any gesture recognizers problems on Android. (static property)CachedImageRenderer.Init(enableFastRenderer: [true/false])Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.3.1...v2.3.2
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.3.1...v2.3.2
CachedImage to always fill entire space available (different behaviour than Image). It's now fixed. You can get old behaviour with CachedImage.FixedOnMeasureBehavior = false; (static property)CachedImage.FixedAndroidMotionEventHandler = false if experiencing any gesture recognizers problems on Android. (static property)CachedImageRenderer.Init(enableFastRenderer: [true/false])ReplaceStringMap - added regex replace support, wiki: https://github.com/luberda-molinet/FFImageLoading/wiki/SVG-support#svg-string-replacement-including-colorsNothing published for this version
Nothing published for this version
Nothing published for this version
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.25...v2.3.1
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.25...v2.3.1
The same as 2.3.0 + fixed nuspec issue with WebP
CachedImage to always fill entire space available (different behaviour than Image). It's now fixed. You can get old behaviour with CachedImage.FixedOnMeasureBehavior = false; (static property)CachedImage.FixedAndroidMotionEventHandler = false if experiencing any gesture recognizers problems on Android. (static property)CachedImageRenderer.Init(enableFastRenderer: [true/false])Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.25...v2.3.0
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.25...v2.3.0
CachedImage to always fill entire space available (different behaviour than Image). It's now fixed. You can get old behaviour with CachedImage.FixedOnMeasureBehavior = false; (static property)CachedImage.FixedAndroidMotionEventHandler = false if experiencing any gesture recognizers problems on Android. (static property)CachedImageRenderer.Init(enableFastRenderer: [true/false])Nothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.24...v2.2.25
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
Xamarin.Forms (Android) now uses fast renderers by default if possible (correct XF version). You can enable / disable fast renderers by CachedImageRenderer.Init(enableFastRenderer: [true/false] override.
resource:// TypeConverter not working from viewmodelsFFImageLoading.Platform could not be resolved because it was built against the ".NETPortable,Version=v5.0" frameworkNothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.23...v2.2.24
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
Xamarin.Forms (Android) now uses fast renderers by default if possible (correct XF version). You can enable / disable fast renderers by CachedImageRenderer.Init(enableFastRenderer: [true/false] override.
Nothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.22...v2.2.23
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
Xamarin.Forms (Android) now uses fast renderers by default if possible (correct XF version). You can enable / disable fast renderers by CachedImageRenderer.Init(enableFastRenderer: [true/false] override.
ToLower with ToLowerInvariant #792Nothing published for this version
Nothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.21...v2.2.22
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.20...v2.2.21
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
ImageService.EnableMockImageService = trueSvgCachedImage.Init() method (to avoid linking problems)FadeAnimationDuration / FadeAnimationForCachedImages for CachedImage viewsPreserveAtrributes to prevent linking issuesMainThreadDispatcher regression which caused images to not appearSvgDataResolver not working when using in PCL project (missing constructor)AsJPGStreamAsync doesn't ignore quality parameterNothing published for this version
Nothing published for this version
Nothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.19...v2.2.20
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
NullReferenceException)It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.18...v2.2.19
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Also for Xamarin.Forms >= 2.4 please set: CachedImage.FixedAndroidMotionEventHandler = true if experiencing any gesture recognizers problems on Android.
I'll include it as a default in next major version.
Nothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.16...v2.2.17
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.15...v2.2.16
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
MvxCachedImageView/MvxSvgCachedImageView for Windows (Preview)CachedImage.FixedAndroidMotionEventHandler propertyNothing published for this version
Nothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.14...v2.2.15
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Nothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.13...v2.2.14
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
DownsampleToViewSize failed scenario: DownsampleToViewSize failed - view is expandable in both dimensions, so it doesn't have a size. Please use DownsampleWidth or DownsampleHeight property.. Read more here: linkIt's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.11...v2.2.13
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.11...v2.2.12
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Nothing published for this version
Nothing published for this version
It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can…
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.10...v2.2.11
FFImageLoading has a regression since 2.2.4 which caused CachedImage to always to fill entire space available (different behaviour than Image. It's now fixed, but as it was included in many versions it may be a breaking change for some. That's why I didn't enable that fix by default. You can do it manually with:
CachedImage.FixedOnMeasureBehavior = true;
I'll include it as a default in next major version.
Read more here: https://github.com/luberda-molinet/FFImageLoading/issues/545
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.9...v2.2.10
Complete history of changes available here: https://github.com/luberda-molinet/FFImageLoading/compare/v2.2.9...v2.2.10
Xamarin.Forms: New SvgCachedImage view.MvxCachedImageView / MvxSvgCachedImageView views. (MvxImageLoadingView is now obsolete)ReplaceStringMap for SVG parsing (eg. changing colors)ITransformation interface refactorings to allow more advanced scenariosSetupOnBeforeImageLoading virtual method to CachedImage/MvxCachedImageView for advanced use-casesEmbeddedResourceImageSource for a better performance resource files loadingThis release contains many issues fixes (bugs, deadlocks, etc). Some of them:
MD5CryptoServiceProvider is not thread safeTaskCanceledException will crash the applicationErrorPlaceHolder ErrorCommand not working on AndroidNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.