[TIMOB-7859] iOS: Ti.platform.macaddress returning UUID
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Won't Fix |
Resolution Date | 2012-04-05T10:11:11.000+0000 |
Affected Version/s | Release 2.0.0 |
Fix Version/s | n/a |
Components | iOS |
Labels | n/a |
Reporter | Ian Howarth |
Assignee | Stephen Tramer |
Created | 2012-03-01T15:54:51.000+0000 |
Updated | 2017-03-22T17:20:43.000+0000 |
Description
Ti.platform.macaddress returns UUID
var window = Ti.UI.createWindow();
var view = Ti.UI.createView({
backgroundColor:'white'
});
window.add(view);
window.open();
var macAddress = Ti.Platform.macaddress;
var label = Ti.UI.createLabel({
text:'macAddress \n' + macAddress,
top:-100,
left:20
})
view.add(label);
var uUID = Ti.Platform.id;
var label2 = Ti.UI.createLabel({
text:'UUID \n' + uUID,
top:100,
left:20
})
view.add(label2);
Steps to reproduce;
Run the code.
Result;
Ti.platform.macaddress and Ti.platform.id return UUID
Expected;
Ti.platform.macaddress should return Mac Address
Apple has stated they are removing access to the macaddress and attempting to do so may cause app submission issues. We cannot guarantee continued access to the macaddress, but will investigate this issue.
Raising to blocker status as this will cause apps to fail verification since this is accessing the UDID. Unsure if Apple will have an issue with the MAC address per se.
This should be handled as part of TIMOB-8173 (and is in fact covered in the documentation for the pull request for it). Going to mark it a duplicate. Although Apple is not yet blocking apps for macaddr access, I anticipate that they will be doing so for raw macaddr as it is what the current UDID is likely hashed from and falls under the umbrella of "unique device identifier".
Actually going to mark this WON'TFIX, for two reasons: * Eric's blocker update is related to TIMOB-8173 * Apple's UDID deprecation/reject policy does not appear to be leading to immediate macaddr rejections, but I anticipate that they will be checking for apps which access the raw macaddr as it is a "unique device identifier".
Closing ticket as the issue will not fix and with reference to the above comments.