代码拉取完成，页面将自动刷新
| title | description |
|---|---|
Network Information |
Get information about wireless connectivity. |
This plugin provides an implementation of an old version of the Network Information API. It provides information about the device's cellular and wifi connection, and whether the device has an internet connection.
To get a few ideas how to use the plugin, check out the sample at the bottom of this page or go straight to the reference content.
Report issues with this plugin on the Apache Cordova issue tracker.
cordova plugin add cordova-plugin-network-information
The
connectionobject, exposed vianavigator.connection, provides information about the device's cellular and wifi connection.
This property offers a fast way to determine the device's network connection state, and type of connection.
function checkConnection() {
var networkState = navigator.connection.type;
var states = {};
states[Connection.UNKNOWN] = 'Unknown connection';
states[Connection.ETHERNET] = 'Ethernet connection';
states[Connection.WIFI] = 'WiFi connection';
states[Connection.CELL_2G] = 'Cell 2G connection';
states[Connection.CELL_3G] = 'Cell 3G connection';
states[Connection.CELL_4G] = 'Cell 4G connection';
states[Connection.CELL] = 'Cell generic connection';
states[Connection.NONE] = 'No network connection';
alert('Connection type: ' + states[networkState]);
}
checkConnection();
Until Cordova 2.3.0, the Connection object was accessed via
navigator.network.connection, after which it was changed to
navigator.connection to match the W3C specification. It's still
available at its original location, but is deprecated and will
eventually be removed.
navigator.connection.type is set to Connection.CELL for all cellular data.When running in the emulator, always detects navigator.connection.type as Connection.UNKNOWN.
Windows Phone can't detect the type of cellular network connection.
navigator.connection.type is set to Connection.CELL for all cellular data.navigator.connection.type as Connection.ETHERNET.navigator.connection.type is set to Connection.CELL_2G for all cellular data.navigator.connection.type is set to Connection.CELL for all cellular data.navigator.connection.type is always set to Connection.UNKNOWN when online.The event fires when an application goes offline, and the device is not connected to the Internet.
document.addEventListener("offline", yourCallbackFunction, false);
The offline event fires when a previously connected device loses a
network connection so that an application can no longer access the
Internet. It relies on the same information as the Connection API,
and fires when the value of connection.type becomes NONE.
Applications typically should use document.addEventListener to
attach an event listener once the deviceready event fires.
document.addEventListener("offline", onOffline, false);
function onOffline() {
// Handle the offline event
}
During initial startup, the first offline event (if applicable) takes at least a second to fire.
When running in the Emulator, the connection.status is always unknown, so this event does not fire.
The Emulator reports the connection type as Cellular, which does not change, so the event does not fire.
This event fires when an application goes online, and the device becomes connected to the Internet.
document.addEventListener("online", yourCallbackFunction, false);
The online event fires when a previously unconnected device receives
a network connection to allow an application access to the Internet.
It relies on the same information as the Connection API,
and fires when the connection.type changes from NONE to any other
value.
Applications typically should use document.addEventListener to
attach an event listener once the deviceready event fires.
document.addEventListener("online", onOnline, false);
function onOnline() {
// Handle the online event
}
During initial startup, the first online event (if applicable) takes
at least a second to fire, prior to which connection.type is
UNKNOWN.
When running in the Emulator, the connection.status is always unknown, so this event does not fire.
The Emulator reports the connection type as Cellular, which does not change, so events does not fire.
The code examples in this section show examples of changing app behavior using the online and offline events and your network connection status.
To start with, create a new FileEntry object (data.txt) to use for sample data. Call this function from the deviceready handler.
Note This code example requires the File plugin.
var dataFileEntry;
function createSomeData() {
window.requestFileSystem(window.TEMPORARY, 5 * 1024 * 1024, function (fs) {
console.log('file system open: ' + fs.name);
// Creates a new file or returns an existing file.
fs.root.getFile("data.txt", { create: true, exclusive: false }, function (fileEntry) {
dataFileEntry = fileEntry;
}, onErrorCreateFile);
}, onErrorLoadFs);
}
Next, add listeners for the online and offline events in the deviceready handler.
document.addEventListener("offline", onOffline, false);
document.addEventListener("online", onOnline, false);
The app's onOnline function handles the online event. In the event handler, check the current network state. In this app, treat any connection type as good except Connection.NONE. If you have a connection, you try to upload a file.
function onOnline() {
// Handle the online event
var networkState = navigator.connection.type;
if (networkState !== Connection.NONE) {
if (dataFileEntry) {
tryToUploadFile();
}
}
display('Connection type: ' + networkState);
}
When the online event fires in the preceding code, call the app's tryToUploadFile function.
If the FileTransfer object's upload function fails, call the app's offlineWrite function to save the current data somewhere.
Note This example requires the FileTransfer plugin.
function tryToUploadFile() {
// !! Assumes variable fileURL contains a valid URL to a text file on the device,
var fileURL = getDataFileEntry().toURL();
var success = function (r) {
console.log("Response = " + r.response);
display("Uploaded. Response: " + r.response);
}
var fail = function (error) {
console.log("An error has occurred: Code = " + error.code);
offlineWrite("Failed to upload: some offline data");
}
var options = new FileUploadOptions();
options.fileKey = "file";
options.fileName = fileURL.substr(fileURL.lastIndexOf('/') + 1);
options.mimeType = "text/plain";
var ft = new FileTransfer();
// Make sure you add the domain of your server URL to the
// Content-Security-Policy <meta> element in index.html.
ft.upload(fileURL, encodeURI(SERVER), success, fail, options);
};
Here is the code for the offlineWrite function.
Note This code examples requires the File plugin.
function offlineWrite(offlineData) {
// Create a FileWriter object for our FileEntry.
dataFileEntry.createWriter(function (fileWriter) {
fileWriter.onwriteend = function () {
console.log("Successful file write...");
display(offlineData);
};
fileWriter.onerror = function (e) {
console.log("Failed file write: " + e.toString());
};
fileWriter.write(offlineData);
});
}
If the offline event occurs, just do something like notify the user (for this example, just log it).
function onOffline() {
// Handle the offline event
console.log("lost connection");
}
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
1. 开源生态
2. 协作、人、软件
3. 评估模型