adobe air 3.2.0 android - custom uri issue

Custom URIs are no longer registered/handled by the adobe air wrapper on android devices.

Tested on evo4g with android 2.3.5  and galaxy tab with android 3.2.

How to reproduce:

create your apk with adt having these settings in your application.xml / android / manifestAdditions / manifest / application:

<activity android:name="helpNav">

  <intent-filter>

    <action android:name="android.intent.action.MAIN" />

    <category android:name="android.intent.category.LAUNCHER" />

  </intent-filter>

  <intent-filter>

    <action android:name="android.intent.action.VIEW" />

    <category android:name="android.intent.category.DEFAULT" />

    <category android:name="android.intent.category.BROWSABLE" />

    <data android:mimeType="application/pdf" />

  </intent-filter>

  <intent-filter>

    <action android:name="android.intent.action.VIEW" />

    <category android:name="android.intent.category.DEFAULT" />

    <category android:name="android.intent.category.BROWSABLE" />

    <data android:scheme="http" android:host="www.this-so-does-not-exist.com" android:path="/something" />

  </intent-filter>

</activity>

How to test:

Open the browser and navigate to http://commonsware.com/sample and click any of the given links. Your air application will not be presented as an intent provider.

More traces captured with DDMS:

04-02 19:47:06.602: I/ActivityManager(128): Starting activity: Intent { act=android.intent.action.VIEW cat=[android.intent.category.BROWSABLE] dat=http://www.this-so-does-not-exist.com/something cmp=android/com.android.internal.app.ResolverActivity } from pid 10018

Simple schemes like <data android:scheme="myscheme" /> dont work anymore either.

Any advice greately appreciated.

Kind regards.