Introduction

The doc.find is not a function error usually appears when Cordova tries to process an edit-config entry in config.xml and the target document or XPath does not match what the tooling expects. In practice, the failure is often caused by malformed XML, an invalid target, or a platform or plugin version mismatch around cordova-ios.

What edit-config Is Doing

Cordova uses edit-config to patch native project files during platform preparation. For iOS privacy permissions, that usually means inserting keys into Info.plist so the app can explain why it needs camera, microphone, location, or photo access.

A typical example looks like this:

1<platform name="ios">
2  <edit-config file="*-Info.plist" mode="merge" target="NSCameraUsageDescription">
3    <string>This app uses the camera to scan receipts.</string>
4  </edit-config>
5</platform>

If Cordova cannot load the target document correctly or cannot resolve the edit location, internal XML handling can fail and produce messages that are less helpful than the real cause.

Check the XML First

Start with the simplest possibility: invalid XML. A missing quote, mismatched closing tag, or duplicated platform block can cause the parser to produce an unexpected object.

Keep the entry minimal and verify:

• the platform name is ios
• the file attribute points at the correct plist target
• the target value is a valid plist key
• the child node matches the value type you want to insert

For a usage description, the value is usually a string.

Use a Valid Target

The target for iOS usage descriptions should be the plist key itself, not an arbitrary XPath copied from another example. For example, if you want microphone access:

1<platform name="ios">
2  <edit-config file="*-Info.plist" mode="merge" target="NSMicrophoneUsageDescription">
3    <string>This app records audio notes.</string>
4  </edit-config>
5</platform>

If the target does not align with the structure Cordova expects for that file, the merge step may fail before it ever writes to the plist.

Clean and Rebuild the iOS Platform

Cordova project state can become stale after plugin changes or repeated platform upgrades. Once config.xml is corrected, rebuild the generated iOS project from a clean state:

cordova platform rm ios
cordova platform add ios
cordova prepare ios

This forces Cordova to regenerate the platform files and reapply config transforms from scratch.

If you are using Ionic on top of Cordova, the equivalent platform reset still matters because the underlying iOS project is generated through Cordova tooling.

Watch for Version Mismatches

Some edit-config errors come from dependency drift rather than the XML snippet itself. If cordova-ios, Cordova CLI, or a plugin that patches plist files is too old or out of sync, internal document APIs may behave differently from what the integration expects.

Check the versions you are actually using:

cordova platform ls
cordova plugin ls

If the project has not been updated in a long time, upgrading the platform and reinstalling affected plugins is often part of the fix.

Prefer Specific, Minimal Edits

When dealing with usage descriptions, avoid broad or complicated merges. Keep each edit-config focused on one plist key. Smaller edits are easier to inspect and less likely to collide with plugin-defined changes.

For example, separate camera and photo library descriptions rather than trying to insert many unrelated values through a single block.

Common Pitfalls

• Using malformed XML in config.xml, especially after manual edits.
• Supplying an invalid target value that does not map cleanly to the iOS plist structure.
• Forgetting to remove and re-add the iOS platform after changing native configuration rules.
• Leaving old plugins or an outdated cordova-ios version in place after other tooling was upgraded.
• Mixing several unrelated plist edits into one large block, which makes failures harder to isolate.

Summary

• 'doc.find is not a function usually points to an edit-config processing problem, not an iOS permission problem by itself.'
• Validate the XML and keep the target focused on a real plist key such as NSCameraUsageDescription.
• Use simple string child values for privacy text entries in Info.plist.
• Rebuild the iOS platform after fixing config.xml so Cordova reapplies the merge cleanly.
• Check Cordova and plugin versions if the XML looks correct but the error persists.