FloBle Plus FlomioSDK Error Code=-18

[SocratesParticipant]

Hello there,

-Im trying to read an ePassport using the FloBle Plus device connected via bluetooth to an iPhone7.
When scanning the passport, the application fires the didReceiveReaderError method with the following error message: “Tag needs to be an ISO14443A tag” (Error code = -18)

-I would like to mainly use the FloBle Plus to perform the BAC for the epassport.

-Does this mean that the FloBle Plus device can’t read the epassport data because the epassport is in a different format?
Am I missing a step here? I also tried with different ReaderStateType values in the configuration of the instance.

Thanks,
Socratis

[ScottKeymaster]

Hi,

We can add that for you in the next release. We currently only detect 14443A tags, and ePassports are 14443B. It will be this link and will be updated by tomorrow: SDK v2.3 beta

Scott

[ScottKeymaster]

That has been updated now, please let me know if there are any issues. You will have to send APDUs to read the data yourself, we do not provide the APDU sequences to read this data.

Kind Regards,
Scott

[SocratesParticipant]

Hello Scott,

Thanks for the quick SDK update, it compiles successfully by following the updated readme files!
However I think you need to register my device again according to the console message. (Richard did that for me last week on the previous SDK).

This is the response:
Serial Number: RR330-004226
The device is not licensed. http://flomio.com/flojack/#getting_device_id

Thanks,
Socratis

[ScottKeymaster]

Currently switching Databases so some are slipping devices through the cracks. Should be working now for you.

Kind Regards,
Scott

[SocratesParticipant]

Thanks Scott,

It works now!

Best regards,
Socratis

[SocratesParticipant]

Hi Scott,

I want to report a behaviour I’m noticing using the FloBle Plus device when scanning an ePassport.

While the scan detection always works for other nfc tags(14443A), it doesn’t always detect the epassport(14443B).

The scan detection works at random times, sometimes taking me up to 10+ times to rebuild the app or restart the device and get into the didFind(_ tag: FmTag!, fromDevice deviceId: String!)

This mainly slows down the development process..
Im using the FlomioSDKv2.3_beta version that you have provided to me.

Thanks, looking forward to your reply.
Socratis

[SocratesParticipant]

Hi Scott,

I attempted to run the v2.3 beta on xCode 8.3 because I assumed that maybe xCode 9 beta 3 and iOS11 bluetooth has some problem from Apple’s side or from the 2.3beta sdk.

So after following the readme once again and setting up the project the same way I did for xCode 9, I get this message when trying to compile with various devices.

Message – ld: framework not found FileProvider for architecture arm64

Have you ever came across this?
Am I doing something wrong?

Thanks,
Socratis

[ScottKeymaster]

Hi Socrates,

I have not seen that problem. We use the SDK on Xcode beta 3 and iOS 11. You might try updating your build settings search paths, along with making sure you have all the correct libraries in Linked Frameworks and Libraries.

I will try reproduce your error, but as we don’t officially support Xcode 9 beta, I will have to give this a lower priority than other issues I am working on.

Kind Regards,
Scott

[SocratesParticipant]

Hi Scott,

Ok thats fine actually. The reason I tried to do that its because of the other issue i’m having where the FloBle plus cant always detect epassport(14443B) but always detects other nfc tags(14443A). This is happening on v2.3 beta you provided.

Have you come across this issue?

Kind regards,
Socratis

[Author]

Posts