"The resulting API analysis file is too large. We were unable to validate your API usage prior to delivery. This is just an informational message.".

Solar2D iOS
#1

Just uploaded using the uploader manually . I have recently just updated to Xcode 6. Anyone know what the ‘’’’ this means?

“The resulting API analysis file is too large. We were unable to validate your API usage prior to delivery. This is just an informational message.”.

I always worry whenever I update Xcode as these things happen. Im guessing this is connected to not being able to use the IOS simulator either

Grrr

#2

Can you reproduce this?

Thanks

Rob

#3

I tried it twice in a row and it happened both times. I figured it might have been a bug with Apple but wasnt sure. I ignored it and it seems submitted now. I cant try again as I would have to reject it and Ive already done this 3 times.

#4

Can you reproduce this?

Thanks

Rob

#5

I tried it twice in a row and it happened both times. I figured it might have been a bug with Apple but wasnt sure. I ignored it and it seems submitted now. I cant try again as I would have to reject it and Ive already done this 3 times.

#6

i have seen this warning today,and is strange because the code is the same than previous builds, and i have never seen it before.Anyway it is only a warning.

#7

I got this error today too.

I found this:

http://stackoverflow.com/questions/21257597/the-resulting-api-analysis-is-too-large-when-upload-app-to-mac-store

Dave

#8

i have seen this warning today,and is strange because the code is the same than previous builds, and i have never seen it before.Anyway it is only a warning.

#9

I got this error today too.

I found this:

http://stackoverflow.com/questions/21257597/the-resulting-api-analysis-is-too-large-when-upload-app-to-mac-store

Dave

#10

I once had this problem.  
The cause turned out to be renaming the build file and having two build files in the Payload folder.  
Deleted both and put a fresh copy of the build in Payload and everything worked fine.

#11

I once had this problem.  
The cause turned out to be renaming the build file and having two build files in the Payload folder.  
Deleted both and put a fresh copy of the build in Payload and everything worked fine.