fix: optimize getCipherStorageForCurrentAPILevel method #457
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I reordered the execution of the instructions to optimize the getCipherStorageForCurrentAPILevel method.
In the case of isBiometry = false it is useless to execute the getCapabilityLevel method which can be calculated in case the RSA private key is missing.
I realized this because not using the warm up, the first de-encryption was still very slow due to this particular.
Furthermore, this re-order does not cause problems for the warm up because it is valued there with isBiometry = true.