Bug 27125 - Continue with using AnimationExtensions stops working
Summary: Continue with using AnimationExtensions stops working
Status: RESOLVED INVALID
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.3
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-02-17 04:35 UTC by Johan Karlsson
Modified: 2015-03-05 06:59 UTC (History)
4 users (show)

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


Attachments
Reprod sample project (173.88 KB, application/zip)
2015-02-17 04:35 UTC, Johan Karlsson
Details


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:
Status:
RESOLVED INVALID

Description Johan Karlsson 2015-02-17 04:35:59 UTC
Created attachment 9866 [details]
Reprod sample project

When using ContinueWith to string animations together it only works one time. The second time the same animation is triggered it gets stuck after the first part.

Reprod:

1. Unzip attachment and open project
2. Run the iOS-version
3. Click button once
4. Animation plays as suspected (Scale in, Scale out)
5. Click button again
6. Animation gets stuck after Scale Out
Comment 1 Ram Chandra 2015-02-17 05:55:28 UTC
I have checked this issue and with the help of attached project I am able to reproduce this issue at our end.

Screencast: (Android)   http://www.screencast.com/t/k36pPFMvBKoP
                   (Windows)  http://www.screencast.com/t/yPo1bJrR

Application output: https://gist.github.com/saurabh360/a11e4ac8ffbc220f3aae
IDE logs: https://gist.github.com/saurabh360/374f98edaf4edc893b1c

Additional Info: I am getting same behavior for both android and iOS.

Environment Info:

Xamarin.Forms: 1.3.4.6331-pre4

=== Xamarin Studio ===

Version 5.7.1 (build 17)
Installation UUID: 6ea47b0d-1852-4aaf-808d-373ff0a5002b
Runtime:
	Mono 3.12.0 ((detached/a813491)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 312000068

=== Apple Developer Tools ===

Xcode 6.1 (6604)
Build 6A1052d

=== Xamarin.iOS ===

Version: 8.6.2.19 (Business Edition)
Hash: d508c8e
Branch: 
Build date: 2015-02-15 22:17:46-0500

=== Xamarin.Android ===

Version: 4.20.0.28 (Business Edition)
Android SDK: /Users/jatin66/Desktop/Backup/android-sdk-macosx
	Supported Android versions:
		1.6    (API level 4)
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin.Mac ===

Version: 1.11.0.1 (Business Edition)

=== Build Information ===

Release ID: 507010017
Git revision: 0bc7d3550b6b088ac25b08dcf7bbe73bcc8658b3
Build date: 2015-02-03 19:43:29-05
Xamarin addins: f7b7d34419c9ec24501bfa7c658e80a6305613e0

=== Operating System ===

Mac OS X 10.10.0
Darwin Jatin66s-iMac.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 2 Jason Smith [MSFT] 2015-03-05 06:59:25 UTC
The code is wrong.

await theButton.ScaleTo(3).ContinueWith((a) => theButton.ScaleTo(1) ); essentially is triggering the second animation on (potentially) a background thread because of the combination of await and continue with.

instead write this as:

await theButton.ScaleTo (3);
await theButton.ScaleTo (1);