> 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/migrations.md). # Migration Guide ## v7.3.14 * Consent has changed from a dialog to an activity see [here](/integration-options/mobile/android/consent-screen.md#show-the-consent-screen) for how this now works using start activity for result instead of triggering a consent ## v7.3.5 * From 7.3.5 the SDK now requires signature instead of sec key please look [here](/integration-options/rest-api/signing-your-api-request/generate-signature.md) for how to generate a signature ## v7.3.3 * Introduction of signature breaks sec\_key implementation please look [here](https://docs.smileidentity.com/rest-api/signing-your-api-request/generate-signature#api-key-for-signature) for how to generate a signature ## v7.2.0 * Removed the useIdCard method from the SIDConfig.Builder class, the SDK will now handle this internally * `setRetryOnfailurePolicy` is no longer mandatory when submitting a job� will default to 10 retries, 15 seconds apart ## v7.1.1 With the introduction of android 11 google is now enforcing scoped storage as explained [here](https://developer.android.com/about/versions/11/privacy/storage) . If you have agent mode enabled and are capturing multiple jobs for later uploading and would like to migrate these jobs to scoped storage you need to make the following changes * Target android 10 in build.gradle by using `targetSdkVersion 29` * Add requestLegacyExternalStorage the AndroidManifest.xml so you can have access to external storage ``` ``` * Request external storage read and write permissions On job submission, all jobs stored in external storage will be migrated to scoped storage and when the right tag is provided a job will be submitted All jobs captured going forward will be stored in scoped storage. ## v7.1.0 * 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 � ## v6.4.3 onwards Migration to the new ID Capture Replace everything associated with * com.smileidentity.libsmileid.utils.CaptureIDCardOverlay * SurfaceView * �FrameLayout ( if copied .from the demo app) Refer to New physical id capture for steps on how to implement the new ID Capture � � ## v6.4.0 to v6.4.1 onwards 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 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 ``` ## v 6.3.x to v 6.4.x ### DETAILS This change introduced sandboxed folders for Smile Identity jobs to make sure they are app specific this uses the package name of the app implementing the Smile Identity library and as such the library requires a context on multiple occasions **SIDInfosManager.class** When getting the instance the method get instance now requires a context ``` //PREVIOUS SIDInfosManager.getInstance() CURRENT (v 6.4.x) SIDInfosManager.getInstance(Context context) ``` ### SIDConfig.class When getting the idle tags the method now requires a context ``` //PREVIOUS public Set getIdleTags() //CURRENT (v 6.4.x) public Set getIdleTags(Context context) ``` ### SIDTagManager.class The methods clearConfig and getConfigCache now require a context ``` //PREVIOUS public void clearConfig(String tag) public SIDConfigCache getConfigCache(String tag) //CURRENT (v 6.4.x) public void clearConfig(String tag,Context context) public SIDConfigCache getConfigCache(String tag,Context context) ``` --- # 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/migrations.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.