PackageInspectionFlash error when developing FlashBuilder, Adobe AIR, and iOS

Question

Creating an iOS application using FB4.7 Premium, Air 3.4. This is currently a very simple test framework. Suddenly, the builder throws PackageInspectionFailed errors and does not complete the assembly. No explanation why. The simulator is working fine.

I should note that I built and packaged this product directly on my iPad all day without any problems. Suddenly I get this error and the application no longer builds. The last thing I did was add this line: text.autoSize = TextFieldAutoSize.LEFT;

Update

After UNDOing these changes, I get a new error (is this progress?) ApplicationVerificationFailed . Again without further information. I did not change certificates, did not create parameters or anything else.

Interestingly, manually dragging and dropping the generated .ipa into iTunes and then syncing with the iPad really installs the application without errors. It just adds many steps to my testing / debugging process.

What is this mistake? What are some of the conditions that I should look for that may cause an error?

Please vote for Adobe Bugbase

I posted an error here for 3.9: vote: https://bugbase.adobe.com/index.cfm?event=newBug

Sarah Northway has another error report for 3.8 here: vote: https://bugbase.adobe.com/index.cfm?event=bug&id=3650414

Let me get some Adobe eyes on this - you need to provide more information about the causes of this error.

Answer 1

It happened to me intermittently several times today, it seems to have worked when I updated the AIR SDK to 4.0, and also when I updated some of my own app.xml settings data.

After a short period of swearing, searching and finding people in Flash Builder, I found that cleaning up the project did the trick.

 Project -> Clean... -> Clean All Projects 

Answer 2

There seem to be a few issues that will lead to this exact error, but two for checking:

Includes the extension pack in the xml application file under node, but forgets to include it in your actual project. So, for example, the command .ane / .swc.

A version of the same application is already on the device, but using different certificates. For instance. client distribution certificate compared to your test certificate.

And very rarely, mine cannot be installed if the application is still running in the foreground.

Answer 3

all of a sudden, without moving the USB cable, I get this error when installing several times in a row on an ios device.

The fix for me was to press the home button on the device to close the application before unattended installation. If I relied on the compiler to automatically close the application, it sometimes stopped with this error.

Answer 4

I found this error intermittently in AIR 3.8 on Windows 7. I have no idea what starts it (not with a code change), but restarting the computer seems to fix it for a while, until it accidentally starts to repeat itself. I discovered a bug for him, and Adobe suggested we vote for a fix:

https://bugbase.adobe.com/index.cfm?event=bug&id=3650414

Answer 5

Just in case...

In my project, there was a conflict between the NOT BEING ABLE developer certificate for processing push notifications and application.xml, which used it in the "Permissions" tag

 <Entitlements> <![CDATA[ <key>aps-environment</key> <string>development</string> ]]> </Entitlements> 

Comment on this block or upload a certificate that supports push-notificaton.

Answer 6

For me, this happened when I started testing a device that has not yet been registered in the training profile.

Answer 7

I'm still not quite sure what causes this, but this happens most often when updating a packaged asset or replacing another asset with the same name.

What is strange about how the FB handles packaged assets is that they are automatically copied (in the background) to the bin-debug folder. this copying occurs no later than when you create / debug, but you can rejoice almost immediately as soon as you drag the asset into a folder identified as a resource folder (that is: it already contains some packed assets).

The solution for me was to open bin-debug and completely remove it from all packaged assets. Then open the "Properties" in the project and go to the settings "Packaging", Reset to "Default", and then go in and check / uncheck the boxes with the assets that you want to pack. Apply the changes and wait for the files to be copied. Then try assembling / debugging again, and usually everything works.

The bonus aspect of this is that your bin-debug folder is cleared of any fissured that can be accumulated from older, now no longer used, assets. they simply clutter up your package settings and in the worst case, they can end up in the final packaged product, unnecessarily inflating it.

Answer 8

I will simply document the causes of this error until Adobe publishes any official information about it (or they make their error messages more specific / descriptive).

Potential reason: SWF compression with LZMA compression

Solution: Configure the compression settings in the Publish Publish Settings dialog box to deflate. The file size will increase significantly, but it will pass the package check.

Answer 9

I had similar experiences. A new mobile Actionscript project. ”In the main class, draw a square to have a visible indication of the funtioning code and trace actions also in the constructor of the main class to check if debugging is alive.

I could not transfer the application to the device via USB until I uninstall the current iTunes installation and install the itunes version for old video cards. http://support.apple.com/kb/DL1784 (I am running Windows 7 on the fairly new macbook pro, but what the hell).

Now the application can be tested using "run" on the device, but debugging will still not work (s).

The strange thing ... Then I added some link icons in the xml file of the application descriptor (they are commented out by default).

For unknown reasons, adding these icons makes packaging, porting to the device via USB, and debugging work.