Bug 24055 - ScaleTo acts different on iOS and Android
Summary: ScaleTo acts different on iOS and Android
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.3
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-10-25 20:57 UTC by Ryan Hatfield
Modified: 2015-02-13 15:55 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Ryan Hatfield 2014-10-25 20:57:26 UTC
Running simple ScaleTo on iOS and Android, using the same Shared forms code..

On iOS ScaleTo origin is CenterX CenterY

on Android ScaleTo origin is 0,0 (top left)

I can submit a simple test case later if needed, my project is rather complex and I've been going around this with Device.OnPlatform code, I figured I should report it.

I'm using Mac for iOS and Android and also occasionally Windows and Visual Studio for Android.

Xamarin.Forms version
Comment 1 Udham Singh 2014-10-27 08:31:03 UTC
Hi Ryan,

Could you please attach your test project and Xamarin build info via Xamarin studio->About XS->Show Details, so we can try to reproduce this issue at our end.

Comment 2 Jason Smith [MSFT] 2015-02-13 15:55:45 UTC
This should be resolved in latest Xamarin.Forms