Problem switching app using an ANE to captive runtime

I'm updating an app previously built with AIR 3.4 for Android with a non-captive runtime using Flash Pro CS6. This free app uses an ANE to deliver ads.

Now I'm publishing this app to AIR 3.7.0.1530 and it forces captive runtime. But now my app no longer receives ads.

Using Android's logcat to view the trace on a test mobile device, I can see that the ane is erroring out due to a missing layout resource id. After unzipping the apk's and comparing them I noted that my ad ANE uses a resource layout file named main.xml and it appears that AIR's captive runtime also uses this file, or it isn't merging it correctly. The xml files are compiled or compressed so I haven't been able to isolate the problem further.

Anyone have any ideas on fixing this?

Does anyone know if AIR provides its own main.xml layout resource file?

If I contact the supplier of the ad ane, do I ask them to change the name of the layout file they use to prevent conflicts? Or one of their resource ids?

If AIR captive runtimes have their own resources, is there some place I can get a list of those resource id's so I can avoid conflicting with them in the future?

Thanks.