May 21, 2018 at 2:44 pm #62989
I just purchased the Flomio SDK pro version, v2.3, and am having trouble getting started. Normally I’d work on it myself for a while before coming to a forum but in the interests of saving time – here I am. Apologies in advance if this isn’t the right place to post this.
What I’ve done so far:
1. Purchased an ACR35 directly from one of ACS’ distributors, GoToTags. This was before I became familiar with Flowmio. I’m not sure if the OEM unit will work with the Flomio SDK – hopefully that’s not an issue.
2. Verified that the device works using the ACS “AJ Demo” utility. Per that utility the firmware version is ACR35 V1.08.
Using TestFlight I attempted to use the Flomio “Test” app – when I start it, I can logon and it turns the green light on but nothing else seems to work (i.e., I tap, nothing happens).
3. Purchased the pro SDK v2.03, and ran through the install steps. I had to manually add libSDKClassesPro.a to “Linked Frameworks and Libraries”, not sure if that might be a sign something else is wrong. If it’s OK, maybe that should be added to the installation steps.
Note: in the online documentation I see links to SDK v3.01. Do I have the current version?
4. Copied the various pieces of code in README.swift.cmd into my project as a starting point.
5. Started my app using “DeviceType.kFlojackMsr” in the config.
6. When my app starts up I see the following error and it crashes. This looks a lot like the forum entry “NSInvalidArgumentException” posted by Olcay on 4/6/2018. I tried removing / re-adding the SDK to ensure all the files are there but keep getting the error.
2018-05-21 14:20:11.042951-0400 Urbanautics[4344:3145347] In Init 2018-05-21 14:20:11.043030-0400 Urbanautics[4344:3145347] bundle(null) 2018-05-21 14:20:11.043514-0400 Urbanautics[4344:3145347] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSURL initFileURLWithPath:]: nil string parameter' *** First throw call stack: (0x1847ded8c 0x1839985ec 0x1847dec6c 0x18513bef0 0x18513be5c 0x104794274 0x104793b1c 0x1059c9220 0x1059c9f34 0x104793a5c 0x104771c88 0x10477dc44 0x1047818c8 0x1059c9260 0x1059c9220 0x1059cddb0 0x184787070 0x184784bc8 0x1846a4da8 0x186687020 0x18e68578c 0x104770118 0x184135fc0) libc++abi.dylib: terminating with uncaught exception of type NSException
Any insight would be appreciated – thanks!
HalMay 21, 2018 at 8:53 pm #62990
Hey Hal, this is the best place to post. Sorry for the issues you’re having, we’ll get you going. First step is to get the Flomio Test app working. If the AJDemo worked for you there shouldn’t be any issue with Flomio Test. Make sure your host device volume is all the way up and only plug in the reader after selecting “Flojack MSR” from the launch menu. It should go something like this:
Firmware version v1.08 is the latest from ACS so you’re good there. I just tested with the latest Flomio Test release and seems the reader state is not being reflected properly and is showing “Disconnected” even though it interrogated tags ok. This may have a been a bug we recently introduced since the app has been undergoing updates. I’ll check on that and get back to you. Either way, you should be able to send get any ISO14443A/B tag to be detected by holding it up the reader and hitting “send” for the default read APDU command
FF B0 00 04 10
RichardMay 23, 2018 at 5:23 am #62997
A couple of things to try also:
Seems like it’s similar to that issue. Try dragging the ScanSound.caf file into your project so that it’s in your projects main bundle.
Another thing to try is to use Cocoapods which will make sure all the build steps are correct. Still keep the ScanSound.caf file in your project root.
June 17, 2018 at 1:22 pm #63185
- This reply was modified 5 months ago by Scott.
Hey Guys – thanks for the reply. Turns out it was the same issue another user had where it couldn’t find ScanSound.caf; thought I had addressed that but I had not. Once that was fixed it’s working.
Thanks!June 18, 2018 at 6:55 am #63188
Good to hear. Glad you got it working!
The topic ‘Newbie / getting started – NSException on startup’ is closed to new replies.