Native Android Extension - Service Not Found

Question

Greetings,
I have created an AIR native extension which I am using in an AIR for Android app.  My native extension needs to use an Android Service from a 3rd party library.  However, seemingly no matter what I do to hook up this Android Service in the native code, the app reports "Unable to start....service not found" at runtime.
Now I have used this service in normal, native Android apps and it works fine - I have tried duplicating the same startup process from my previous apps, that process still results in a "service not found" error in this AIR for Android app. 
Does anyone know whats going on here, or had similar issues?
My only thought at this point is that the intense mangling that happens when AIR compiles an APK might be screwing up the path to the Service, therefore the class loader on the Android device is unable to find the service at runtime.  However, I do not know how to prove this hypothesis.
I have gone as far as to write my own Service class which wraps around the 3rd party service, so that the service I'm requesting is in the same java package as all the other native extension code I'm writing, but that option didn't work either.
Any help would be appreciated.
Thanks.
Matt
PS - In case you're wondering, I did make sure to declare the <service> tag in my extension's manifest file.

Answer 1

Hey Chris!
I figured out *JUST NOW* what the issue is (and this is certainly NOT documented in any PDF, or whitepaper on Native Extensions).
The problem lies with both the Signing Certificate and the package name for your AIR Application.
Rules for Adobe AIR Native Extensions
Rule 1 (Documented)
The Code Signing Certificate package must match the application id in your app.xml
so if the certificate package is `com.my.company`, then the air app id must be `<id>com.my.company</id>`
Rule 2. (Partially Documented)
When packaging a native extension for android using ADT, a prefix is added to your package name so it looks like `air.com.my.company`.
(Not Documented)
When the Android ActivityManager tries to run your service it looks for it in `air.com.my.company`. Thus, the Service class must live in the same package (including the 'air' prefix) within your java code. My TestService class now is defined as `air.com.my.company.TestService`
And with the following manifest, it runs just fine!
<application>
          <activity android:name=".TestActivity">
                    <intent-filter>
                             <action android:name="TestActivity"/>
                              <category android:name="android.intent.category.DEFAULT"/>
                    </intent-filter>
          </activity>
          <service android:enabled="true" android:exported="true" android:name=".TestService">
               <intent-filter>
                                       <action android:name="test.default.service"/>
               </intent-filter>
          </service>
</application>
Start the service using the following code
startService(new Intent("test.default.service"));
Thanks again!
Bow