Originally created by @b-raines on GitHub (Apr 11, 2016).
When looping through window.subviews the next responder object for the 2 subviews returned were both windows (instead of a UIViewController). Moved call to showPrompt() to a different area as a temporary solution.
Call to #userDidSignificantEvent was taking place upon dismissing an AVPlayerViewController which was presented modally over a UIPageViewController (that was embedded within a UINavigationController).
I didn't spend too much time diagnosing this, but my assumption is that the presented view controller had not been fully dismissed yet, causing the unexpected behavior... If I have time later, I'll try to dig in and determine if that was actually the cause.
Originally created by @b-raines on GitHub (Apr 11, 2016).
When looping through `window.subviews` the next responder object for the 2 subviews returned were both windows (instead of a UIViewController). Moved call to `showPrompt()` to a different area as a temporary solution.
Call to #userDidSignificantEvent was taking place upon dismissing an AVPlayerViewController which was presented modally over a UIPageViewController (that was embedded within a UINavigationController).
I didn't spend too much time diagnosing this, but my assumption is that the presented view controller had not been fully dismissed yet, causing the unexpected behavior... If I have time later, I'll try to dig in and determine if that was actually the cause.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @b-raines on GitHub (Apr 11, 2016).
When looping through
window.subviewsthe next responder object for the 2 subviews returned were both windows (instead of a UIViewController). Moved call toshowPrompt()to a different area as a temporary solution.Call to #userDidSignificantEvent was taking place upon dismissing an AVPlayerViewController which was presented modally over a UIPageViewController (that was embedded within a UINavigationController).
I didn't spend too much time diagnosing this, but my assumption is that the presented view controller had not been fully dismissed yet, causing the unexpected behavior... If I have time later, I'll try to dig in and determine if that was actually the cause.