iOS doesn't see my Beacon

[Mark W. Schumann]

I read this post with great interest!

devzone.nordicsemi.com/.../

I'm having a similar problem with my Nordic Beacon application. I followed the advice to switch my advertised Company ID to 0x4C, but my iOS application still doesn't see the (spoofed) iBeacon. Specifically, my Nordic device doesn't show up when I make the .startRangingBeaconsInRegion API call, even though I'm advertising it with an Apple Company ID.

Is there anything else about the Beacon advertising format that I need to know about to get iOS to see it? I'm using the ble_app_beacon example as my starting point.

To clarify, I do see my spoofed iBeacon when I run the nRF Connect application on my Android phone, and it shows as an iBeacon with Company: Apple, Inc. <0x004C> and Type: Beacon <0x02> as expected. It simply doesn't appear when I attempt to "range" beacons in my iPhone app.

[Stefan Birnir Sverrisson]

Hi Mark

Check out the last section on this thread, the "Update beacon parameters from the IOS Beacon app" section. You should add a "proprietary beacon" in the app in order to see a non-connectable beacon.

[Mark W. Schumann]

Turns out, by the time I got to the point of asking this particular question, my problem was in the iOS application. Setting up the "region" can be pretty persnickety, but it's not a Nordic issue! Thank you.