HttpImageSource's ImageSourceState.Ready fires twice

I’ve only ecountered whith using HttpImageSource, probably other ImageSource’s are affected as well.

Do you mean that ImageSource.Changed fires twice with ImageSource.State having the value ImageSourceState.Ready?

If so, I don’t think this is a bug; there’s nothing promising to only fire ImageSource.Changed only on ImageSource.State-changes…

That being said, I can see from the code that there’s a redundant call to ImageSource.OnChanged(), which would trigger ImageSource.Changed an extra time when updating the image. I’ll look into getting rid of this, but they might be there for a good reason…

Yes, exactly. I’m relying on the ImageSourceState.Ready state – however it’s not hard to filter out redundant state changes on the app side. Thanks for the swift reply!