This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRFBeacons does not build

Howdy,

I just got my nRF51822 Bluetooth Smart Beacon Kit. I down loaded "nRF Beacon iOS_1.0.zip" and fixed up the project and targets so that it was using the correct Code Signing profiles.

When I try to build the project in XCode 6.0.1 on an iPhone 5 with iOS 8, I get 6 errors:

            BeaconsViewController.m:96:22: error: multiple methods named 'enable' found with mismatched result, parameter type or attributes
            BeaconsViewController.m:96:22: error: bad receiver type 'BOOL' (aka 'signed char')
            BeaconsViewController.m:381:23: error: multiple methods named 'enable' found with mismatched result, parameter type or attributes
            BeaconsViewController.m:381:23: error: bad receiver type 'BOOL' (aka 'signed char')
            BeaconsViewController.m:467:15: error: multiple methods named 'enable' found with mismatched result, parameter type or attributes
            BeaconsViewController.m:467:15: error: bad receiver type 'BOOL' (aka 'signed char')

After fixing up the code by casting the objects from the array to what I expect to be the Beacons class, for example:

            Beacons *beacon = self.beacons[beaconIndex];

When I build the app and follow the instructions, it never finds the beacon. I am able to follow the Update instructions and re-configure the Beacon -- which means I can find the beacon to reconfigure, but can't find the beacon when in Beacons mode. It keeps telling me Beacon Not Found.

This is a bit disappointing -- was hoping it would work out of the box. Any help will be greatly appreciated.

EDIT: I downloaded the app from the AppStore, and it also does not work.

UPDATE: I am able to get the app to work in an iOS 7 device with no problem. This means that the code and the apps functionality is broken on iOS8, which is seriously problematic.

Cheers, Bryan

Parents
  • Apple has added a filter on iOS 8 that filters on the content of the beacon package. So unless the beacon is using the correct packet structure it will not be visible in iOS8.

    The information on the packet structure needed is available from Apple under the MFI and iBeacon licensing. To prevent users outside this licensing to get access to this we have implemented the beacon code to by default not be iBeacon compatible.

  • Q1: It's an application, but you figured this out. Q2: No, no renaming should be needed. Q3: Push the button when you connect power/battery. As you say, it will time out, if it does, just re-enable the bootloader mode when you have the app and file ready.

    Q4: Doesn't work on Android. Yes, the Android app will filter on Nordic company ID. We hope to have a fix to this soon as well so that beacons can be read independently of smart phone platform.

Reply
  • Q1: It's an application, but you figured this out. Q2: No, no renaming should be needed. Q3: Push the button when you connect power/battery. As you say, it will time out, if it does, just re-enable the bootloader mode when you have the app and file ready.

    Q4: Doesn't work on Android. Yes, the Android app will filter on Nordic company ID. We hope to have a fix to this soon as well so that beacons can be read independently of smart phone platform.

Children
No Data
Related