Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
In short, calling to get the physical address of a network interface mangles the address. Of the 6 segments that comprise a MAC address the first 3 become the last 3 and the last 3 are all 0.
Obj-C MAC: 00:16:CB:CB:BC:3B
MonoTouch MAC: CB:BC:3B:0:0:0
For more information please see:
On-going discussion, source code and reference URLs
It has also been reported that this is an issue in OSX in addition to iOS.
I'll take a look at this.
Fixed in master/c89f1eb, mono-2-10/a02076b
Exciting news, will there be a build soon that includes this fix? This is huge since Apple killed the device unique identifier!
Any news on when this will be released or is there any work around?
It will be released with MonoTouch 5.0.4 (which should be coming later this month).
Just a note, it should be released with MonoTouch 5.0.5 since 5.0.4 is already released :)
Should the fix be in the 5.1.1 branch? I'm asking because it is not.
No, this was fixed after 5.1.1 was released. It will be in 5.1.2 though.
Is it possible to use some source code from Github and include it directly in my app so I could have access to the MAC address even before 5.1.2 is released?
oh no! it didn't make it in 5.1.1... as Rene, is there anyway we can fix it ourselves?
I have an app update I need to get through and this is one of the last bits that is holding it up now.
Dean: you can get 5.1.2, which came out just now :)
Thanks Rolf, just hit Check for Updates and here it comes! yay!