Skip to main content
oliversen
Inspiring
January 19, 2018
Answered

Publishing error: "Error creating files. Namespace is invalid in the application descriptor file

  • January 19, 2018
  • 1 reply
  • 974 views

I am trying to publish an application with the Admob ANE. I get this error "Error creating files. Namespace is invalid in the application descriptor file."

Anyone who have had this issue earlier?

<?xml version="1.0" encoding="utf-8" standalone="no" ?>

  
<application xmlns="http://ns.adobe.com/air/application/26.0">
  
<id>NorskRadioUtenAir</id>
  
<versionNumber>1.0.0</versionNumber>
  
<versionLabel/>
  
<filename>NorskRadioUtenAir</filename>
  
<description/>
  
<name>NorskRadioUtenAir</name>
  
<copyright/>
  
<initialWindow>
  
<content>NorskRadioUtenAir.swf</content>
  
<systemChrome>standard</systemChrome>
  
<transparent>false</transparent>
  
<visible>true</visible>
  
<fullScreen>false</fullScreen>
  
<aspectRatio>portrait</aspectRatio>
  
<renderMode>cpu</renderMode>
  
<autoOrients>false</autoOrients></initialWindow>
  
<icon/>
  
<customUpdateUI>false</customUpdateUI>
  
<allowBrowserInvocation>false</allowBrowserInvocation>

  
<android>
  
<manifestAdditions><![CDATA[<manifest>
  
<uses-permission android:name="android.permission.INTERNET"/>
  
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>   <application>
  
<meta-data android:name="com.google.android.gms.version" android:value="4323000" />
  
<!-- should be android:value="@integer/google_play_services_version" -->
  
<activity android:name="com.google.android.gms.ads.AdActivity" android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize"/>
  
</application>
  
</manifest>]]></manifestAdditions>
  
</android>
  
<extensions>
  
<extensionID>com.pozirk.ads.AdMob</extensionID>
  
</extensions>
  
</application>

This topic has been closed for replies.
Correct answer kglad

update to air 27 and retest.

1 reply

kglad
Community Expert
kgladCommunity ExpertCorrect answer
Community Expert
January 19, 2018

update to air 27 and retest.

oliversen
oliversenAuthor
Inspiring
January 21, 2018

Thank you kglad! I updated from AIR26 to AIR 28 And I didnt get the error

kglad
Community Expert
Community Expert
January 21, 2018

you're welcome.