
Product
Introducing Pull Request Stories to Help Security Teams Track Supply Chain Risks
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.
react-native-zoom-sdk
Advanced tools
Before you start, you should add Zoom SDK by downloading iOS and Android SDK to your project
place iOS SDK in ios/lib/
directory of your project.
Or add this line to your Podfile
pod 'ZoomMobileRTC'
After that install the package with:
$ npm install react-native-zoom-sdk --save
Run the link
command. It will execute other SDK config to your app.
$ react-native link react-native-zoom-sdk
Libraries
➜ Add Files to [your project's name]
node_modules
➜ react-native-zoom-sdk
and add RNMobileRTC.xcodeproj
libRNMobileRTC.a
to your project's Build Phases
➜ Link Binary With Libraries
Cmd+R
)android/app/src/main/java/[...]/MainActivity.java
import com.reactor.RNMobileRTCPackage;
to the imports at the top of the filenew RNMobileRtcPackage()
to the list returned by the getPackages()
methodandroid/settings.gradle
:
include ':react-native-zoom-sdk'
project(':react-native-zoom-sdk').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-zoom-sdk/android')
android/app/build.gradle
:
compile project(':react-native-zoom-sdk')
initialize
Initializes the SDK with SDK authorization. Returns a promise as a result.
Catch and handle errors with codes from RNMobileRTC.AuthError
object.
Signature:
RNMobileRTC.initialize(sdkKey, sdkSecret, 'zoom.us')
startMeeting
Starts the new meeting. Returns a promise that represents a result of starting
the meeting. Catch and handle error types from RNMobileRTC.MeetingError
object
Signature:
RNMobileRTC.startMeeting({
meetingNumber: '0123456789',
userName: 'Nana',
userType: UserType.ZOOM_USER,
})
joinMeeting
Joins the user to the meeting. Returns a promise that represents a result of joining
to the meeting. Catch and handle error types from RNMobileRTC.MeetingError
object
Signature:
RNMobileRTC.joinMeeting({ meetingNumber: '0123456789', userName: 'Nana', })
const { UserType } = RNMobileRTC;
UserType.API_USER // API user type
UserType.ZOOM_USER // Work email user type
UserType.SSO_USER // Single-sign-on user type
import RNMobileRTC from 'react-native-zoom-sdk';
export default class App extends Component<{}> {
constructor() {
super();
...
RNMobileRTC.initialize(key, secret, domain)
.then((result) => alert(result))
.catch((error) => { throw new Error(error.message) });
}
handleJoinTheMeeting() {
// Join the meeting
RNMobileRTC.joinMeeting({
meetingNumber: '0123456789',
userName: 'Nana',
// pwd: 'my password',
// participantId: '111',
}).then((result) => alert(result))
.catch((error) => {
if (error.code === RNMobileRTC.MeetingError.MEETING_NOT_EXIST) {
console.error('Meeting does not exist!');
}
});
}
render() {
return (
<View style={styles.container}>
<TouchableOpacity onPress={this.handleJoinTheMeeting}>
<Text style={styles.welcome}>
Join the meeting!
</Text>
</TouchableOpacity>
</View>
);
}
}
FAQs
Zoom.us SDK bridge for React Native
The npm package react-native-zoom-sdk receives a total of 1 weekly downloads. As such, react-native-zoom-sdk popularity was classified as not popular.
We found that react-native-zoom-sdk demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.
Research
/Security News
npm author Qix’s account was compromised, with malicious versions of popular packages like chalk-template, color-convert, and strip-ansi published.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.