You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I can see, all the beacon examples use 0x4c00 (Apple) as a company ID in the advertisement payload.
There is also some code that checks if company ID equals 0x4c00, but only for nearby scanning.
My question: is it necessary to use 0x4c00?
I've tried changing it to 0x0100 and reports stopped appearing in OpenHaystack. Is it Apple's limitation or my fault?
If it's Apple's limitation, how would 3rd-party MFi beacons work then? I bet they won't use Apple's company IDs in adv packets.
The text was updated successfully, but these errors were encountered:
As I can see, all the beacon examples use
0x4c00
(Apple) as a company ID in the advertisement payload.There is also some code that checks if company ID equals
0x4c00
, but only for nearby scanning.My question: is it necessary to use
0x4c00
?I've tried changing it to
0x0100
and reports stopped appearing in OpenHaystack. Is it Apple's limitation or my fault?If it's Apple's limitation, how would 3rd-party MFi beacons work then? I bet they won't use Apple's company IDs in adv packets.
The text was updated successfully, but these errors were encountered: