Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

React Native Network Info API for Android & iOS

License

NotificationsYou must be signed in to change notification settings

react-native-netinfo/react-native-netinfo

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ActionsSupports Android, iOS, macOS, Windows and WebMIT LicenseLean Core Extracted

React Native Network Info API for Android, iOS, macOS, Windows & Web. It allows you to get information on:

  • Connection type
  • Connection quality

Getting started

Install the library using either Yarn:

yarn add @react-native-community/netinfo

or npm:

npm install --save @react-native-community/netinfo

Using React Native >= 0.60

Linking the package manually is not required anymore withAutolinking.

  • iOS Platform:

    $ npx pod-install # CocoaPods on iOS needs this extra step

  • Android Platform with AndroidX:

    Modify yourandroid/build.gradle configuration:

    buildscript {  ext {    buildToolsVersion = "xx.yy.zz"    minSdkVersion = xyz    compileSdkVersion = xyz    targetSdkVersion = xyz  }
  • macOS Platform:

    Autolinking is not yet available on macOS. See theManual linking steps for macOS below.

Manually link the library on macOS
  1. Open your project.xcodeproj on xcode.

  2. Right click on the Libraries folder and selectAdd files to "yourProjectName".

  3. AddRNCNetInfo.xcodeproj (located atnode_modules/@react-native-community/react-native-netinfo/macos) to your project Libraries.

  4. Go toBuild Phases -> Link Binary with Libraries and add:libRNCNetInfo-macOS.a.

  • Windows Platform:

    Autolinking automatically works on RNW >= 0.63.

Minimum supported versions for windows

  • react-native-windows 0.63 or newer
  • MSVC build tools v142 (included in Visual Studio 2019) or newer
  • x86, x64, or arm64 are supported, arm (32-bit) is not supported

React Native Compatibility

To use this library you need to ensure you are using the correct version of React Native.We support react-native 0.60+ with auto-linking.

If you are using a version of React Native that is lower than 0.60 check older versions of this README for details,but no support will be provided.

Browser Compatilibity

The web implementation heavily depends on theNetwork Information API which is still an is an experimental technology and thus it's not supported in every browser.If this API is not available the library will safely fallback to the oldonLine property and return basic connection information.

AbortController is used to cancel network requests, and may not be available on Internet Explorer, though it is available on Edgehttps://caniuse.com/abortcontroller

Node Compatibility

Node v16 is the minimum required node version -AbortController is only present in stable versions of node from v16 on

Migrating from the corereact-native module

This module was created when the NetInfo was split out from the core of React Native. To migrate to this module you need to follow the installation instructions above and then change your imports from:

import{NetInfo}from"react-native";

to:

importNetInfofrom"@react-native-community/netinfo";

Note that the API was updated after it was extracted from NetInfo to support some new features, however, the previous API is still available and works with no updates to your code.

Usage

Global vs isolated instance

Internally this library has a network state manager class to handle all the functionality and state. This library provides two options for instantiating the class:

  1. you can use global library functions which taps into a global singleton instance of the class
  2. or you can create isolated instances of the class to tap into, each being separately configured

Global instance functions:

Subscribe to network state updates:

import{addEventListener}from"@react-native-community/netinfo";// Subscribeconstunsubscribe=addEventListener(state=>{console.log("Connection type",state.type);console.log("Is connected?",state.isConnected);});// Unsubscribeunsubscribe();

Get the network state once:

import{fetch}from"@react-native-community/netinfo";fetch().then(state=>{console.log("Connection type",state.type);console.log("Is connected?",state.isConnected);});

Get network state updates from the global instance via a react hook:

import{useNetInfo}from"@react-native-community/netinfo";const{ type, isConnected}=useNetInfo();

Isolated instance:

Use an isolated instance of the network manager:

import{useNetInfoInstance}from"@react-native-community/netinfo";const{netInfo:{ type, isConnected}, refresh}=useNetInfoInstance();

API

Types

NetInfoState

Describes the current state of the network. It is an object with these properties:

PropertyTypeDescription
typeNetInfoStateTypeThe type of the current connection.
isConnectedboolean,nullIf there is an active network connection. Defaults tonull on most platforms forunknown networks. Note: Web browsers report network typeunknown for many otherwise valid networks (https://caniuse.com/netinfo), soisConnected may betrue orfalse and represent a real connection status even for unknown network types in certain cases.
isInternetReachableboolean,nullIf the internet is reachable with the currently active network connection. If unknown defaults tonull
isWifiEnabledboolean(Android only) Whether the device's WiFi is ON or OFF.
detailsThe value depends on thetype value. See below.

Thedetails value depends on thetype value.

type isnone orunknown

details isnull.

type iswifi

details has these properties:

PropertyPlatformTypeDescription
isConnectionExpensiveAndroid, iOS, macOS, Windows, WebbooleanIf the network connection is considered "expensive". This could be in either energy or monetary terms.
ssidAndroid, iOS (not tvOS), WindowsstringThe SSID of the network. May not be present,null, or an empty string if it cannot be determined.On iOS, your app must meet at least one of thefollowing requirements and you must set theshouldFetchWiFiSSID configuration option or no attempt will be made to fetch the SSID. On Android, you need to have theACCESS_FINE_LOCATION permission in yourAndroidManifest.xml and accepted by the user.
bssidAndroid, iOS (not tvOS), Windows*stringThe BSSID of the network. May not be present,null, or an empty string if it cannot be determined.On iOS, make sure your app meets at least one of thefollowing requirements. On Android, you need to have theACCESS_FINE_LOCATION permission in yourAndroidManifest.xml and accepted by the user.
strengthAndroid, WindowsnumberAn integer number from0 to100 for the signal strength. May not be present if the signal strength cannot be determined.
ipAddressAndroid, iOS, macOS, WindowsstringThe external IP address. Can be in IPv4 or IPv6 format. May not be present if it cannot be determined.
subnetAndroid, iOS, macOSstringThe subnet mask in IPv4 format. May not be present if it cannot be determined.
frequencyAndroid, Windows*numberNetwork frequency. Example: For 2.4 GHz networks, the method will return 2457. May not be present if it cannot be determined.
linkSpeedAndroidnumberThe link speed in Mbps.
rxLinkSpeedAndroidnumberThe current receive link speed in Mbps. (Android Q / API level 29 and above)
txLinkSpeedAndroidnumberThe current transmit link speed in Mbps. (Android Q / API level 29 and above)

* RequireswiFiControl capability in appxmanifest. Without it, these values will be null.

type iscellular

details has these properties:

PropertyPlatformTypeDescription
isConnectionExpensiveAndroid, iOS, macOS, Windows, WebbooleanIf the network connection is considered "expensive". This could be in either energy or monetary terms.
cellularGenerationAndroid, iOS, WindowsNetInfoCellularGenerationThe generation of the cell network the user is connected to. This can give an indication of speed, but no guarantees.
carrierAndroid, iOSstringThe network carrier name. May not be present or may be empty if none can be determined.
type isbluetooth,ethernet,wimax,vpn, orother

details has these properties:

PropertyTypeDescription
isConnectionExpensivebooleanIf the network connection is considered "expensive". This could be in either energy or monetary terms.

NetInfoStateType

Describes the current type of network connection. It is an enum with these possible values:

ValuePlatformDescription
noneAndroid, iOS, macOS, Windows, WebNo network connection is active
unknownAndroid, iOS, macOS, Windows, WebThe network state could not or has yet to be be determined
cellularAndroid, iOS, Windows, WebActive network over cellular
wifiAndroid, iOS, macOS, Windows, WebActive network over Wifi
bluetoothAndroid, WebActive network over Bluetooth
ethernetAndroid, macOS, Windows, WebActive network over wired ethernet
wimaxAndroid, WebActive network over WiMax
vpnAndroidActive network over VPN
otherAndroid, iOS, macOS, Windows, WebActive network over another type of network

NetInfoCellularGeneration

Describes the current generation of thecellular connection. It is an enum with these possible values:

ValueDescription
nullEither we are not currently connected to a cellular network or type could not be determined
2gCurrently connected to a 2G cellular network. Includes CDMA, EDGE, GPRS, and IDEN type connections
3gCurrently connected to a 3G cellular network. Includes EHRPD, EVDO, HSPA, HSUPA, HSDPA, and UTMS type connections
4gCurrently connected to a 4G cellular network. Includes HSPAP and LTE type connections
5gCurrently connected to a 5G cellular network. Includes NRNSA (iOS only) and NR type connections

NetInfoConfiguration

The configuration options for the library.

PropertyTypeDefaultDescription
reachabilityUrlstringhttps://clients3.google.com/generate_204The URL to call to test if the internet is reachable. Only used on platforms which do not supply internet reachability natively or ifuseNativeReachability isfalse.
reachabilityHeadersobject{}A HTTP headers object, an object literal, or an array of two-item arrays to set request's headers, to use during the reachabilityUrl URL call to test if the internet is reachable. Defaults to{}.
reachabilityMethodNetInfoMethodTypeHEADThe HTTP request method to use to call reachabilityUrl URL to call to test if the internet is reachable. Defaults toHEAD.GET is also available
reachabilityTest(response: Response) => booleanPromise.resolve(response.status === 204)A function which is passed theResponse from calling the reachability URL. It should returntrue if the response indicates that the internet is reachable. Only used on platforms which do not supply internet reachability natively or ifuseNativeReachability isfalse.
reachabilityShortTimeoutnumber5 secondsThe number of milliseconds between internet reachability checks when the internet was not previously detected. Only used on platforms which do not supply internet reachability natively or ifuseNativeReachability isfalse.
reachabilityLongTimeoutnumber60 secondsThe number of milliseconds between internet reachability checks when the internet was previously detected. Only used on platforms which do not supply internet reachability natively or ifuseNativeReachability isfalse.
reachabilityRequestTimeoutnumber15 secondsThe number of milliseconds that a reachability check is allowed to take before failing. Only used on platforms which do not supply internet reachability natively or ifuseNativeReachability isfalse.
reachabilityShouldRun() => boolean() => trueA function which returns a boolean to determine if checkInternetReachability should be run.
shouldFetchWiFiSSIDbooleanfalseA flag indicating one of the requirements on iOS has been met to retrieve the network (B)SSID, and the native SSID retrieval APIs should be called. This has no effect on Android.
useNativeReachabilitybooleantrueA flag indicating whether or not Netinfo should use native reachability checks, if available.

Global instance methods

Please note the difference between global and isolated usage describedhere

configure()

Configures the library with the given configuration. You only need to supply the properties which you want to change from the default values.

Note that calling this will stop all previously added listeners from being called again. It is best to call this right when your application is started to avoid issues.

Example:

NetInfo.configure({reachabilityUrl:'https://clients3.google.com/generate_204',reachabilityTest:async(response)=>response.status===204,reachabilityLongTimeout:60*1000,// 60sreachabilityShortTimeout:5*1000,// 5sreachabilityRequestTimeout:15*1000,// 15sreachabilityShouldRun:()=>true,shouldFetchWiFiSSID:true,// met iOS requirements to get SSID. Will leak memory if set to true without meeting requirements.useNativeReachability:false});

addEventListener()

Subscribe to connection information. The callback is called with a parameter of typeNetInfoState whenever the connection state changes. Your listener will be called with the latest information soon after you subscribe and then with any subsequent changes afterwards. You should not assume that the listener is called in the same way across devices or platforms.

ParameterTypeDescription
listener(state:NetInfoState) => voidThe listener which will be called whenever the connection state changes

Example:

// Subscribeconstunsubscribe=NetInfo.addEventListener(state=>{console.log("Connection type",state.type);console.log("Is connected?",state.isConnected);});// Unsubscribeunsubscribe();

useNetInfo()

AReact Hook which can be used to get access to the latest state from the global instance. It returns a hook with theNetInfoState type.

Example:

import{useNetInfo}from"@react-native-community/netinfo";constYourComponent=()=>{constnetInfo=useNetInfo();return(<View><Text>Type:{netInfo.type}</Text><Text>Is Connected?{netInfo.isConnected?.toString()}</Text></View>);};

You can optionally send configuration when setting up the hook. Note that configuration is global for the library, so you shouldn't send different configuration for different hooks. It is instead recommended that you calledNetInfo.configure() once when your project starts. The hook option is only provided as a convinience.

constYourComponent=()=>{constnetInfo=useNetInfo({reachabilityUrl:'https://clients3.google.com/generate_204',reachabilityTest:async(response)=>response.status===204,reachabilityLongTimeout:60*1000,// 60sreachabilityShortTimeout:5*1000,// 5sreachabilityRequestTimeout:15*1000,// 15sreachabilityShouldRun:()=>true,shouldFetchWiFiSSID:true,// met iOS requirements to get SSIDuseNativeReachability:false});// ...};

fetch()

Returns aPromise that resolves to aNetInfoState object.

Example:

NetInfo.fetch().then(state=>{console.log("Connection type",state.type);console.log("Is connected?",state.isConnected);});

You can optionally send aninterface string so thePromise resolves to aNetInfoState from theNetInfoStateType indicated ininterface argument.

NetInfo.fetch("wifi").then(state=>{console.log("SSID",state.details.ssid);console.log("BSSID",state.details.bssid);console.log("Is connected?",state.isConnected);});

refresh()

Updates NetInfo's internal state, then returns aPromise that resolves to aNetInfoState object. This is similar tofetch(), but really only useful on platforms that do not supply internet reachability natively. For example, you can use it to immediately re-run an internet reachability test if a network request fails unexpectedly.

Example:

NetInfo.refresh().then(state=>{console.log("Connection type",state.type);console.log("Is connected?",state.isConnected);});

This will also update subscribers usingaddEventListener and/oruseNetInfo.

Isolated instance

Please note the difference between global and isolated usage describedhere

useNetInfoInstance()

AReact Hook which can be used to create and manage an isolated instance of a network manager class. It returns arefresh function and the currentNetInfoState.

Example:

import{useNetInfoInstance}from"@react-native-community/netinfo";constYourComponent=()=>{const{netInfo, refresh}=useNetInfoInstance();return(<View><Text>Type:{netInfo.type}</Text><Text>Is Connected?{netInfo.isConnected?.toString()}</Text></View>);};

isPaused: You can also pause the hooks internal network checks by passing a boolean valuetrue as the first argument.

configuration: You can optionally send configuration as the second argument when setting up the hook. Note that configuration is local to the instance managed by this hook and has no relation to the configuration passed to other functionsconfigure() oruseNetInfo();

import{useNetInfoInstance}from"@react-native-community/netinfo";constYourComponent=()=>{constisPaused=false;constconfig={reachabilityUrl:'https://clients3.google.com/generate_204',reachabilityTest:async(response)=>response.status===204,reachabilityLongTimeout:60*1000,// 60sreachabilityShortTimeout:5*1000,// 5sreachabilityRequestTimeout:15*1000,// 15sreachabilityShouldRun:()=>true,shouldFetchWiFiSSID:true,// met iOS requirements to get SSIDuseNativeReachability:false}const{ netInfo}=useNetInfoInstance(isPaused,config);//...

Troubleshooting

Errors when building on Android

Errors while running Jest tests

If you do not have a Jest Setup file configured, you should add the following to your Jest settings and create thejest.setup.js file in project root:

setupFiles:['<rootDir>/jest.setup.js']

You should then add the following to your Jest setup file to mock the NetInfo Native Module:

importmockRNCNetInfofrom'@react-native-community/netinfo/jest/netinfo-mock.js';jest.mock('@react-native-community/netinfo',()=>mockRNCNetInfo);

Issues with the iOS simulator

There is aknownissue with the iOS Simulator which causes it to not receive network change notifications correctly when the host machine disconnects and then connects to Wifi. If you are having issues with iOS then please test on an actual device before reporting any bugs.

Switching between different Wi-Fi does not send events in iOS

The SCNetworkReachability API used in iOS does not send events to the app in the background, so switching from one Wi-Fi network to another when your App was in background will not send an event and your network state will be out of sync with device state. To be sure you have up to date status when your app is in foreground again, you should re-fetch state each time when App comes to foreground, something like this:

useEffect(()=>{constsubAppState=AppState.addEventListener("change",async(nextAppState)=>{if(IS_IOS_DEVICE&&nextAppState=='active'){letnewNetInfo=awaitNativeModules.RNCNetInfo.getCurrentState('wifi');//your code here}});constunsubNetState=NetInfo.addEventListener(state=>{//your code here});return()=>{if(subAppState){subAppState.remove();}unsubNetState();};},[]);

Maintainers

Maintainers Emeritus

Contributing

Please see thecontributing guide.

License

The library is released under the MIT license. For more information seeLICENSE.


[8]ページ先頭

©2009-2025 Movatter.jp