MS-989 SimFace in dev builds only#1203
Conversation
| if (version == rocV3BioSdk.version) rocV3BioSdk else rocV1BioSdk | ||
| } | ||
| FaceConfiguration.BioSdk.SIM_FACE -> resolveSimFaceVersionUseCase() | ||
| FaceConfiguration.BioSdk.RANK_ONE -> resolveRankOneVersionUseCase() |
There was a problem hiding this comment.
It's a matter of preference but do we really need to extract something as simple as the version resolving? It seems the overhead is higher than the code itself.
There was a problem hiding this comment.
It is not necessary, but it has the benefit of isolating each SDK's logic.
Honestly, I was just trying a lot of things to minimise the amount of classes that we would need to duplicate per build type and this is a by-product of the experimentation. We can simplify it when the need for build types is gone.
BurningAXE
left a comment
There was a problem hiding this comment.
Awesome that we won't inflate release size needlessly!
974b4a4 to
6167762
Compare
7b69efe to
fa6a305
Compare
6167762 to
76fc303
Compare
fa6a305 to
ae4e39e
Compare
76fc303 to
7f07880
Compare
7f07880 to
be324d3
Compare
ae4e39e to
659fe32
Compare
|



JIRA ticket
Will be released in: 2025.2.0
Notable changes
simFacefield in the config should only be provided to dev projects by the backend, so there is little to no risk of it affecting the release build. The code itself does not add any noticeable difference in the APK file.APK breakdown
Both APKs were generated from the same code/commit:
Testing guidance
Additional work checklist