Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Request]: network_info_plus: use ConnectivityManager for getWifiIP and getWifiGatewayIP from Android 7 (N), so ethernet works below Android 12

未关闭
  • 哪里不对？
#3,998 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@redge-munch 已经在做这个了。

开始于 2026年10月6日。

  • #3999 来自 @redge-munch —— 未关闭

评估

难度
3/5
预计耗时
半天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
android, dart, flutter, kotlin
领域
mobile, mobile-dev

调研方向

Work is already in open PR #3999; do not start a duplicate. The Android path lives in the network_info_plus plugin: NetworkInfoPlusPlugin.setupChannels() currently constructs ConnectivityManager only from VERSION_CODES.S, and NetworkInfo.getWifiIPAddress() / getGatewayIPAddress() use the same S gate (WifiInfo/dhcpInfo below that). Confirm minSdk 19 still needs the Wi-Fi fallback below N. Done means ethernet IP/gateway work on API 24–30 without crashing getDhcpServerAddress on API 24–29.

由索引模型根据 Issue 内容生成。

描述

enhancement triage
Plugin

network_info_plus

Use case

If an Android device below version 12 is on ethernet, the plugin can't find the network:

  • getWifiIP() gives back null
  • getWifiSubmask() gives back an empty string
  • getWifiBroadcast() and getWifiIPv6() don't work either
  • getWifiGatewayIP() doesn't give the ethernet gateway

On Android 12 and up it works fine. The Android code uses ConnectivityManager there, and that works for any kind of connection. But it only turns on at Build.VERSION_CODES.S. Below that, the plugin uses WifiInfo and dhcpInfo instead. Those only know about Wi-Fi, so on ethernet they just give back 0.

The thing is, the ConnectivityManager calls are much older than Android 12. getActiveNetwork() is API 23, and the rest are API 21. The only newer one is getDhcpServerAddress(), which the gateway code uses. That one is API 30.

The S check came in with #1151. #420 asks for something similar, but this is just for Android.

Proposal

Turn on the ConnectivityManager code from Android 7 (Build.VERSION_CODES.N, API 24) instead of Android 12. That takes 3 small changes.

1. Get ConnectivityManager from N in NetworkInfoPlusPlugin.setupChannels()

Right now it's only set up on S and above, so it's null on older devices. If you only change the check in NetworkInfo.kt, nothing happens.

var connectivityManager: ConnectivityManager? = null
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {
    connectivityManager = context.applicationContext.getSystemService(Context.CONNECTIVITY_SERVICE) as ConnectivityManager
}

2. Change the check in NetworkInfo.getWifiIPAddress()

Only the version number changes. The rest stays the same.

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {
    val linkAddresses =
        connectivityManager?.getLinkProperties(connectivityManager.activeNetwork)?.linkAddresses
    // ...unchanged
}

3. Get the gateway from the default route in NetworkInfo.getGatewayIPAddress()

You can't just change the version number here. getDhcpServerAddress() needs API 30, so it would crash on API 24 to 29. The default route works from API 21. It's also a bit better on Android 12+, because it gives you the real gateway and not the DHCP server. Those aren't always the same thing.

return if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {
    val linkProperties =
        connectivityManager?.getLinkProperties(connectivityManager.activeNetwork)
    val defaultRoute = linkProperties?.routes?.firstOrNull { route -> route.isDefaultRoute }

    defaultRoute?.gateway?.hostAddress
} else {
    // ...existing dhcpInfo fallback, unchanged
}

Subnet mask, broadcast and IPv6 don't need any changes. They all use the IP from getWifiIPAddress(), so they start working once that does.

The plugin's minSdk is 19, so the old Wi-Fi code still runs on anything below N.

I tried this on ethernet on API 25, 28 and 30, and it works on all of them. Before the change, none of them showed anything. It might work on API 23 (M) too, but I haven't tried that.

主要语言
Dart
星标
1.9k
派生
1.3k
平均合并
4 天 2 小时
30 天内合并 PR
15

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

fluttercommunity/plus_plugins 的其他 Issue

查看 fluttercommunity/plus_plugins 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。