I just received my BR301 BLE and after I select my Bluetooth reader from drop down list, i get an error stating “no objects found.”
I read the log and it connects and reads certs but drops before they register.
I see other users have had this issue in the past. I have an iPhone 13 Pro Max, Gemalto DLGX4-A 144.
I have tried all trouble-shooting besides this. I hope this is a simple fix. Other readers and middleware I use work fine but this was supposed to eliminate the middleware portion however it’s not looking good.
Any assistance would be great! Trying to streamline some processes for work and field collection and if this can actually work…game changer😎
Thanks in advance!
We believe we have a fix for this issue and are currently QA testing the fix to get into the app store. You can get the beta build now to test it by signing up here:
https://twocanoes.com/smart-card-utility-beta/
Please make sure to reboot after installing the beta. There seems to be an issue on Apple’s side with updating these types of apps that require a reboot.
tim
No luck yet, still the same error. I downloaded the Beta and still no luck. I haven’t reverted to an older build since the newest one should incorporate the older ones.
Here is what log prints:
2022-02-04T22:43:40-08:00: starting up
2022-02-05T08:37:57-08:00: starting up
2022-02-05T08:41:50-08:00: starting up
2022-02-05T08:41:55-08:00: readerInterfaceDidChange: FT_00A050080527 attached: true
2022-02-05T08:41:55-08:00: card interface isAttached: true
2022-02-05T08:41:56-08:00: device name is Feitian_FT_00A050080527. Loading certs
2022-02-05T08:41:56-08:00: reading certificates from FEITIAN Reader
2022-02-05T08:41:56-08:00: -----connectReader
2022-02-05T08:41:56-08:00: -----SCardEstablishContext
2022-02-05T08:41:56-08:00: -----gCardHandle
2022-02-05T08:41:56-08:00: -----TCSFeitianTransmit
2022-02-05T08:41:56-08:00: checking for card inserted Optional(“Feitian_FT_00A050080527”)
2022-02-05T08:41:56-08:00: handle is 13895432
2022-02-05T08:41:56-08:00: name is bR301
2022-02-05T08:41:56-08:00: checking for card inserted 0 dwEventState:32
2022-02-05T08:41:58-08:00: card inserted
2022-02-05T08:41:58-08:00: SCardConnect2
2022-02-05T08:41:58-08:00: DONE
2022-02-05T08:41:58-08:00: trying PIVSmartCard
2022-02-05T08:41:59-08:00:
sending APDU: cla:0 ins:a4 p1:4, p2:0 data:00a404000ba000000308000010000100
2022-02-05T08:42:00-08:00: APDU send successful. Response: 6a82
2022-02-05T08:42:00-08:00: APDU command returned not found. /Users/tperfitt/Documents/Projects/Smart Card Utility/SCU Mobile/SmartCardReaderProtocol.swift:268
2022-02-05T08:42:00-08:00: APDU send error in retry. /Users/tperfitt/Documents/Projects/Smart Card Utility/SCU Mobile/PIVSmartCard.swift:83
2022-02-05T08:42:01-08:00:
sending APDU: cla:0 ins:a4 p1:4, p2:0 data:00a404000ba000000308000010000100
2022-02-05T08:42:01-08:00: APDU send successful. Response: 6a82
2022-02-05T08:42:01-08:00: APDU command returned not found. /Users/tperfitt/Documents/Projects/Smart Card Utility/SCU Mobile/SmartCardReaderProtocol.swift:268
2022-02-05T08:42:01-08:00: APDU send error in retry. /Users/tperfitt/Documents/Projects/Smart Card Utility/SCU Mobile/PIVSmartCard.swift:83
2022-02-05T08:42:01-08:00: APDU send error. /Users/tperfitt/Documents/Projects/Smart Card Utility/SCU Mobile/PIVSmartCard.swift:86
2022-02-05T08:42:01-08:00: trying PIVTransitionalSmartCard
2022-02-05T08:42:01-08:00:
sending APDU: cla:0 ins:a4 p1:4, p2:0 data:00a4040007a000000116db00
2022-02-05T08:42:01-08:00: APDU send successful. Response: 610d
2022-02-05T08:42:01-08:00:
sending APDU: cla:0 ins:c0 p1:0, p2:0 data:00c000000d
2022-02-05T08:42:01-08:00: APDU send successful. Response: 6f0b8407a000000116db00a5009000
2022-02-05T08:42:01-08:00: ATR:6f0b8407a000000116db00a500
2022-02-05T08:42:01-08:00:
sending APDU: cla:80 ins:52 p1:0, p2:0 data:80520000020102
2022-02-05T08:42:01-08:00: APDU send successful. Response: 6102
2022-02-05T08:42:01-08:00:
sending APDU: cla:0 ins:c0 p1:0, p2:0 data:00c0000002
2022-02-05T08:42:01-08:00: APDU send successful. Response: 30009000
2022-02-05T08:42:01-08:00: headerLengthData:
2022-02-05T08:42:01-08:00: header length wrong size!
2022-02-05T08:42:01-08:00: Connected------
2022-02-05T08:42:01-08:00: Showing all the certificates
Then after that I get the “no objects error, retry reading certs.”
Thanks for help with this!
The log is very helpful. It shows that it can’t find the “applet” on the card. We support 2 different types of cards: PIV and CACv2 PIV transitional. What kind of card do you have? It usually has some laser printing on the back with the manufacturer and some identifiers.
tim
Hi Tim,
I have a Gemalto DLGX4-A 144. It works on my work computer as well as my other readers, too include an iPhone specific lightening reader.
Thanks for the help and timely replies.
V/r
Greg Mireles
Do you have a Mac by any chance? If so, can you get me an APDU trace on a reader that works with the same card? Instructions here:
Please send it to support@twocanoes.com
tim
Sorry for the late reply. I do have a desktop Mac from 2017 but running the most current OS. I will get that fired up this weekend (or sooner) and will send the log to the support email you provided.
Thanks
V/r
Greg Mireles
Hi Tim,
So the Mac that I do have is too old to work with for this purpose so I was wondering what else we could do?
I still cannot get the reader to read my certs and the same log screen snapshot I sent in the previous emails, is still currently what is going on (error, no objects).
I really feel your set-up is the key to me developing out some really neat products for the US Army Corps of Engineers (USACE), but just need this to read/see the card and print for pins.
Help me get this up and running and I am positive there will be more action coming your way as we are in the midst of revolutionizing how our workflows operate in a wide variety of formats from mobile data collection to ease of use for mobility.
Thanks again in advance and we can talk more later if you’d like.
Have a great day!
V/r
Greg Mireles
I sent you a reply via our support portal. Let’s have a meeting and dig into what the issue is. I think we should be able to figure it out and resolve it.
tim