iOS AdHoc Build Weirdness - includes a zip file?

Hi,

Yesterday I switched from a developer provisioning profile to an Ad Hoc profile. Seems to be all looking good at the iTunes Connect end (certificate, AppID, Provisioning profile). Updated Xcode and it appears in the iOS Build dialog in the simulator.

When I build, I get my usual .app archive that I always got on the Developer provisioning profile, but now there is also another archive there - a .zip with the same name.

Why is this happening?

Thanks,

Nathan.

It gets even weirder… the resultant archive (both zip and app) is missing 4 files from my images folder (out of 266). Works fine using my old development provisioning profile, but not the AdHoc one. If I manually add the images into the archive it also works.

Keen to ship my product so any help/advice would be good - something’s not right here.

The Zip file is what you would distribute to Apple through the app uploader.  It’s harmless that it produces both.

What are the four images?  Anything special about them? 

They are png images I use in the background. Have listed some details to see if you can spot anything…

MenuBgHigh.png - 320x568 - 22k

MenuBgHigh@2x.png - 640x1136 - 130k

MenuBgWide.png - 360x480 - 21k

MenuBgWide@2x.png - 720 x 960 - 121k

If device.isTall I use the High version, and if it’s not I use the wide version.

I worked around this for testing by just copying the files into the app archive, but now I want to upload to the App Store and I can’t just add images to the archive as it breaks the signature.

Even if you can let me know how to re-sign it after I put the files back in that would be good.

Thanks,

Nathan.

Can you watch the console log as your app builds and look for errors?  It’s possible those images might be causing problems for png_crush causing Xcode to spit them out.  If you want to put them up on dropbox or somewhere I can get to them, I’ll be happy to look at the images and see if there is something amis with them.  You might want to just for fun open them up in Photoshop or what ever image editor you use and make sure they are saved as a 24bit (in photoshop terms, they don’t count the alpha channel) 32bit (in other peoples terms) RGB PNG files and make sure they are not Indexed 8 bit (should work, but just to be safe).  

Good call - I watched the console and it says “Not a PNG file…” which is a bit weird - it’s been working on the dev provisioning profile. Will quickly recreate them and let you know how I go.

The development profile doesn’t run png_crush.

Turns out they were jpg files that I saved with a png extension - sorry - noob error.

Saved them as jpg and I’m working again.

Thanks Rob.

Nathan.

It gets even weirder… the resultant archive (both zip and app) is missing 4 files from my images folder (out of 266). Works fine using my old development provisioning profile, but not the AdHoc one. If I manually add the images into the archive it also works.

Keen to ship my product so any help/advice would be good - something’s not right here.

The Zip file is what you would distribute to Apple through the app uploader.  It’s harmless that it produces both.

What are the four images?  Anything special about them? 

They are png images I use in the background. Have listed some details to see if you can spot anything…

MenuBgHigh.png - 320x568 - 22k

MenuBgHigh@2x.png - 640x1136 - 130k

MenuBgWide.png - 360x480 - 21k

MenuBgWide@2x.png - 720 x 960 - 121k

If device.isTall I use the High version, and if it’s not I use the wide version.

I worked around this for testing by just copying the files into the app archive, but now I want to upload to the App Store and I can’t just add images to the archive as it breaks the signature.

Even if you can let me know how to re-sign it after I put the files back in that would be good.

Thanks,

Nathan.

Can you watch the console log as your app builds and look for errors?  It’s possible those images might be causing problems for png_crush causing Xcode to spit them out.  If you want to put them up on dropbox or somewhere I can get to them, I’ll be happy to look at the images and see if there is something amis with them.  You might want to just for fun open them up in Photoshop or what ever image editor you use and make sure they are saved as a 24bit (in photoshop terms, they don’t count the alpha channel) 32bit (in other peoples terms) RGB PNG files and make sure they are not Indexed 8 bit (should work, but just to be safe).  

Good call - I watched the console and it says “Not a PNG file…” which is a bit weird - it’s been working on the dev provisioning profile. Will quickly recreate them and let you know how I go.

The development profile doesn’t run png_crush.

Turns out they were jpg files that I saved with a png extension - sorry - noob error.

Saved them as jpg and I’m working again.

Thanks Rob.

Nathan.