This fork changes as been merged back on cordova-plugin-iosrtc
repository and will be released on cordova-plugin-iosrtc
version 5.0.0, for more information see PR cordova-rtc#363
This Cordova Plugin cordova-plugin-iosrtc-simplyrtc
module version is a fork of cordova-plugin-iosrtc
hosted on Github originally made by Saúl Ibarra Corretgé (https://bettercallsaghul.com) and available here: https://github.com/BasqueVoIPMafia/cordova-plugin-iosrtc/
This fork of cordova-plugin-iosrtc
module named cordova-plugin-iosrtc-simplyrtc
starts at version 4.0.3-rc1
in case previous the repository decides to pick up work again on version 4.0.3
.
For more information please visit: cordova-rtc#353
Cordova iOS plugin exposing the ̶f̶u̶l̶l̶ WebRTC W3C JavaScript APIs.
- Public Google Group (mailing list) for questions and discussions about cordova-plugin-iosrtc.
- Bug Tracker for reporting issues and requesting new features (please don't use the bug tracker for questions or problems, use the mailing list instead).
- NPM package.
Yet another WebRTC SDK for iOS?
Absolutely not. This plugin exposes the WebRTC W3C API for Cordova iOS apps (you know there is no WebRTC in iOS, right?), which means no need to learn "yet another WebRTC API" and no need to use a specific service/product/provider.
Who?
This plugin was initially developed at eFace2Face, and later maintained by the community, specially by Saúl Ibarra Corretgé (The OpenSource Warrior Who Does Not Burn).
In order to make this Cordova plugin run into a iOS application some requirements must be satisfied in both development computer and target devices:
- Xcode >= 7.2.1
- iOS >= 9 (run on lower versions at your own risk, but don't report issues)
cordova-ios
4.X
Within your Cordova project:
$ cordova plugin add cordova-plugin-iosrtc-simplyrtc
(or add it into a <plugin>
entry in the config.xml
of your app).
- Remove the iOS platform and add it again (this apply "hook" file):
$ cordova platform remove ios
$ cordova platform add ios
- Building: Guidelines for building a Cordova iOS application including the cordova-plugin-iosrtc plugin.
- Building
libwebrtc
: Guidelines for building Google's libwebrtc with modifications needed by the cordova-plugin-iosrtc plugin (just in case you want to use a different version of libwebrtc or apply your own changes to it).
The plugin exposes the cordova.plugins.iosrtc
JavaScript namespace which contains all the WebRTC classes and functions.
var pc = new cordova.plugins.iosrtc.RTCPeerConnection({
iceServers: []
});
cordova.plugins.iosrtc.getUserMedia(
// constraints
{ audio: true, video: true },
// success callback
function (stream) {
console.log('got local MediaStream: ', stream);
pc.addStream(stream);
},
// failure callback
function (error) {
console.error('getUserMedia failed: ', error);
}
);
In case you'd like to expose the API in the global namespace like regular browsers you can do the following:
// Just for Cordova apps.
document.addEventListener('deviceready', function () {
// Just for iOS devices.
if (window.device.platform === 'iOS') {
cordova.plugins.iosrtc.registerGlobals();
// load adapter.js
var script = document.createElement("script");
script.type = "text/javascript";
script.src = "js/adapter-latest.js";
script.async = false;
document.getElementsByTagName("head")[0].appendChild(script);
}
});
And that's all. Now you have window.RTCPeerConnection
, navigator.getUserMedia
, etc.
See the FAQ.
Read the full documentation in the docs folder.
People and companies using cordova-plugin-iosrtc.
If you are using the plugin we would love to hear back from you!
Don't call plugin methods within WebSocket events (onopen
, onmessage
, etc). There is an issue in iOS Safari (see issue #12). Instead run a setTimeout()
within the WebSocket event if you need to call plugin methods on it.
Or better yet, include the provided ios-websocket-hack.js in your app and load into your index.html
as follows:
<script src="cordova.js"></script>
<script src="ios-websocket-hack.min.js"></script>
There is no real media source attached to the <video>
element so some HTML5 video events and properties are artificially emitted/set by the plugin on behalf of the video element.
Methods such as play()
, pause()
are not implemented. In order to pause a video just set enabled = false
on the associated MediaStreamTrack
.
See CHANGELOG.md.
- Harold Thetiot
- Iñaki Baz Castillo (no longer active maintainer)
- Saúl Ibarra Corretgé (no longer active maintainer)
Looking for new maintainers. Interested? Comment here.
MIT :)