Update: This appears to be a dup of another post (a bug report, also posted today)
Has anyone been able to export to iOS using a signing key (to create an .ipa file)?
2.1.0, 2.2.0, latest
Basic description of the problem:
When compiling a Construct2 Cordova export for iOS and using a signing key, Cocoon will produce a .zip result that does not contain an .ipa file, but rather an .ipa folder within an archive that appears to be corrupt or malformed.
Despite the result.zip being about 30MB, the archive only shows and extracts only the below 3 files, which only amount to about 69KB.
The folder contains only these 3 files.
This workflow has been great for months. All I’ve done is upload a new build from Construct and it no longer works. I understand that the .ipa file is basically an archive itself, so that isn’t part of the confusion. I’ve tried different Cocoon versions, archive utilities… created a new signing key… something appears to have changed server-side.
I’m using Windows 10 for the most part. if I try to extract the result.zip on a mac, I get an “Error 2”.
Windows 10, El Capitan.
Steps will reproduce the problem:
- Export something to Cordova using Construct r255
- Compile it in Cocoon for iOS, using a known good signing key.
- Observe the result zip file produced
I’m expecting a .ipa file that I can load onto my iPad for immediate as has always been the case.
I use the same certificates and Construct export that have been working for several months… creating a new signing key does not seem to help.
The compilation is successful, I just don’t get an .ipa file inside the result.zip as I did before. I get a folder
(Also happens on Webview, Webview+)
Used plugins (if relevant):
Framework/game engine (if relevant):
Construct 2 r255