New issue
Advanced search Search tips

Issue 843300 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Bug



Sign in to add a comment

EarlGrey: Exception is thrown when UIViewPropertyAnimators are started and stopped within same runloop

Project Member Reported by kkhorimoto@chromium.org, May 15 2018

Issue description

EarlGrey swizzles out |-animationDidStart:| and |-animationDidStop:| using custom implementations that provide hooks to drive EG animation synchronization code.  These swizzled methods call AnimationDidStart() and AnimationDidStop() in GREYCAAnimationDelegate.m, which in turn calls the category method |-grey_setAnimationState:| on the CAAnimation provided.

When a UIViewPropertyAnimator is started and stopped within the same runloop, however, the CAAnimation is actually an instance of NSNull, so an exception is thrown because the |-grey_setAnimationState:| function is not available.  AnimationDid[Start/Stop]() should be updated to check whether |animation| is NSNull before attempting this call.
 
Owner: linds...@chromium.org
We need to roll in EarlGrey's newest versions for this bug.  Lindsay I'll assign this bug to you as this should be fixed by rolling EG.  Feel free to re-triage.

Sign in to add a comment