# Android Registration Client v1.0.1 **Release Name**: Android Registration Client v1.0.1 **Release version**: 1.0.1 **Support**: Beta Release **Release Date**: 10th April, 2026 ### **Overview** Android Registration Client v1.0.1 introduces significant improvements to system flexibility, auditability, and security. This release focuses on three key areas: enhanced configurability that reduces hardcoded values for easier deployment across different environments, comprehensive audit logging for improved transparency and compliance tracking, and operator biometric validation to prevent unauthorized data capture during applicant registration. These enhancements strengthen the system's maintainability, accountability, and data integrity while supporting diverse implementation requirements. 1. **Configurability Improvements:** This release improves configurability by moving several previously fixed system values into configuration settings. As a result, the platform can adapt more easily to different deployment environments and operational requirements without requiring source code changes. With these updates, administrators can easily adjust system behavior through configuration settings, making it quicker to respond to changing needs. This reduces reliance on development teams for minor updates and helps streamline operational workflows. Overall, this improvement increases system flexibility, scalability, and maintainability, ensuring smoother deployments and easier long-term management across diverse implementations. 2. [**Operator Biometric Restriction**](https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-issuance/android-registration-client/overview/features#id-11.-match-sdk)**:** A new validation has been implemented to ensure that an operator’s biometrics are not accepted during applicant registration. This prevents scenarios where operator data could be mistakenly or intentionally captured as part of an applicant’s record. By enforcing this rule, the system ensures that only the applicant’s biometric information is recorded, maintaining the accuracy and authenticity of identity data. This is critical for preserving the integrity of the registration process. This enhancement also strengthens security and compliance by reducing the risk of misuse and aligning with best practices for handling sensitive biometric information. 3. **Audit Enhancements:** Audit logging has been introduced for key system actions and workflows, improving overall transparency and traceability. Critical operations are now recorded, providing clear visibility into system usage and user activities. These logs enable faster debugging and issue resolution by offering a detailed history of events. Teams can track what actions were performed, when they occurred, and by whom, making it easier to identify and resolve problems. In addition, the audit capability supports compliance and governance requirements by ensuring that all significant actions are documented. This strengthens accountability and builds trust in the system. {% hint style="success" %} **Note**: Compatible with[ ](https://docs.mosip.io/1.2.0/releases/release-notes)MOSIP [1.2.0.1](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/release-notes-1.2.0.1) (JAVA 11) {% endhint %} {% hint style="warning" %} **Note**: **NOT** Compatible with MOSIP [v1.2.1.0](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/v1.2.1.0) (JAVA 21) {% endhint %} ### Story Progress & Updates
JIRADescription
RCF-351As an Operator, my biometrics should not be accepted when I am registering an applicant.
RCF-1301We had a few values that were hardcoded which has now made to be configurable.
RCF-1278Editable Cron Job in Scheduled Job Settings.
RCF-1277Audits have been added to be in parity with Desktop Registration Client.
RCF-1275Added syncs and batch jobs.
### Bugs Fixed Below is the list of bug fixes as part of the 1.0.1 release, To get the complete list of bug fixes please refer [**here**](https://mosip.atlassian.net/issues?jql=text%20~%20%22parent%3Drcf-31%20and%20fixVersion%3Drcf-1.0.1%20and%20issuetype%20%3D%20bug%22%20OR%20summary%20~%20%22parent%3Drcf-31%20and%20fixVersion%3Drcf-1.0.1%20and%20issuetype%20%3D%20bug%22%20OR%20\(parent%20%3D%20RCF-31%20AND%20fixVersion%20%3D%20rcf-1.0.1%20AND%20issuetype%20%3D%20Bug\)%20ORDER%20BY%20created%20DESC).
JIRADescription
RCF-1268ARC: While packet creating Threshold values and score values are giving same, continue button is not enable in biometric page.
RCF-1264ARC: In the ARC Smtp Notifications are not displaying for all the packets.
RCF-1256ARC: In the auto logged out, while in the offline mode the warning pop up time start after 5 minutes.
RCF-1254ARC: In the global config settings page all the pop up messages are not getting in logged in languages.
RCF-1251ARC: In the global settings page after changing the local values incorrect prompt message is displaying.
RCF-1249ARC: Device is not getting detected when device status is "busy/not-ready/not-registered" in device settings page.
RCF-1220ARC: In the local values when we edit/update the unlimited allowed values should get the prompt message.
RCF-1218ARC: Search/Filter option is not displaying in the Global Config settings screen.
RCF-1002ARC: Not receiving any error message when trying to fetch, also able to generate UIN multiple times using an already consumed packet.
MOSIP-34477Security testing: ARC fake Identity Generation issue.
MOSIP-34400Security testing: ARC- user verification for certain actions.
MOSIP-34361Security testing: ARC- CBC issue.
MOSIP-34359Security testing: ARC- utilization of local authentication mechanisms.
MOSIP-34357Security testing: ARC - data protection in case of loss of device.
MOSIP-34355Security testing: ARC- session logout issue.
RCF-755ARC: Server status is not moving further after "Packet receiver" even after UIN generation.
RCF-665RCF: Getting "IDA Response fetch failed" error message while onboarding/Updating biometrics user.
RCF-418RCF: After entered the age still validation message not removing in DOB like address/phone number.
RCF-373RCF - Incorrect error message on login screen.
RCF-183RCF: Should be getting an appropriate error message, If the device/user is not onboarded.
RCF-119Add machine name in the auth request.
### Known Issues To view the list of known issues, refer [**here**](https://mosip.atlassian.net/issues/?jql=parent%3Drcf-31%20and%20issuetype%3Dbug%20and%20status%20not%20in%20%28closed%2C%20Canceled%29%20and%20labels%21%3DARC_Real_Device). ### Repository Released
RepositoriesTags Released
android-registration-clientv1.0.1
### Compatibile Platform/Module The following table outlines the tested and certified compatibility of Inji Verify 0.10.0 with other modules.
Platform/ModuleVersion
MOSIP1.2.0.1
{% hint style="warning" %} **Note**: **NOT** Compatible with **MOSIP** [**v1.2.1.0**](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/v1.2.1.0) (JAVA 21) {% endhint %} ### Build and Deploy To access the build and read through the deployment instructions, refer to the[ Developer Guide](https://docs.mosip.io/1.2.0/modules/android-registration-client/android-registration-client-developer-guide). ### Configurations For details related to Android Registration Client configurations, refer to the[ Configuration Guide](https://docs.mosip.io/1.2.0/modules/android-registration-client/android-registration-client-configuration). ### User Guide To learn more about the available features, processes, and user interface, refer[ Android Registration User Guide](https://docs.mosip.io/1.2.0/modules/android-registration-client/android-registration-client-user-guide) for further information.