iOS, How to get assets from assets.car?

[hubertn62296302]

Hi.

I'm trying to use iOs app slicing in my app. I assume this is possible because here https://forums.adobe.com/thread/2168836​ is showed how to compile and add xcassets folder into ipa. I can't find any other adobe documentation than post above.
I add in Application Descriptor assetCar tag under <iPhone> tag. I didn't add it under <InfoAdditions> <![CDATA> as suggested in post, because ADT refuse to build with descriptor like this. I think InfoAdditions allow only key value tags .

After build and list .ipa directory from app I see Assets.car in package, but I can't find way to get any asset inside it.

Is this is possible or I done something wrong? or maybe I need ane for it.

[Anki_AG_ · Accepted solution]

Hi Hubert,

As of now we are mot supporting iOS App Slicing. As part of AIR 22, we had added support for multitasking. To enable multitasking, we need to add tags in the Application Descriptor as mentioned below

<iPhone>

<multitasking>true </multitasking>

<launchScreen> LaunchScreen.storyboardc </launchScreen>

<assetsCar>Assets.car</assetsCar>

   <InfoAdditions>

     <![CDATA[

     <key>UIDeviceFamily</key>

      <array>

               <string>1</string>

               <string>2</string>

      </array>

      ]]>

   </InfoAdditions>

</iPhone>

As mentioned in the forum 6/16/2016 - Release - AIR 22 Runtime and SDK , assets.car is created through xcode and assets can be viewed in xcode only.

Thanks,

Ankit

Adobe AIR Team

[hubertn62296302]

ok, Thank You.
If you can, please fix xml in this post 6/16/2016 - Release - AIR 22 Runtime and SDK​ .because now it looks like these tags were under InfoAdditions

     <multitasking>true</multitasking>
     <launchScreen>LaunchScreen.storyboardc</launchScreen>
     <assetsCar>Assets.car</assetsCar>
     <key>UIDeviceFamily</key>
     <array>
          <string>1</string>
          <string>2</string>
     </array>
]]></InfoAdditions>

[Anki_AG_]

Hi Hubert,

Glad it worked. Yes you are right about the mistakes in forum post. We will get it corrected.

Thanks,

Adobe AIR Team