React native download file over wifi

is a library to provide WiFi Direct (Peer-To-Peer, P2P) service to react-native.

Important: currently only Android support realized. If you want to provide iOS support, then you should to note to react-native-multipeer repository.

This library will not work on emulator. If you want to use this library, you should test working it on real devices.

Test project with all API cases you can find here.

React Native Compatibility

To use this library you need to ensure you match up with the correct version of React Native you are using.

p.s. React Native introduced AndroidX support in 0.60, which is a breaking change for most libraries (incl. this one) using native Android functionality.

Installation

Install library from

Allow grant permission to WiFi module

Link library

Note: You should skip it if you use react-native >0.60

• Append the following lines to

• Insert the following lines inside the dependencies block in :

• Open up

  • Add import to the imports at the top of the file.
  • Add to the list returned by the method. Add a comma to the previous item if there's already something there.

API

Initialization

Subscribers & Actions annunciators

Interaction with other devices

CONSTANTS

API

Initialization

initialize()

This method must calling before any using of others method, because here happened start initialization of module. Recommend to initialize it on root files, but if your application has specific logic, then you can call it before directly using. Notice, that recommend called only once.

startDiscoveringPeers()

starting emit action to discover available devices. Note, that this function doesn't return any information about available devices/peers. It return information about successfully start.

stopDiscoveringPeers()

prevent emit action to discover available devices. Note, that this function doesn't return any information about available devices/peers. It return information about successfully stopping of discovering.

Subscribers & Actions annunciators

subscribeOnPeersUpdates(callback)

allow to subscribe on events, that will notify about availability of nearby devices.

unsubscribeFromPeersUpdates(callback)

subscribeOnConnectionInfoUpdates(callback)

unsubscribeFromConnectionInfoUpdates(callback)

subscribeOnThisDeviceChanged(callback)

unsubscribeFromThisDeviceChanged(callback)

Interaction with other devices

getAvailablePeers()

If you don't want to always get notification from event emitter, when peers list has changed, you can use this method. This method will return info about nearby devices, that is available for searching, at the time of the call this method.

Important: before using this method you also need to call . In other case you always will get empty array.

connect(deviceAddress)

Connect to network. The devices found from the method. Should use field from necessary device from array. This field represent a that is used to connect.

connectWithConfig(connectionArgs)

Connect to network. The method takes two arguments and an optional . specifies to the OS the intentsity with which the device initiaiting the connection wants to be the group Owner.(i.e the server). It takes a value between and , 0 and 15 being the least and most likely group owners respectively. i.e device specifying is more likely to be a group owner. Link to andrdoid documentation [https://developer.android.com/reference/android/net/wifi/p2p/WifiP2pConfig]

cancelConnect()

Cancel connection from network. Should use when you want to reconnect or turn off wifi.

If you want to disconnect, then you can use the following chain of functions:

createGroup()

P2P STAR is a peer-to-peer strategy that supports a 1-to-N, or star-shaped, connection topology. In other words, this enables connecting devices within radio range (~100m) in a star shape, where each device can, at any given time, play the role of either a hub (where it can accept incoming connections from N other devices), or a spoke (where it can initiate an outgoing connection to a single hub), but not both. So achieve this goal you can use method, so create your own group.

removeGroup()

Before exit of application you need to call this method, if earlier you created group via method.

getGroupInfo()

You can call it after method is executed. Info from this method also is available in . This method was created basically for supporting API <= 17. See issue thread.

getConnectionInfo()

This method in the main is used in flow. It's needed for saving internally of this library. Also this method returns actual connection information. Fot its usage see description of method.

sendFile(pathToFile)

You should call this method if you want to copy file from client side to server using wi-fi p2p feature. Before sending you should execute next steps:

1. Create group on server side
2. Connect to server-group from client side
3. After establishing connection you should call on client side
4. Call on server side ( return - path to saved file)
5. Call on client side, after resolving

sendMessage(message)

You should call this method if you want to send from client side to server (group) using wi-fi p2p feature. Before sending you should execute next steps:

1. Create group on server side (side, which will receive message)
2. Connect to server-group from client side
3. After establishing connection you should call on client side (also recommend do it on group-server side)
4. Call on server side ( return - message from client)
5. Call on client side, after resolving

Note: you cannot send character encoding for string and by default this library uses .

receiveFile(folder, fileName, forceToScanGallery)

If you expect, that someone may send you a file - you can call this method in order to receive it.

If you want to save file with the same name as it's on client device, then before sending file you can about its .

is an optional parameter, which indicate whether should we scan and detect new files or not in order to show them in Gallery app. By default it's .

Note: if you expect file to be received you should request permissions for writing to the storage:

receiveMessage()

If you expect, that someone may send you a message - you can call this method in order to receive it:

CONSTANTS

WifiP2pDevice statuses

Events of library

Caveats

On Android >= 6.0 you should ask permissions before usage of this library (since this grants are required):

Note: you should ask this grants before

Note: on Android 10 you will probably need to ask instead of .

If you are using Android Oreo (8.0) or higher, then you also need to request permission, and location should be enabled.

Example of usage

Current Tags

• 3.2.1                                ...           latest (2 months ago)

28 Versions

• 3.2.1                                ...           2 months ago
• 3.2.0                                ...           2 months ago
• 3.1.0                                ...           5 months ago
• 3.0.0                                ...           5 months ago
• 2.0.2                                ...           7 months ago
• 2.0.1                                ...           7 months ago
• 2.0.0                                ...           7 months ago
• 1.0.2                                ...           9 months ago
• 1.0.1                                ...           a year ago
• 1.0.0                                ...           a year ago
• 0.6.7                                ...           a year ago
• 0.6.6                                ...           a year ago
• 0.6.5                                ...           2 years ago
• 0.6.4                                ...           2 years ago
• 0.6.3                                ...           2 years ago
• 0.6.2                                ...           2 years ago
• 0.6.1                                ...           2 years ago
• 0.6.0                                ...           2 years ago
• 0.5.0                                ...           2 years ago
• 0.4.9                                ...           2 years ago
• 0.4.8                                ...           2 years ago
• 0.4.4                                ...           2 years ago
• 0.4.3                                ...           2 years ago
• 0.4.1                                ...           2 years ago
• 0.3.6                                ...           2 years ago
• 0.3.5                                ...           2 years ago
• 0.3.3                                ...           2 years ago
• 0.3.2                                ...           2 years ago