Notes on Apple Core Bluetooth Peripheral ID

  • The only peripheral ID that Core Bluetooth API offers after discovery is CBPeripheral.identifier.
  • Not MAC address.
    You can’t get MAC address via Core Bluetooth. There is no public API for this. If this is an internal or jailbreak application you can get the value of the kLockdownBluetoothAddressKey key via liblockdown.dylib.
  • It’s obtained via callback function didDiscoverPeripheral. (iPhone acts as central device)
  • Type is NSUUID, not CBUUID. UUID is deprecated as of iOS 7.0.
  • identifier has been moved to CBPeer class, which is base class of CBPeripheral. So net effect is the same.
  • A different central will return a different id for the same peripheral.
  • A central will return the same id for a peripheral. Thus, it can be stored and used later per Apple doc.
    However, I don’t know how long it will return the same id.
    Important: assuming the peripheral doesn’t use Bluetooth 4.0 Privacy feature, which changes its ID periodically.
  • Peripheral MAC & central id (& possible time) is used (by Core Bluetooth) in generating this CBPeripheral.identifier.
Advertisements
Notes on Apple Core Bluetooth Peripheral ID

Interesting about android NFC whitelist nfcee_access.xml file

Since the wallet only works if its signature is in this whitelist file, we can deduce the business strategy.
Below is the list of app signatures in whitelist nfcee_access.xml file in different popular android phones:

– Nexus S, Nexus 4: Google wallet (of course).
I guess this is only way I get Google Wallet if you have T-Mobile & AT&T.
– Verizon Note 2: VZW ISIS + VZW CERT.
ISIS Wallet only.
– T-Mobile GS4: ISIS development + production.
ISIS Wallet only.
– International GS3: Google wallet + Samsung wallet.
Samsung has its own wallet too.
– Sprint GS3: Google wallet
– Sprint GS4: Google wallet + Sequent Wallet.
Reflecting Sprint new business deal with Sequent.

Interesting about android NFC whitelist nfcee_access.xml file

Xcode Error – Could not launch app – No such file or directory

I got this annoying error with Xcode 4.6.1: Could not launch app – No such file or directory Error.

Xcode was working for me for awhile without problem with my iPhone. A friend wanted me to install an app on his phone. And I got this error.

It turns out that the “Deployment Target” (=IOS 6.0) is higher than that on the phone IOS 5.1.1.

I hope it helps,

Xcode Error – Could not launch app – No such file or directory

iOS console log using ASL

If you want to get iOS console log, you can use below code:

NSMutableArray* mainList = [NSMutableArray array];
aslmsg q, m;
int i;
const char *key, *val;
q = asl_new(ASL_TYPE_QUERY);
aslresponse r = asl_search(NULL, q);
while (NULL != (m = aslresponse_next(r)))
{
    NSMutableDictionary *tmpDict = [NSMutableDictionary dictionary];
    for (i = 0; (NULL != (key = asl_key(m, i))); i++)
    {
        NSString *keyString = [NSString stringWithUTF8String:(char *)key];
        val = asl_get(m, key);
        NSString *string = [NSString stringWithUTF8String:val];
        [tmpDict setObject:string forKey:keyString];
    }
    [mainList addObject:tmpDict];
}
aslresponse_free(r);
iOS console log using ASL

iOS accessory bug:

After extensive testing, I found a big IOS external accessory bug in iOS 5.x.x – 6.1.2 detailed below.
I submitted the bug to Apple and got confirmation that they are aware of it but they can’t share anymore detail. A fix may be in next version! Standard Apple secret procedure.

EAAccessory object returns no protocol string (even with accessory attached) after iPhone wakes
up from deep sleep
Steps to Reproduce:
– Put iPhone with app into sleep for 3 hours (or overnight) by pressing power button.
– Wake up iPhone using home/power button.
– Print out the protocol string as below:
NSArray *accessories = [[EAAccessoryManager sharedAccessoryManager] connectedAccessories];
for (EAAccessory *eaa in accessories) {
NSLog(@”protocol %@”, eaa.protocolStrings);
}
– We tried to put in 6s retry timer but it doesn’t help.

iOS accessory bug: