For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 7 replies, 4 voices, and was last updated 12 years, 1 month ago by
.
-
Posts
-
edited by support-wayne, Apple removed access to the UUID in ios6. This is not a bug.
I have a user who has what appears (to me anyway) a funky UUID. I have my users install/run UUID viewer from the app store and send me the UUID so I can add it to the device list and generate an updated profile. I’ve not had an install fail but this one did on this device. It’s an iPhone 4S running 7.0.2. I always send a copy of the install to myself and reinstall the app so I can have the same user experience. It works fine on my phone….
The UUID of this particular device begins with ffffffff followed by the rest of the character string. None of the other 20 or so devices have a UUID that begins with this.
Anyone have any insight?
Thank you,
Something’s causing the first part of the UUID to report as all ones. Remember:
1111 (binary) = F (hexadecimal), so a lot of F’s = a lot of 1’s.
No idea why this is happening.
-1TC
Q: can the UDID even be accessed programmically any longer?
In ios6 apple discontinued the old api for access the device id.
The only way I know of to view the device ID now is from itunes.Yup that seems to be it. That makes it very difficult for internal apps that will never make it to the App Store. Now it seems every new device needs to be plugged into iTunes to get the uuid. Doesn’t make the iStuff platform development very developer friendly.
I want to clarify if my post was misunderstood that obviously this is an Apple rant and not directed towards the Mobi folks. My apps are developed for internal company use only. As such they will not go to the App store for general consumption. As such, this UUID thing has a direct impact on me and my ability to deliver my apps as ‘seamlessly’ as possible to my user community. Prior to iOS7 I could add a new device and deliver the app to a new user from anywhere. Obviously, walking a user through connecting to iTunes and getting the UUID is possible but clearly a PITA…I’m confident that this affects others here too.. “That’s one small step for man, One giant leap for mankind (BACKWARDS)” Sorry for the Rant.. but I know you understand..
This odd UUID also caused me some significant issues. Typically we have always used UDID Lite to get the UDID to place into the Apple Development web app. However, UDID Lite reported a similarly formatted ffffff…… UDID, which would never allow the installation to complete. Connecting to iTunes revealed a different UDID, which worked immediately after pasting it into the Apple Dev site and rebuilding the provisioning profiles. This was on an iPhone 5s with iOS 7.0.4.
@DCoudron see the 1st topic of the thread that reports that access to the UDID is no longer available except through itunes. Apple disabled the ios api for access the device id. So all the apps like UDID Lite report an invalid device id.
