Corrupted Binaries?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Corrupted Binaries?

Mike Kerner via use-livecode
Ok, so I uploaded my app to Apple and this is what I got back:

----------------

Dear developer,

We have discovered one or more issues with your recent delivery for "myAppName". To process your delivery, the following issues must be corrected:

Invalid Binary - The app contains one or more corrupted binaries. Rebuild the app and resubmit.

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

-------------------

Anyone know what they might be talking about?   There are no files being copied in (“Copy Files” section of the App Settings).    Is this because I checked “Disable ATS”?

-Dan

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Corrupted Binaries?

Mike Kerner via use-livecode
Hi Dan,

On 2017-08-25 00:16, Dan Friedman via use-livecode wrote:
> Anyone know what they might be talking about?   There are no files
> being copied in (“Copy Files” section of the App Settings).    Is this
> because I checked “Disable ATS”?

It would appear as if Apple have 'done something' recently with the
checks they perform on binaries. This is the third report of a problem
we've had and are currently looking into it.

We found this article online (related to Adobe products, but they do a
'similar' thing for iOS builds to us):

https://helpx.adobe.com/digital-publishing-suite/kb/itunes-connect-rejection-invalid-binary.html

Basically they suggest "Deselect "Enable For iCloud", "Enable for
Passes" and/or "Enable for Data Protection"" and regenerate the
provisioning profile. Now, it might not be one of these three things,
however it could be that there is a mismatch between the settings you
are generating for the provisioning profile, and the settings in the
S/B.

Sorry I can't provide any more assistance at the moment - we are still
trying to work out exactly what the problem is!

Warmest Regards,

Mark.

--
Mark Waddingham ~ [hidden email] ~ http://www.livecode.com/
LiveCode: Everyone can create apps

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Corrupted Binaries?

Mike Kerner via use-livecode
On 2017-08-28 11:04, Mark Waddingham via use-livecode wrote:
> Sorry I can't provide any more assistance at the moment - we are still
> trying to work out exactly what the problem is!

I think we found the problem:

http://quality.livecode.com/show_bug.cgi?id=20308

Apple clearly upgraded their toolchains in their App submission process
which has uncovered a small error in the 64-bit Mach-O (executable)
files generated for iOS devices - it doesn't affect execution, but the
newer toolchains flag an error which is presumably why a 'corrupted
binary' message is being sent for builds in the last week or so.

Warmest Regards,

Mark.

--
Mark Waddingham ~ [hidden email] ~ http://www.livecode.com/
LiveCode: Everyone can create apps

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode