appium doesn't see send button until scrolled down

[tomholub]

This is interesting - the create email button always hovers in the same space. Why is it needed to scroll down before we can tap it? (in actual app, I don't need to scroll to see/tap the button)

Originally posted by @tomholub in #1065 (comment)

[tomholub]

[ivan-ushakov]

Possible linked with issue #1079

[tomholub]

From my testing, it seemed unrelated. Regardless of loading status, it didn't seem to recognize the send button until I scroll a bit lower. But only if there was more than one page worth of emails (with only a few emails, no problem).

It's as if the additional inbox items obscure the button somehow. Even though visually they don't.

[tomholub]

@sosnovsky maybe you would know?

[tomholub]

I observed it here: https://flowcrypt.semaphoreci.com/jobs/0026251b-48ef-4b3a-8b8d-1587e778380f

[0-2] Screenshot of failed test was saved to /Users/semaphore/git/flowcrypt-ios/appium/tmp 11:55
[0-2] Error in "COMPOSE EMAIL:  user is able to send encrypted email after resetting pass phrase" 11:55
Error: element ("-ios class chain:**/XCUIElementTypeButton[`label == "+"`]") still not displayed after 15000ms 11:55
    at async InboxScreen.checkInboxScreen (/Users/semaphore/git/flowcrypt-ios/appium/tests/screenobjects/inbox.screen.ts:40:5) 11:55
    at async UserContext.<anonymous> (/Users/semaphore/git/flowcrypt-ios/appium/tests/specs/composeEmail/SendEncryptedEmailAfterWrongPassPhrase.spec.ts:41:5) 11:56
[0-2] RETRYING in /Users/semaphore/git/flowcrypt-ios/appium/FlowCrypt.app - /tests/specs/composeEmail/SendEncryptedEmailAfterWrongPassPhrase.spec.ts 12:04
[0-2] RUNNING in /Users/semaphore/git/flowcrypt-ios/appium/FlowCrypt.app - /tests/specs/composeEmail/SendEncryptedEmailAfterWrongPassPhrase.spec.ts 14:11
[0-2] addedRecipientEl value:   demo@flowcrypt.com  14:11
[0-2] Screenshot of failed test was saved to /Users/semaphore/git/flowcrypt-ios/appium/tmp 14:11
[0-2] Error in "COMPOSE EMAIL:  user is able to send encrypted email after resetting pass phrase" 14:11
Error: element ("-ios class chain:**/XCUIElementTypeButton[`label == "+"`]") still not displayed after 15000ms 14:11
    at async InboxScreen.checkInboxScreen (/Users/semaphore/git/flowcrypt-ios/appium/tests/screenobjects/inbox.screen.ts:40:5) 14:11
    at async UserContext.<anonymous> (/Users/semaphore/git/flowcrypt-ios/appium/tests/specs/composeEmail/SendEncryptedEmailAfterWrongPassPhrase.spec.ts:41:5)

[sosnovsky]

Wasn't able to fix this issue yet, but found that compose button becomes non-accessible after tableNode.reloadData() at https://github.com/FlowCrypt/flowcrypt-ios/blob/master/FlowCrypt/Controllers/Inbox/InboxViewController.swift#L271

Maybe Texture re-renders all views on the screen after reloadData and it causes accessibility issues, which are fixed after any gesture (scroll or tap)
Trying to find solution...

[tomholub]

Thanks for looking into this! Were you able to reproduce this manually - compose email button not tappable on the first tap of loading inbox, if there are many messages?

[sosnovsky]

No, it works well for me in the app, fails only during ui tests

[tomholub]

So far, do you think this is fixable (with reasonable effort) ?

[sosnovsky]

It seems there is no simple way to make compose button work without scroll - I tried different methods (like adding zPosition to button, enabling/disabling button it on data load etc), but only scroll make it work in 100% cases.

Probably there is some issue with Texture rendering accessibility structure for views which are floating above another views. Scrolling down re-renders view and structure is fixed.

So I just updated some selectors there to use accessibility identifiers for faster tests, but haven't found any reliable solution for original issue.

[tomholub]

Got it. Thanks for looking into it 👍