#2438 improve handling of invalid keys on message compose

[ioanmo226]

This PR improved handling of invalid keys on message compose(Refresh EKM keys for invalid keys on message screen)

close #2438 // if this PR closes an issue

---

Tests (delete all except exactly one):

• Tests added or updated

---

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

• addresses the issue it closes (if any)
• code is readable and understandable
• is accompanied with tests, or tests are not needed
• is free of vulnerabilities
• is documented clearly and usefully, or doesn't need documentation

[ioanmo226]

@sosnovsky Could you check in your local if below semaphoreci issue also occurs in your local?
It works fine in my local though. Only semaphoreci.

2023-12-01T05:55:10.621Z ERROR @wdio/config:ConfigParser: Failed loading configuration file: file:///Users/semaphore/git/flowcrypt-ios/appium/config/wdio.mock.conf.ts: Cannot use import statement outside a module
/Users/semaphore/git/flowcrypt-ios/appium/config/wdio.mock.conf.ts:100:05
import { join } from 'path';

[sosnovsky]

@sosnovsky Could you check in your local if below semaphoreci issue also occurs in your local? It works fine in my local though. Only semaphoreci.

Works well locally for me too.
Semaphore issue can be caused by different node.js version there, maybe they changed it recently, so setting node version explicitly in semaphore.yml should fix this issue.

[ioanmo226]

I think we set to correct node v18 in semaphoreci?

flowcrypt-ios/.semaphore/semaphore.yml

Line 81 in 6fd5696

- sem-version node 18 && cache restore appium-npm && cd ./appium && npm i && cd .. && cache store appium-npm appium/node_modules

[sosnovsky]

I think we set to correct node v18 in semaphoreci?

I checked your previous PR (where tests were passing) and Semaphore used node 18.18.2 there, while this PR uses node 18.19.0, so looks like there is some changes in this node update which broke tests code.

You can try to use node v20 on semaphore, to check if it fixes issue.

[ioanmo226]

Yep!
Seems like v18.19.0 is not stable and when I change it to v20, it works fine.

[ioanmo226]

Thank you for your assistant

[sosnovsky]

Works great now, thanks!