> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/integration-options/mobile/android/smile-id-sdk/release-notes.md). # Release Notes {% hint style="danger" %} This SDK is deprecated and will receive limited support. Please adopt the v10 SDK. {% endhint %} ## 7.3.30 * Fixed issue with reenrolling user using the .setAllowNewEnroll method on the config * Fixed issue with updating a user on file selfie using the .useEnrolledImage method on the config ## 7.3.24 * Fixed crash caused by unstable network conditions by replacing the OkHttp Network Interceptor with a regular Interceptor * Fixed crash caused by passing too large a Bitmap as parcelable by instead passing the resource between Activities * Fixed a bug where the BVN Consent image did not show if using the Flutter SDK ## 7.3.22 * Feature: BVN * Feature: Added optional crash reporting for crashes caused by Smile ID SDKs * It is highly recommended to enable this by calling `enableSmileIdentityCrashReporting()` in your Application's `onCreate` ## 7.3.16 * Improved blur detection experience during document capture * Updated the android gradle plugin to 7.2 this may warrant an upgrade of several packages particularly app compat which is now using 1.5.1 ## 7.3.15 * Improved blur detection experience during document capture ## 7.3.14 * Improved blur detection experience during document capture * Changed consent from a dialog to an actual activity ## 7.3.13 * Improved user experience during document captures to avoid unnecessary ui feedbacks ## 7.3.12 * Updated project gradle wrapper to 7.5 * Updated gradle plugin to 7.2.1 * Updated target SDK to android 32 * Added blur to document live capture pipeline, SDK won't allow blurred captures capturedBlurryMessage attribute on the view will display the respective message * Added darkness to document live capture pipeline, SDK won't allow dark captures\ capturedDarkMessage attribute on the view will display the respective message * Better messaging for document capture * Added ability to set id type as passport/id card/ other which will enable the the correct aspect ratio for the document * Document capture will be in landscape mode always for better document captures ## 7.3.11 * Job status delay to match SLA * Cropping issue fix (*Known issue of a bad crop when capturing documents on a samsung S8*) ## 7.3.10 * Document capture improvements * Fix for crash from shutter sounds * Consent screen dark mode opt out *Known issue of a bad crop when capturing documents on a samsung S8* ## 7.3.9 * Old job tag fix * Adjusted selfie camera preview aspect ratio * Integration source sdk (android) and version * UI customisation fixes ## 7.3.8 * Document verification fix on for enrol image to true/false ## 7.3.7 * Fix for auth smile crash in 7.3.5 * ID Card capture orientation allowing for portrait ID ## 7.3.6 * Enable id card capture only to submit document verification jobs * UI Customisations for selfie,id card and review screen * Android 12 compatibility ## 7.3.5 * User consent dialog to get consent on ID types that require consent from users, see here for more information * Document verification [(now in beta)](/integration-options/server-to-server/javascript/products/document-verification.md) * Minor bug fixes * Breaking change, please generate a new api key under signature as described [here](/integration-options/rest-api/signing-your-api-request/generate-signature.md) ## 7.3.4 * Fixed bugs with smile auth having missing parameters and better handling of partner parameters ## 7.3.3 * Introduced a new authentication method for api calls using the signature instead of the sec\_key * Updated auth smile to handle string timestamps ## 7.3.2 Small improvements and bug fixes ## **7.3.0** -> * Improved and updated underlying selfie and id capture face detection functionality * Improved selfie capture for better image processing for liveness images * Added back of id card capture feature ## v7.2.0 * We have removed the mandatory retry policies and have set a default but you can still override the default if you see a need to do so using `setRetryOnfailurePolicy.` when submitting a job� the SDK will default to 10 retries, 15 seconds apart. * Removed `useIdCard` on the SIDConfig.Builder class so the SDK can handle this automatically. * The first version which is compatible with Smile ID UI which is a layer we have built to abstract the manual configuration to the SDK and for convenional use this is an easier way to get started very quickly in fewer lines of code. � � ## v7.1.2 * Fixed issue with switching between the test and production environments ## v7.1.1 * Moved to the recommended scoped storage to support Android 11 devices.See [here](https://developer.android.com/about/versions/11/privacy/storage) for the android 11 storage changes * Fixed crashes with unsatisfied link error related to selfie and id capture * Fixed black oval issue witthout error reporting when selfie capture fails to start * Introduced storage space checks for read/write permissions and available disk space. * Introduced camera permission check and related error when starting selfie capture to avoid silent failures ## v7.1.0 onwards * Moved SmartCardView class from the com.smileidentity.libsmileid.core.idcapure package to com.smileidentity.libsmileid.core class * Added real time light and blur checks on ID card capture * Added custom messaging for the ID Card capture as demonstrated here * Added onIDCardStateChange(IDCardState idCardState) for feedback to the realtime ID card quality checks ## v7.0.1 onwards * The SDK is now available on maven central and can be installed by following the Getting Started Guide * SDK now requires a Smile Config file from the partner portal available [here](https://dev01-smileid.herokuapp.com/sdk) * SDK now handles the urls and port configuration and introduced the environment enum SIDNetData.Environment.TEST and SIDNetData.Environment.PROD to manage your Smile ID environmen ### Version 6.4.2 * Fixed issues with ID capture being closely tied to job submissions where an enroll would fail if ID capture had been invoked on the same tag * Fixed issues with capturing ID before selfie * New and improved ID Capture view in a few lines of code please see here for more information on how to implement this. ### Version 6.4.2 Fixed issues with Job Type 5 which was resulting in a silent failure due to remaining job configurations from previous versions. Added the ability to set custom callback using the SDK, this can be done by using the SIDNetData class. After setting the other settings in this class then call the method `setCallBackUrl` as in the example below ``` SIDNetData data = new SIDNetData(); ....//other SIDNetData settings data.setCallBackUrl(https://example.com/callback); ``` ### Version 6.4.1 The SDK will provide validation by default and will return an error which can be either ``` ID_VALIDATION_INVALID_COUNTRY = 42 or ID_VALIDATION_INVALID_ID_TYPE = 43 or ID_VALIDATION_MISSING_REQUIRED_FIELDS = 40 ``` �For more information on required fields per ID type please refer to [ID authority support](https://docs.usesmileid.com/supported-id-types/for-individuals-kyc/backed-by-id-authority) You can turn off this remote validation by using ``` builder = new SIDConfig.Builder(this) .... setValidateIdInfo(false) ... builder.build(); //this will only validate to make sure there is a country, id type and id ``` Fixed a crash for a subset of armv7 devices caused by a linking error ### Version 6.4.0 **BREAKING CHANGES** * The singleton SIDInfosManager.getInstance() now requires a context when getting the instance * All calls to methods in SIDTagManager should add a context parameter * If you have a custom implementation which was reading or writing to the `sid.jobs.SI` folder please change to `apppackagenamesid.jobs.SI` **Fixes** * Fix for bug when reusing the same tag for all jobs the sdk was reusing information now every job will clear cached information based on tag on failure or success **Features** * Jobs will now be stored in application specific directories based on the package name with the `sid.jobs.SI` suffix � ## Version 6.3.1 #### Fixes * Fix for conflict issues with other libraries using opencv particularly the card.io library * Fix for job type 5 user id information when using the `.submitAll()` method from `SIDNetworkRequest` class ## Version 6.3.0 #### Bug Fixes * Fix for correct camera orientation from the CaptureIDCard for Nexus 5 devices * Supporting multiple orientation for the camera from CaptureIDCard class and will now follow the activity/fragment's orientation with the correct display (however landscape is still greatly advised since it provides a better user experience as well as better resolution for the final image) * Jobs using submitAll methods from SIDNetwork request will now have unique configurations per job and this is by introduction of the SIDTagmanager class which should be called before a job is submitted an example is on this page #### Features * ID Validation aka Job Type 5 which is a simple validation for ID information can now be performed in the library see this page for more information --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://legacy-docs.usesmileid.com/integration-options/mobile/android/smile-id-sdk/release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.