Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address returned as empty string for Maltese national id #379

Open
a-karthi-optisol opened this issue Oct 18, 2022 · 4 comments
Open

Address returned as empty string for Maltese national id #379

a-karthi-optisol opened this issue Oct 18, 2022 · 4 comments

Comments

@a-karthi-optisol
Copy link

  • Xcode version: 14.0
  • BlinkID SDK version: 5.13.0
  • What are you trying to scan: Maltese national id card

Description of problem:
I am trying to scan and get details from Maltese id card, but it gives address value as empty string
help me to fetch address from the result data from PPBlinkID -> 5.13.0

Relevant code:
self.blinkIdRecognizer = MBBlinkIdCombinedRecognizer()
let usdlResult = self.blinkIdRecognizer.result. //MARK:- MBBlinkIdCombinedRecognizerResult!
if let data = usdlResult?.barcodeResult,
data.address != "" {
let postal = data.postalCode
KYCManager.sharedInstance.kycModel.postalCode = postal
let city = data.city
KYCManager.sharedInstance.kycModel.city = city
let street = data.street
KYCManager.sharedInstance.kycModel.streetAddress = street
let jurisCode = data.jurisdiction
KYCManager.sharedInstance.kycModel.state = jurisCode
} else if let addressStreet1 = usdlResult?.address {
KYCManager.sharedInstance.kycModel.streetAddress = addressStreet1
// here i get empty string for maltese id card that's the issue i have facing now
}

print of address -->
(lldb) po usdlResult?.address
▿ Optional

  • some : ""

Data structure of usdlResult -->
(lldb) po usdlResult
▿ Optional

  • some : <MBBlinkIdCombinedRecognizerResult: 0x281439620>
    dateOfBirth: <MBDateResult: 0x281afe490>, date: 1979-07-02 18:30:00 +0000, original string 790703
    dateOfExpiry: <MBDateResult: 0x281affb70>, date: 2032-04-19 18:30:00 +0000, original string 320420
    dateOfIssue: <MBDateResult: 0x281afe520>, date: (null), original string
    dateOfExpiryPermanent: 0
    documentNumber: #
    firstName: #
    lastName: #
    sex: #
    nationality: MALTESE
    mrzResult: Document Type: Identity Card; issuer: MLT; issuerName: MALTA; documentNumber:#<; documentCode: ID; dateOfExpiry: <MBDateResult: 0x281aff9c0>, date: 2032-04-19 18:30:00 +0000, original string 320420; primaryID: #; secondaryID: #; dateOfBirth: <MBDateResult: 0x281afcea0>, date: 1979-07-02 18:30:00 +0000, original string 790703; nationality: MLT; nationalityName: MALTESE; gender: #; opt1: 0257310L<<<<<<<; opt2: 220421<<<<<;
    driverLicenseDetailedInfo: <MBDriverLicenseDetailedInfo: 0x281afdef0>
    classInfo: <MBClassInfo: 0x28356f980>
    frontImageAnalysisResult: <MBImageAnalysisResult: 0x280f32740>
    backImageAnalysisResult: <MBImageAnalysisResult: 0x280f30f80>
    barcodeResult: <MBBarcodeResult: 0x106357d90>
    frontVizResult: <MBVizResult: 0x282c74d20>
    backVizResult: <MBVizResult: 0x282c748c0>
    processingStatus: 0
    frontProcessingStatus: 0
    backProcessingStatus: 0
    recognitionMode: 1
    scanningFirstSideDone: 1
    digitalSignatureVersion: 0
    age: #
    expired: 0
@mparadina
Copy link
Contributor

Hi @a-karthi

Just to double-check, did you maybe try scanning the document with the current latest version of the SDK to see if the behaviour will change?

Also, is the mentioned behaviour happening only on one, or mulitple documents of the same type?
Lastly, is the document you're trying to scan real, or a sample, for instance, found on the internet?

@a-karthi-optisol
Copy link
Author

I tried with real one - Maltese national id card
I tried with real passports and driving licence it will give the address, so i think it will happen on this particular Maltese id card
I did not udpate the sdk,if u tell it is necessary and it will be fix the problem means we will try that?
All the id we worked out till now is real :)

@mparadina
Copy link
Contributor

Hi @a-karthi

Yes, there could be an issue with that particular document since, as mentioned, you did not experience the same behaviour with other documents.
Just to double-check, are you scanning a physicial document, or from a screen?

I reccomend at least testing out the latest version, as we've made improvemnts to the SDK in terms of reducing the error rates in the scanning process in comparson to the 5.13.0 version, which came out more than a year ago.

Please test this out and let me know the results.

@a-karthi-optisol
Copy link
Author

I have faced the issue on that particular document - Maltese id card
It occurs while scanning physical and from a screen
I have updated the SDK to 5.20.0 still the issue remains same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants