RNMT-3824 Errors in the first reads/writes of a Key Store when multiple initializations run simultaneously

[usernuno]

Description

Reverts the previous fix. Raises the used version of the Key Store Plugin.

Context

Fixes https://outsystemsrd.atlassian.net/browse/RNMT-3824

This commit raises the used version of the Key Store Plugin. It mostly does not affect this plugin, but we should raise this to the latest version available.

Type of changes

• [ ] Feature (change which adds functionality)
  • [ ] BREAKING CHANGE (existing functionality will not work as expected due to new feature)
• [x] Fix (change which fixes an issue)
  • [ ] BREAKING CHANGE (existing functionality will not work as expected due to fix)
• [ ] Performance (change which improves performance)
  • [ ] BREAKING CHANGE (existing functionality will not work as expected due to performance improvement)
• [ ] Refactor (non-breaking change that is neither feature, fix nor performance)
• [ ] Style (non-breaking change that only affects formatting and/or white-space)

Components affected

• [x] Android platform
• [ ] iOS platform
• [ ] JavaScript
• [ ] OutSystems

Tests

Manual tests were performed

Screenshots (if appropriate)

Checklist

• [x] Pull request title follows the format RNMT-XXXX <title>
• [ ] Tests have been created
• [x] Code follows code style of this project
• [x] CHANGELOG.md file is correctly updated
• [ ] Changes require an update to the documentation
  • [ ] Documentation has been updated accordingly

[cmfsotelo]

Comming late to the party, but, can you give more context on the why of the revert commit?

[usernuno]

Comming late to the party, but, can you give more context on the why of the revert commit?

We reverted the fix in this plugin and the Key Store Plugin because we don't want the experience to be the current one. If possible we intend to remove the lock screen popup during the app (it only appears in Android 10 due to the new used intent).

The fix was essentially enforcing that the lock screen was actually correctly authenticated. Since we intend to remove the lock screen, that version was not released. To release a new one we needed to revert the change.

There is already an issue in the backlog to tackle the experience.