jitsi-meet

Commit Graph

Author	SHA1	Message	Date
Saúl Ibarra Corretgé	b920140488	android: update Gradle plugin version for AS 3.0.1	8 years ago
Saúl Ibarra Corretgé	49acd6bf6a	android: simplify using the Google Maven repo reference Also remove mavenLocal since we don't need it.	8 years ago
Saúl Ibarra Corretgé	3460fe03e5	android: update target SDK version Android Oreo (API level 26) is supported since React Native 50.	8 years ago
Saúl Ibarra Corretgé	5308f78c9a	[Android] Fix Android Studio 3.0 (final)	8 years ago
Saúl Ibarra Corretgé	a14cc60e30	[Android] Specify build tools version Android Studio won't build the app otherwise. Since the gradle plugin 3.0 beta7, the minimum supported build tools version is 26.0.2, so set it to that. Also bump compileSdkVersion to 26 since they need to match (in the major number, that is). The target API is still 25. Android Oreo (26) brought some changes in overlay permissions which I haven't figured out yet.	8 years ago
Saúl Ibarra Corretgé	ae0e37be34	[Android] Fix Android Studio 3.0 RC2	8 years ago
Lyubo Marinov	e0b73fdd1c	[Android] Fix Android Studio 3.0 Beta 7	8 years ago
Lyubo Marinov	b3cef401f2	[Android] Fix Android Studio 3.0 Beta 6	8 years ago
Saúl Ibarra Corretgé	fe8f383a41	[Android] Update gradle plugin version for Android Studio 3 beta 5	8 years ago
Lyubo Marinov	72c9933e73	[RN] SDK building, installing, and publishing Based on work authored by Shuai Li <sli@atlassian.com>, Daniel Ornelas <dornelas@atlassian.com>, and Lyubo Marinov <lmarinov@atlassian.com>.	8 years ago
Saúl Ibarra Corretgé	ba49c7955a	[Android] Fix gradle and plugin versions with Android Studio 3.0 Beta 4	8 years ago
Saúl Ibarra Corretgé	5f55b3198c	[Android] Update gradle plugin version for Android Studio 3 beta 2	8 years ago
Saúl Ibarra Corretgé	ca80839094	[Android] Fix gradle and plugin versions with Android Studio 3.0 Canary 9	8 years ago
Saúl Ibarra Corretgé	4f6ec920cd	[Android] Set targetApiVersion to 25 We keep being compatible with versions all the way down to 16 for now, but this will disable internal compatibility shims when running on 25.	8 years ago
Saúl Ibarra Corretgé	0d33844d51	[Android] Use an appropriate Android support library version It must match the compileSdkVersion major number.	8 years ago
Saúl Ibarra Corretgé	51934dac1b	[Android] Fix gradle version with Android Studio 3.0 Canary 8	8 years ago
Saúl Ibarra Corretgé	326ce4217f	[Android] Fix gradle and plugin versions with Android Studio 3.0 Canary 6	8 years ago
Saúl Ibarra Corretgé	96bfcafc97	[Android] Use target API 23 This reverts commit `c9a29153dd`. Now that react-native-webrtc supports the permissions system in 23, use it since it provides a more pleasant experience to users. In addition, fix a bug in the previous code: the React Native view must be loaded after we have acquired the permission to draw on top of other apps, otherwise our app may crash while we accept the permission, since React may try to draw.	8 years ago
Lyubo Marinov	948d18f954	[Android] Fix "Minimum supported Gradle version is 4.1-milestone-1"	8 years ago
Saúl Ibarra Corretgé	01ac394e92	[Android] Fix compileSdkVersion It must match the major number in buildToolsVersion.	8 years ago
Lyubo Marinov	2fa7e777d6	Speed `react-native run-android` up	8 years ago
Saúl Ibarra Corretgé	c9a29153dd	[RN] Lower Android target SDK version to 22 API level 22 is below 23 (aka Marshmallow), which included an overhaul in the permissions system. React Native recommends 22 (it's the default when you create a new app) and there have been reports when set higher [0] and [1]. This also fixes a critical bug, wherein Jitsi Meet wouldn't request permissions for the camera and microphone. Last, this change also allows us to get rid of the overlay checking code, because it was only needed for API level 23 or higher. [0]: https://github.com/facebook/react-native/pull/10479 [1]: https://github.com/facebook/react-native/issues/10587	8 years ago
Lyubo Marinov	90466183d6	[RN] Consistency in Jitsi Meet SDK for Android	8 years ago
Saúl Ibarra Corretgé	ddea60efe9	[RN] Add initial Jitsi Meet SDK for Android Dames en heren, welcome to Jitsi Meet SDK for Android, the Jitsi Meet library for Android. The Jitsi Meet SDK encapsulates React Native and all the dependencies Jitsi Meet has so other aopplications can integrate it easily. Unlike iOS, creating "fat" libraries is not allways (if at all) possible on Android, however, effort was put into making the integration as easy as possible. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of an Android library, hidden away from the application using it. This surfaced as a number of issues which had to be addressed specifically due to our use-case: - Activity lifecycle methods must be linked with the React Native engine, so the library provides wrapper methods. - Custom fonts have to be manually added as assets, since the provided gradle script doesn't work properly in a library target. - The RN packager has to be manually triggered since the gradle script will no longer do it for us. At this stage, the Jitsi Meet application is just a small single activity application which uses the Jitsi Meet SDK to create a single activity which represents the entire application. Events and external conference handling are forthcoming. PS: Yours truly would like to add that it was a lot more fun to work on the iOS side of things.	8 years ago
Lyubo Marinov	e89c2b242d	Android plugin for Gradle 2.2.3 Recent versions of the Android plugin for Gradle started to automatically download the SDK build tools dependency if it is not installed already. So it is no longer necessary to have the developer of the Android app install the SDK build tools dependency in advance.	8 years ago
Lyubomir Marinov	7f3ff13c18	Merge jitsi-meet-react's mobile support As a step toward merging jitsi-meet-react with jitsi-meet to share as much source code as possible between mobile and Web, merge the part of jitsi-meet-react's source tree which supports mobile inside the jitsi-meet source tree and leave jitsi-meet-react's Web support in the source code revision history but don't have it in master anymore because it's different from jitsi-meet's Web support. In other words, the two projects are mechanically merged at the file level and don't really share source code between mobile and Web.	9 years ago
Lyubomir Marinov	d55e0f70d9	Import jitsi/jitsi-meet-react#2f23d98 As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at `2f23d98424` i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code.	9 years ago

26 Commits (2f23f8e4004b611af8318d32ba61325ec003bf5c)