When a plugin fails, it is tempting to change everything at once. Resist that urge. Cordova gives you several layers to inspect, and the fastest path is to isolate which layer is actually broken.
Start in JavaScript
Confirm the plugin object exists after deviceready. If your code runs before Cordova finishes booting, the native side may be fine while the app still reports undefined APIs.
Then inspect native setup
Check that the plugin is installed for the platform you are running, not only listed in package metadata. If needed, remove and re-add the platform after committing your app source.
- Read the device log, not only browser console output.
- Check permissions before calling the native feature.
- Test the smallest possible plugin call.
- Compare emulator behavior with a physical device.
Debugging rhythm:
Make one change, rebuild, test one behavior, write down the result. That rhythm beats three hours of hopeful toggling.