App rejected because of my framework about ios-framework HOT 7 CLOSED

I am about to distribute my framework to my clients. I must find out a solution if this is the cause for rejection, if yes anyone has any clues how to fix this ???.

from ios-framework.

Run this find to check if the *.a file include the uniqueIdentifier
$ find .|grep -v .svn |grep ".a"|grep -v ".app"|xargs grep uniqueIdentifier

http://stackoverflow.com/questions/16409966/app-rejected-bui-i-dont-use-udid

from ios-framework.

@gmeroz Thanks

from ios-framework.

I am preparing my library for release. I have ran the find command as suggested in the linked StackOverflow post and have noticed that I get some hits. The one thing to notice is that this only occurs when I run xcodebuild from the command line. Building from Xcode does not result in matches.

I have looked at the matched files and found that these are just matches to the method name (along with all the other method names for UIDevice). I do not use uniqueIdentifier in the code and do not include any third party libraries.

Is there more action that I need to take. I was going to submit a dummy app with the library to Apple with my concerns in the notes, but I think that might be more of a last resort. I am just trying to be prudent and not release this to a client without ensuring this is covered.

from ios-framework.

Not sure if this helps, but I had to eliminate declarations of UIDevice
instance pointers in favour of calling its methods inline via the
currentDevice singleton to rid myself of uniqueIdentifier warnings.

I.e. get rid of these declarations:
UIDevice* device = [ UIDevice currentDevice ]; // I think that's the
singleton accesor...

Just having that "device" local var was somehow evil.

Nick
On Jun 17, 2013 3:01 PM, "Steven Gillan" [email protected] wrote:

I am preparing my library for release. I have ran the find command as
suggested in the linked StackOverflow post and have noticed that I get some
hits. The one thing to notice is that this only occurs when I run
xcodebuild from the command line. Building from Xcode does not result in
matches.

I have looked at the matched files and found that these are just matches
to the method name (along with all the other method names for UIDevice). I
do not use uniqueIdentifier in the code and do not include any third party
libraries.

Is there more action that I need to take. I was going to submit a dummy
app with the library to Apple with my concerns in the notes, but I think
that might be more of a last resort. I am just trying to be prudent and not
release this to a client without ensuring this is covered.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47#issuecomment-19577994
.

from ios-framework.

Thanks @nrichards. I made the same change you suggested (using the singleton directly rather than getting an instance of it locally), now running the find command returns no matches.

from ios-framework.

@swgillan +1 Thanks @nrichards

from ios-framework.