[iOS][isVisible:false rendering issue] [Rendering of hidden components conflicts with animations]

Platform

What platform is your issue or question related to? (Delete other platforms).

• iOS

Author or host

Host - Teams iOS client

Version of SDK

latest main

Details

Suppose you have a hidden element in the card (set using isVisible:false tag). If the render function is called using an animation, it results in the hidden components being visible on the device/simulator. (This could be a potential Apple issue as well).

Repro steps: In ViewController wrap the code for adaptive card rendering with this animation block:

[UIView animateWithDuration:0 animations:^{​​
        renderResult = [ACRRenderer render:cardParseResult.card
                                    config:hostconfigParseResult.config
                           widthConstraint:kAdaptiveCardsWidth
                                  delegate:self];
    }​​];

CardJson:

{
  "body": [
    {
      "separator": true,
      "text": "Please select an item from the list.",
      "weight": "bolder",
      "type": "TextBlock",
      "spacing": "none"
    },
    {
      "items": [
        {
          "separator": true,
          "text": "PAGE 1 of 3. Showing results 1-4 of 11 ",
          "weight": "bolder",
          "type": "TextBlock",
          "spacing": "none"
        }
      ],
      "id": "page1",
      "type": "Container"
    },
    {
      "id": "page2",
      "isVisible": false,
      "items":[
        {
          "separator": true,
          "text": "PAGE 2 of 3. Showing results 5-8 of 11 ",
          "weight": "bolder",
          "type": "TextBlock",
          "spacing": "none"
        }
      ],
      "type": "Container"
    }
  ],
  "type": "AdaptiveCard",
  "version": "1.2"
}

Screenshot of the issue:

Correct Behaviour:

Please let me know if you need more details.

[jwoo-msft]

Hi @adumrewal,

I haven’t tried all of the enumeration’s values but the ones I tried such as UITableViewRowAnimationTop, UITableViewRowAnimationBottom and etc, all worked as expected. c.c. @lindach167

[jwoo-msft]

@shalinijoshi19,

I have discussed this issue with @adumrewal. It’s possible that it’s an Apple issue. I’m going to repro the issue first. I will update the thread once I’m done with accessibility issues.