crash when scanning on ethernet

[MrSn0wy]

Describe the bug
App crashes when scanning with an Ethernet connection. Looks like just a small nullpointer exception for bssid, since no wifi.

To Reproduce
Steps to reproduce the behavior:

1. Connect Ethernet to phone.
2. Scan in app

Device

• Device: xiaomi redmit note 12 pro+
• OS: android 14
• Ning Version 3.0.3
• rooted? yes

LogCat Logs
AndroidRuntime: FATAL EXCEPTION: main
AndroidRuntime: Process: de.csicar.ning, PID: 11587
AndroidRuntime: java.lang.NullPointerException: getBSSID(...) must not be null
AndroidRuntime: at de.csicar.ning.ScanRepository$startScan$2.invokeSuspend(ScanRepository.kt:36)
AndroidRuntime: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
AndroidRuntime: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
AndroidRuntime: at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:124)
AndroidRuntime: at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
AndroidRuntime: at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
AndroidRuntime: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
AndroidRuntime: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
AndroidRuntime: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)
AndroidRuntime: Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@f8ea997, Dispatchers.Main]

[hiSandog]

For scanning on Ethernet, the important missing details are whether discovery assumes WiFi-specific APIs and whether the device has multiple active network interfaces. A useful log would include interface names, IP/subnet, route used for discovery, and the crash stack. The fix should probably enumerate eligible IPv4/IPv6 interfaces generically rather than assuming the active transport is WLAN.

[csicar]

Thanks for sharing this. Should be a relatively simple fix.
Though I cannot promise when I'll find the time to fiz this