I believe this is just a misunderstanding caused by the template timodule.xml not getting updated after we settled on our standard for putting the <android> section into tiapp.xml (somewhere around 1.5.0, probably). So the entries in timodule.xml should be structured the same way entries in tiapp.xml are. But the comment inside the template timodule.xml shows the manifest element looking like this: <android:manifest>, which is wrong. So perhaps the customer was following that wrong advice and thus it wasn't working.
Instead the section should look just like it would in a tiapp.xml:
If it's done that way, it already works (I didn't need to make any programming changes, though I did update timodule.xml template to reflect this.)
If QA wants to test this:
- Create a new Android module or use an existing Android module.
- Open the module's timodule.xml file and change the <android> section to look like this:
- Build the module.
- Copy the packaged module ZIP file to a Titanium Mobile project's root folder.
- In the Titanium Mobile project's tiapp.xml file, be sure to add the <module> section to specify that the module should be used in the project.
- Build the Titanium Mobile project.
- Open build/android/AndroidManifest.xml and go down near the bottom, and you should see the READ_CONTACTS permission in there – that came from the timodule.xml