Home › Forums › Ask the Flomies › SDK issue with Swift (iOS)
Tagged: Bluetooth Connection, FloBLE Plus, Flomio SDK, Sample app
-
AuthorPosts
-
October 20, 2016 at 3:07 am #56969
Hello Richard
We have some issues with the BLE that we would like to discuss over the phone. Maybe give your office a call during normal business hours?
In addition, our techs just sent me a log, seems our App keeps crashing and we don’t really know why. Can you please assist.
2016-10-20 14:51:57.552671 OH9H[398:121317] ::discovered peripheral ACR1255U-J1-000942 40A7ACD8-2FF0-4C79-AA8C-5CBCE841BE32 2016-10-20 14:51:57.752763 OH9H[398:121317] Peripheral Connected 2016-10-20 14:51:58.135897 OH9H[398:121317] Services Discovered 2016-10-20 14:51:58.139304 OH9H[398:121317] Reader Detected 2016-10-20 14:51:58.825475 OH9H[398:121317] Peripheral Successfully Attached 2016-10-20 14:51:58.825983 OH9H[398:121317] -[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x15ff06940 2016-10-20 14:51:58.826344 OH9H[398:121317] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x15ff06940'
Thank you for all your help!
Mike
October 20, 2016 at 3:33 am #56970Hi Mike, not sure what the source of that error is but let me start by asking to share the code you’re using to initialize the Flomio SDK. Inside the download bundle there’s a README file with detailed directions on how to get a simple app that scans tags built in Xcode or Android Studio. Did your techs follow that guide? I’d start there. Also, we have a Test App we can share via the TestFlight system that is a polished implementation of what’s directly laid out in the README. Let me know if haven’t gotten that yet.
RE: phone support. Unfortunately we don’t offer free phone support, only via Flomio Service hours. I understand it’s perhaps not an expense you’ve budgeted for so glad to provide all the support you need via the Forums, albeit at a bit more delayed pace.
best,
RichardOctober 20, 2016 at 3:44 am #56971Hello Richard,
Well, the purpose of the call was because you had wanted to hear what we use the Floble for and I figured it would be easier/quicker to explain over the phone than to write it out but I will attempt to do so.
As I am not able to add attachments in this email, I will send you the code on initialization of the Flomio SDK in email.
Mike
October 20, 2016 at 4:01 am #56973Hi Mike, I looked over the code you shared via email. It’s written in Swift which hasn’t been officially released yet. I would recommend sticking with our ObjC instructions for now. Otherwise, Scott on our team will have to look over your code and figure out the problem. I’ll tell him to do so today.
best,
RichardOctober 20, 2016 at 6:03 am #56985Hi Mike,
I have looked over your code and although it all looks correct, it does differ from our Swift implementation from the README which is available in the Flomio SDK v2.1 (beta)The most notable difference is your initialization.
Here is the default initialization in the READMElet readerManager : FmSessionManager = FmSessionManager() readerManager.selectedDeviceType = DeviceType.floBlePlus //flojackBzr, flojackMsr, flojackAny readerManager.delegate = self let configurationDictionary : [String : Any] = ["Scan Sound" : 1, "Scan Period" : 1000, "Reader State" : ReaderStateType.readUuid.rawValue, //readData for NDEF "Power Operation" : PowerOperation.autoPollingControl.rawValue, //bluetoothConnectionControl low power usage "Allow Multiconnect" : false] readerManager.setConfiguration(configurationDictionary) readerManager.createReaders()
I hope this helps, let me know how this works for you and I will continue to assist you on this. It’s worth mentioning that we are only in early days of support for Swift and it is not officially released.
Kind Regards,
ScottOctober 20, 2016 at 9:10 am #56988Hello Scott,
Just sent the message over to our tech. Will try and see. Definitely will keep you updated. Thank you for getting back to us so quickly!
Mike
October 20, 2016 at 10:43 am #56991Hello Scott,
Unfortunately it is still crashing.
I have sent the a screen shot to email. Please advise. Thank you.
Mike
October 20, 2016 at 11:16 am #56994Hi Michael,
You are still using
self.fmManager = FmSessionManager.sharedManager() as! FmSessionManager
I’m not entirely sure if this is the cause of your error but will you change it to:
self.fmManager = FmSessionManager()
Kind Regards,
ScottOctober 20, 2016 at 11:25 am #56997Error in the bottom still exists. Will continue to try. =(
Mike
October 20, 2016 at 11:30 am #56998Also, can you confirm you are using the latest Flomio SDK v2.1 (beta)?
- This reply was modified 8 years, 2 months ago by Scott.
October 20, 2016 at 11:32 am #57000Yes, confirmed. Using 2.1
October 20, 2016 at 11:41 am #57001I have emailed you
ViewController-Bridging-Header.h ViewController.swift
to try.
Regards,
ScottOctober 20, 2016 at 7:09 pm #57013Here is the log:
To answer Richard, yes our team has written in swift before.2016-10-21 05:53:10.406766 OH9H[470:149509] Init FloBLE Plus 2016-10-21 05:53:10.500159 OH9H[470:149509] ::centralManagerDidUpdateState supports 5 2016-10-21 05:53:10.666591 OH9H[470:149509] ::discovered peripheral Charles Ku 的 iPhone 95515B11-77FA-E4DF-89C1-E2B8667FC89A 2016-10-21 05:53:10.688812 OH9H[470:149509] ::discovered peripheral ACR1255U-J1-000942 40A7ACD8-2FF0-4C79-AA8C-5CBCE841BE32 2016-10-21 05:53:13.308633 OH9H[470:149509] Peripheral Connected 2016-10-21 05:53:14.066813 OH9H[470:149509] Services Discovered 2016-10-21 05:53:14.070712 OH9H[470:149509] Reader Detected 2016-10-21 05:53:14.937037 OH9H[470:149509] Peripheral Successfully Attached 2016-10-21 05:53:14.937816 OH9H[470:149509] -[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x133d242d0 2016-10-21 05:53:14.938533 OH9H[470:149509] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[ABTAcr1255uj1Reader checksumFromBuffer:length:]: unrecognized selector sent to instance 0x133d242d0' *** First throw call stack: (0x18cba81c0 0x18b5e055c 0x18cbaf278 0x18cbac278 0x18caa659c 0x10015a790 0x100158e38 0x100158058 0x10013de44 0x10015a064 0x193778364 0x1937784c4 0x193774ef4 0x193770018 0x193783f58 0x19377c70c 0x100df125c 0x100df121c 0x100dfeb54 0x100df4ce4 0x100df6060 0x18cb55f2c 0x18cb53b18 0x18ca82048 0x18e505198 0x192a55628 0x192a50360 0x1000be1e8 0x18ba645b8) libc++abi.dylib: terminating with uncaught exception of type NSException
Mike
October 20, 2016 at 9:03 pm #57016Mike, can you send the following info:
Device: iPhone 6?
OS: iOS version 10.0.2?
Xcode: version 8.0?
Reader: FloBLE Plus? Serial Number?
100% reproducible?
Battery level: Fully charged?
NFC Tag used: Mifare Ultralight?best,
RichardOctober 20, 2016 at 9:07 pm #57017Device: Ipad Air 2
OS: IOS version 10.0.2
Xcode: version 8.0
Reader: Floble Plus(Previously BZR)
100% reproducible: ????
Battery Level: Fully Charged
NFC Tag: NTAG 213October 21, 2016 at 12:10 pm #57023Any update??
Mike
October 21, 2016 at 12:25 pm #57024Hey Mike, seems you’re level of urgency is above the responsiveness we deliver over the Forums. As I mentioned before our Swift support is in beta and not officially released yet. Scott is investigating your issue to provide you some support but doing so while needing to deliver on many other tasks that have higher business value for us. Perhaps you will consider purchasing Flomio Service hours to get the level of attention you need. Otherwise, please bare with us as we juggle through our commitments before getting to your Swift needs.
best,
RichardOctober 24, 2016 at 9:14 pm #57040Hello Richard,
We know we are not your biggest customer so we are not a high value target but we have been consistent with utilizing your products. As it has been a few days, I just wanted to see if there was any update.
Mike
October 25, 2016 at 7:25 am #57044Hi Mike,
The problem here is reproducing your error. I have just built another project in Swift using the swift README using the latest FlomioSDK v2.1(beta) with no issues.
You have been able to get the bridging headers and build settings configured correctly to initialize the reader, it’s very strange that that “checksumFromBuffer” method is causing a crash. There is no mention of that method in our SDK but it could be from the driver.
Any advice now would just be speculative at best other than suggesting that you try to follow the steps in the README with another test project. FlomioSDKv2.1 (beta)Kind Regards,
ScottOctober 25, 2016 at 7:45 am #57046Hi Mike,
From searching the forums, there are a number of mentions of that ‘checksumFromBuffer’ error.
From this post, they suggest adding the linker flag ‘-ObjC’ to your target (In Targets -> YourAppTarget -> Build Settings -> Linking -> Other Linker Flags add ‘-lc++’ and ’-ObjC’) fixes that problem.
Hopefully that resolves the issue for you.Kind Regards,
Scott- This reply was modified 8 years, 1 month ago by Scott.
-
AuthorPosts
You must be logged in to reply to this topic.