BeaconParser for iBeacon

[mrtree1]

Quick and obvious question: What's the parsing string for iBeacons?

I'd like to use this library, but I need to support iBeacons as well, and I'm currently using the previous iBeacon library.

[ghost]

The solution in this post on Stack Overflow worked for me:

http://stackoverflow.com/questions/25027983/is-this-the-correct-layout-to-detect-ibeacons-with-altbeacons-android-beacon-li
On 11 Aug 2014 10:47, "Tree" notifications@github.com wrote:

Quick and obvious question: What's the parsing string for iBeacons?

I'd like to use this library, but I need to support iBeacons as well, and
I'm currently using the previous iBeacon library.

—
Reply to this email directly or view it on GitHub
#13.

[mrtree1]

Thanks Justin, that works for me.

It would seem fairly natural to want iBeacon support built into this library, or at least have a clearer indication of what to do for them given the old iBeacon library page redirects to this project. Is there a legal reason to avoid mentioning iBeacons in the readme?

[davidgyoung]

Apologies for the somewhat vague response... the library is intentionally designed to be free of intellectual property. Frustrating as it is, providing explicit instructions on how to use the library with specific proprietary beacons is impossible without bringing that property into the library documentation. The end result is that if you want to use the library with proprietary beacons, you have to find this information on third party sites.

[mrtree1]

Thanks for clarifying the reasoning David. I understand the rationale. At least there is a link to the solution directly from the project now :-)