Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS : Argument 4 (NSNumber) of WifiManager.connectToProtectedSSID is marked as nullable #396

Closed
anuragipankaj opened this issue Aug 9, 2024 · 4 comments · Fixed by #397
Labels

Comments

@anuragipankaj
Copy link

i'm facing this iOS issue in the latest version of react native wifi reborn package while calling the function :

WifiManager.connectToProtectedSSID

this is how I'm using it:

WifiManager.connectToProtectedSSID(ssid, API.pIDevicePassword, false)

I think this is an issue in Pod file content where it is asking a parameter to be marked as nullable. Please suggest and provide guidance on how to fix it.

Argument 4 (NSNumber) of WifiManager.connectToProtectedSSID is marked as nullable but React requires that all NSNumber arguments are explicitly marked as nonnull to ensure compatibility with Android.

RCTLogArgumentError(RCTModuleMethod*, unsigned long, objc_object*, char const*)
RCTModuleMethod.mm:67
-[RCTModuleMethod processMethodSignature]
-[RCTModuleMethod invokeWithBridge:module:arguments:]
facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&, int, (anonymous namespace)::SchedulingContext)
facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int)::$_0::operator()() const
invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int)
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_lane_serial_drain
_dispatch_lane_invoke
_dispatch_root_queue_drain_deferred_wlh
_dispatch_workloop_worker_thread
_pthread_wqthread
start_wqthread

@DavideViolante
Copy link
Collaborator

DavideViolante commented Aug 9, 2024

I think duplicate of #379 and so I think this is a verified issue since v4.12.0, maybe since this change b5bdb35

edit: cc @alexma01

@nrsleonardo
Copy link

same here.
using v4.11.0 with no issues.

@DavideViolante
Copy link
Collaborator

DavideViolante commented Aug 28, 2024

Can someone on this thread test the PR? #397

@JuanSeBestia
Copy link
Owner

🎉 This issue has been resolved in version 4.13.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants