Update the expectations of the tests now that the clearContents behavior is corrected.

Author: Scott Goodson

AsyncDisplayKit/ASDisplayNode.mm

@@ -1770,6 +1770,10 @@ - (void)setInterfaceState:(ASInterfaceState)newState
     // Trigger asynchronous measurement if it is not already cached or being calculated.
   }
 
+  // For the FetchData and Display ranges, we don't want to call -clear* if not being managed by a range controller.
+  // Otherwise we get flashing behavior from normal UIKit manipulations like navigation controller push / pop.
+  // Still, the interfaceState should be updated to the current state of the node; just don't act on the transition.
+  
   // Entered or exited data loading state.
   if ((newState & ASInterfaceStateFetchData) != (oldState & ASInterfaceStateFetchData)) {
     if (newState & ASInterfaceStateFetchData) {

AsyncDisplayKitTests/ASDisplayNodeTests.m

@@ -1702,7 +1702,11 @@ - (void)testInterfaceStateForNonCellNode
   XCTAssert(node.interfaceState == ASInterfaceStateInHierarchy);
 
   [node.view removeFromSuperview];
-  XCTAssert(!node.hasFetchedData);
+  // We don't want to call -clearFetchedData on nodes that aren't being managed by a range controller.
+  // Otherwise we get flashing behavior from normal UIKit manipulations like navigation controller push / pop.
+  // Still, the interfaceState should be None to reflect the current state of the node.
+  // We just don't proactively clear contents or fetched data for this state transition.
+  XCTAssert(node.hasFetchedData);
   XCTAssert(node.interfaceState == ASInterfaceStateNone);
 }