opentok-react-native
Advanced tools
Comparing version 0.3.4 to 0.3.5
{ | ||
"name": "opentok-react-native", | ||
"version": "0.3.4", | ||
"version": "0.3.5", | ||
"description": "React Native components for OpenTok iOS and Android SDKs", | ||
@@ -8,4 +8,3 @@ "main": "src/index.js", | ||
"scripts": { | ||
"test": "echo \"Error: no test specified\" && exit 1", | ||
"postinstall": "node ./scripts/postInstall" | ||
"test": "echo \"Error: no test specified\" && exit 1" | ||
}, | ||
@@ -12,0 +11,0 @@ "keywords": [ |
@@ -57,7 +57,7 @@ ![OpenTok Labs](https://d26dzxoao6i3hh.cloudfront.net/items/0U1R0a0e2g1E361H0x3c/Image%202017-11-22%20at%2012.16.38%20PM.png?v=2507a2df) | ||
6. Open <YourProjectName>.xcworkspace file in XCode. This file can be found in the `ios` folder. | ||
6. Open `<YourProjectName>.xcworkspace` file in XCode. This file can be found in the `ios` folder of your React Native project. | ||
7. Click `File` and `Add Files to` | ||
8. Add the following files to the project: | ||
8. Add the following files from `../node_modules/opentok-react-native/ios` to the project: | ||
* `OTPublisher.h` | ||
@@ -74,6 +74,7 @@ * `OTPublisher.m` | ||
* `OTSubscriberView.swift` | ||
* `<YourProjectName>-Bridging-Header.h` | ||
9. Click `Create Bridging Header` when you're prompted with the following modal: `Would you like to configure an Objective-C bridging header?` | ||
10. Add the contents from the `Bridging-Header.h` file in `../node_modules/opentok-react-native/ios` to `<YourProjectName>-Bridging-Header.h` | ||
### Android Installation | ||
@@ -80,0 +81,0 @@ |
@@ -61,3 +61,3 @@ import React, { Component, Children, cloneElement } from 'react'; | ||
OT.disconnectSession((disconnectError) => { | ||
if (disconnectError) { | ||
if (!disconnectError) { | ||
this.setState({ | ||
@@ -67,3 +67,3 @@ sessionInfo: null, | ||
} else { | ||
handleError(error); | ||
handleError(disconnectError); | ||
} | ||
@@ -70,0 +70,0 @@ }); |
Sorry, the diff of this file is not supported yet
Install scripts
Supply chain riskInstall scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
237
0
0
91869
37
624