appium: CheckSettingsForLoggedUser.spec failed

[ivan-ushakov]

Output:

[iPhone Simulator iOS 15.0 #0-6] Spec: /Users/ivan/Documents/Projects/FlowCrypt/flowcrypt-ios/appium/tests/specs/settings/CheckSettingsForLoggedUser.spec.ts
[iPhone Simulator iOS 15.0 #0-6] Running: iPhone Simulator on iOS 15.0 executing /Users/ivan/Library/Developer/Xcode/DerivedData/FlowCrypt-dkmvlhcprnebshbeurvkormazmnk/Build/Products/Debug-iphonesimulator/FlowCrypt.app
[iPhone Simulator iOS 15.0 #0-6] Session ID: 964b1378-4733-470c-b903-822fa3e667fe
[iPhone Simulator iOS 15.0 #0-6]
[iPhone Simulator iOS 15.0 #0-6] SETTINGS: 
[iPhone Simulator iOS 15.0 #0-6]    ✖ user should see public key and should not see private key
[iPhone Simulator iOS 15.0 #0-6]
[iPhone Simulator iOS 15.0 #0-6] 1 failing (1m 0.6s)
[iPhone Simulator iOS 15.0 #0-6]
[iPhone Simulator iOS 15.0 #0-6] 1) SETTINGS:  user should see public key and should not see private key
[iPhone Simulator iOS 15.0 #0-6] Error: element ("~Show public key") still not displayed after 15000ms
[iPhone Simulator iOS 15.0 #0-6] Error: element ("~Show public key") still not displayed after 15000ms
[iPhone Simulator iOS 15.0 #0-6]     at processTicksAndRejections (internal/process/task_queues.js:93:5)
[iPhone Simulator iOS 15.0 #0-6]     at KeysScreen.checkSelectedKeyScreen (/Users/ivan/Documents/Projects/FlowCrypt/flowcrypt-ios/appium/tests/screenobjects/keys.screen.ts:79:34)
[iPhone Simulator iOS 15.0 #0-6]     at UserContext.<anonymous> (/Users/ivan/Documents/Projects/FlowCrypt/flowcrypt-ios/appium/tests/specs/settings/CheckSettingsForLoggedUser.spec.ts:29:20)

For some reason we can not read keys from storage

[tomholub]

Is this on master?

[ivan-ushakov]

Is this on master?

This happens on issue-852-no-prv-found branch

[tomholub]

@ivan-ushakov would you want @sosnovsky to debug this further? He has his hands empty now. In fact @sosnovsky I also wanted your review on this PR, it's huge.

[sosnovsky]

I compiled app from the latest code of issue-852-no-prv-found branch and this test passes there without any issues

Maybe it was fixed by today's PR code updates?

[tomholub]

Yes - Ivan ended up fixing it yesterday in the same PR.