it is not yet clear if this is causing problems for app store
rejections, since right now it is just rumors that are spreading
without anybody giving real details of such rejections. We
submitted our own apps with this code in the app and will monitor
also the web further.
We are also looking into easy ways to modify the SDK to make the
beta version still being able to use the UUID information and being
app store safe. If you want to be 100% safe right now, you can
change the code you posted and always use return
@"invalid" and remove the other lines for app store by e.g.
using #ifdef CONFIGURATION_AppStore statements. (The
exact line may differ on your setup depending on your configuration
yes, for beta tests we do need to UDID, because otherwise we
would need the users in your app to always setup an account on our
site to be able to provide in-app updates and collect test
statistics. Also we would need the user somehow to identify the
device if he has multiple. So we need to compare the device to the
devices in the provisioning profile. Things are just getting very
complex all over the place.
But as I said, it is only used and needed for beta testing. So
we just published updated versions of the SDKs which move the UDID
check into delegate methods that you have to implement. So you can
make sure using the proper #ifdef statement that the
UDID is only grabbed when building the beta version but not when
building for the app store. That way the code will not be present
in the binary at all.
I just downloaded your latest SDK: do you still maintain
CNSHockeyManager that used to encapsulate both QuincyManager and
I'm using it, so it would be nice to have a ready-to-use SDK with
the latest fixes regarding UDIDs.
I found no trace of it in this release.
Oh and by the way, now JSONKit is now provided again in the
we updated both the combined SDK and HockeyKit / QuincyKit
yesterday night and removed all references to the UDID. Instead,
you should implement a delegate method
customDeviceIdentifier and return nil for your
store builds / the UDID for beta builds. A blog post on this is
coming later today.
We added the version information into the SDK as a define only 2
version ago. So if you don't find the string "#define SDK_VERSION"
in your files you are on a version released before March. We'd
encourage you to update to the latest version.
you can update HockeyKit & QuincyKit as you have them now,
no problem at all. The combined HockeySDK is where most of the
future development will go into. So sooner or later it would be
helpful to migrate. Right now it is basically a wrapper class
around both SDKs with support for a Jira SDK. So it is up to you
We haven't used SVN for a while, not sure what the reason for
your headaches is. Maybe the easiest solution is to remove the
files, commit, then re-add them.
CrashReporter.framework hasn't got any UDID-related changes (it
didn't use the UDID anyway), but we made a bugfix about 2 months
ago which fixes a bug in the crash log when your app name incudes a
UTF char (like ä or é).
Yeah I think that is what I end up doing. I think it is because
svn treats them as folders and is a little stupid on the matter. I
end up having to delete, commit and then readd them.
On another note how is the best method of getting the udid sent
on the crashes for betas so that the user appears in the meta
section of the crash? Since removing the alwayssensudid (from
memory) it doesn't tie these up.