[Bug]: requestConsentInfo fails when options are undefined

[becvert]

Framework

Cordova CLI

Plugin Version

2.0.0

Android & Java Version

iOS 8.1.1

Current Behavior

When I call admobNextGen.requestConsentInfo(undefined, success, failure), failure is called.
I expect a success callback instead even with undefined options

Steps to Reproduce

1. latest plugin and cordova iOS 8.1.1
2. call admobNextGen.requestConsentInfo(undefined)
3. error is caught and the failure callback is called

Error Log / Stack Trace

[NSNull options] unrecognized selector send to instance

https://github.com/swaplab-engine/cordova-plugin-admob-nextgen/blob/87e48400eacbae2082bde5d23a6fff41d1153b94/src/ios/ConsentExecutor.m#L24

Config File (Optional)

Code of Conduct

• I have searched the existing issues and this is not a duplicate.
• I have provided the error logs and environment details.

[EMI-INDO]

Hi @becvert,

Thank you for reporting this.

Why the crash happens:

When you pass undefined from JavaScript, the Cordova bridge translates it into an NSNull object on the native iOS side. The Objective-C code expects an NSDictionary and attempts to access its keys (e.g., options[@"debug"]). Since NSNull is not a dictionary, it triggers the unrecognized selector sent to instance exception, which causes the native app to crash.

Correct Usage:

As explicitly documented in the README.md, the requestConsentInfo method strictly requires an options object as its first parameter. It is not designed to accept undefined.

// Correct usage based on the documentation
admobNextGen.requestConsentInfo({
    debug: false,
    reset: false,
    tagForUnderAgeOfConsent: false
}, successCallback, errorCallback);

If you do not want to provide any specific configuration, you must pass an empty object at the very least, not undefined:

admobNextGen.requestConsentInfo({}, successCallback, errorCallback);

To keep the native codebase simple and clean, I expect developers to follow the API contract provided in the documentation. However, to prevent hard crashes caused by incorrect usage in the future, I will add a validation check on the JavaScript layer (www/admobNextGen.js). This will reject invalid arguments and trigger the error callback before the data even reaches the native iOS bridge.

• Please update your implementation to pass a valid object as shown in the README.md.

[becvert]

Yes indeed that's the culprit.
However on the Android side you do check for null:

cordova-plugin-admob-nextgen/src/android/ConsentExecutor.java

Line 52 in 9e4cca1

if (options != null) {

But it's up to you. I appreciate a lot you're giving time and efforts.
And it will be good enough for me now to jump into production.