# CTK local test: Device Discovery handled but test does not proceed **URL:** \ **Category:** Support\ **Tags:** ctk\ **Created:** [July 17, 2025, 6:38am UTC](https://community.mosip.io/t/ctk-local-test-device-discovery-handled-but-test-does-not-proceed/2174 "2025-07-17T06:38:38Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![wjyang](https://avatars.discourse-cdn.com/v4/letter/w/e9bcb4/32.png) [@wjyang](https://community.mosip.io/u/wjyang)\ **Post date:** [July 17, 2025, 6:38am UTC](https://community.mosip.io/t/ctk-local-test-device-discovery-handled-but-test-does-not-proceed/2174/1 "2025-07-17T06:38:38Z")
I’m currently testing CTK (Compliance Tool Kit) installed on my local machine. After successfully launching CTK and creating a project, I implemented the test Device Discovery Response according to the MDS Specification ([MDS Specification | MOSIP Docs 1.2.0](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/mds-specification#device-specification)). ![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/2X/e/e1ec49e1a22211d7c20abf27dee19a436d231cf7.png) The response is captured correctly by CTK, but the process does not proceed beyond that point. To troubleshoot, I also registered the partner and created a device in the PMP portal (under Device Details – Create Device), but the issue persists. I would appreciate any help or guidance on how to resolve this. Below is the Device Discovery Response data I used: ================================================================== // cpp resp.\_deviceId = “1”; resp.\_deviceStatus = “Not Registered”; resp.\_certification = “L0”; resp.\_serviceVersion = “0.9.5”; resp.\_deviceSubIdList.append(“0”); resp.\_callbackId = “[http://127.0.0.1](http://127.0.0.1)”; resp.\_deviceCode = “111122223333”; resp.\_specVersionList.append(“0.9.5”); resp.\_purpose = “Registration”; resp.\_digitalId.\_serialNo = “111122223333”; resp.\_digitalId.\_make = “Brand”; resp.\_digitalId.\_model = “Model”; resp.\_digitalId.\_type = “Iris”; resp.\_digitalId.\_deviceSubType = “Double”; resp.\_digitalId.\_deviceProvider = “test1111”; resp.\_digitalId.\_deviceProviderId = “test1111”; resp.\_digitalId.\_dateTime = “2025-07-17T11:18:12”; resp.\_error.\_errorCode = “100”; resp.\_error.\_errorInfo = “Device not registered”; ---
**Author:** ![wjyang](https://avatars.discourse-cdn.com/v4/letter/w/e9bcb4/32.png) [@wjyang](https://community.mosip.io/u/wjyang)\ **Post date:** [July 18, 2025, 8:15am UTC](https://community.mosip.io/t/ctk-local-test-device-discovery-handled-but-test-does-not-proceed/2174/3 "2025-07-18T08:15:45Z")
![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/2X/e/eb90ff588c162c27a1ce8af36605b288454afae8.png) I am currently trying to test a device intended for use as a registration device. In the “Add a new Project” form, there is a required field called **SBI Hash**. What does **SBI Hash** mean, and where can I find or generate it? Any guidance would be appreciated. ---
**Author:** ![wjyang](https://avatars.discourse-cdn.com/v4/letter/w/e9bcb4/32.png) [@wjyang](https://community.mosip.io/u/wjyang)\ **Post date:** [July 18, 2025, 9:33am UTC](https://community.mosip.io/t/ctk-local-test-device-discovery-handled-but-test-does-not-proceed/2174/4 "2025-07-18T09:33:44Z")
> **[MDS Specification | MOSIP Docs 1.2.0](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/mds-specification)** ![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/2X/6/6fd20577de6266aeeb0387b490d61a25719ac770.png) In the Digital ID structure shown in the documentation, what does the field **`deviceProviderId`** refer to? Is it the **CTK login ID** , or is it a **separately assigned identifier**? I would appreciate clarification on where this ID comes from and how it should be set. ---
**Author:** ![wjyang](https://avatars.discourse-cdn.com/v4/letter/w/e9bcb4/32.png) [@wjyang](https://community.mosip.io/u/wjyang)\ **Post date:** [July 18, 2025, 10:15am UTC](https://community.mosip.io/t/ctk-local-test-device-discovery-handled-but-test-does-not-proceed/2174/5 "2025-07-18T10:15:37Z")
**The main issue (device not found) has now been resolved.** It turned out to be a mistake on my end related to the Device Discovery response JSON. I’d be grateful if you could take a look at my earlier questions regarding the **SBI Hash** and **deviceProviderId**. ---
**Author:** ![ckesiraju](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@ckesiraju](https://community.mosip.io/u/ckesiraju)\ **Post date:** [July 18, 2025, 12:29pm UTC](https://community.mosip.io/t/ctk-local-test-device-discovery-handled-but-test-does-not-proceed/2174/6 "2025-07-18T12:29:05Z")
Hi @wjyang Thanks for reaching out. We are looking into your query and will get back to you soon! Until then, happy coding with MOSIP! Best regards, Team MOSIP ---
**Author:** ![mayuradesh](https://avatars.discourse-cdn.com/v4/letter/m/e19adc/32.png) [@mayuradesh](https://community.mosip.io/u/mayuradesh)\ **Post date:** [July 18, 2025, 12:52pm UTC](https://community.mosip.io/t/ctk-local-test-device-discovery-handled-but-test-does-not-proceed/2174/7 "2025-07-18T12:52:34Z")
Hi @wjyang You can refer here to understand SBI Hash: [Hash Generation | Compliance Tool Kit](https://docs.mosip.io/compliance-tool-kit/developer-guides/hash-generation) DeviceProviderId = partner id that you can get after onboarding the partner in PMS Hope this helps. Mayura