haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
jiti-meet/ios/app/app.xcodeproj/project.pbxproj

434 lines
16 KiB
Plaintext
Raw Normal View History

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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
// !$*UTF8*$!
{
archiveVersion = 1;
classes = {
};
objectVersion = 46;
objects = {
Coding style consistency Includes automatic recommended Xcode project file fixes.
2017-02-15 17:19:36 +00:00
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
/* Begin PBXBuildFile section */
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE6E1EC5BC3C00EEFB41 /* JitsiMeet.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 0B26BE6D1EC5BC3C00EEFB41 /* JitsiMeet.framework */; };
0B26BE6F1EC5BC3C00EEFB41 /* JitsiMeet.framework in Embed Frameworks */ = {isa = PBXBuildFile; fileRef = 0B26BE6D1EC5BC3C00EEFB41 /* JitsiMeet.framework */; settings = {ATTRIBUTES = (CodeSignOnCopy, RemoveHeadersOnCopy, ); }; };
0B412F1F1EDEE6E800B1A0A6 /* ViewController.m in Sources */ = {isa = PBXBuildFile; fileRef = 0B412F1E1EDEE6E800B1A0A6 /* ViewController.m */; };
0B412F211EDEE95300B1A0A6 /* Main.storyboard in Resources */ = {isa = PBXBuildFile; fileRef = 0B412F201EDEE95300B1A0A6 /* Main.storyboard */; };
[iOS] Link with WebRTC.framework at the top level Before, Jitsi Meet (the app) would only link with JitsiMeet.framework, which in turn embedded WebRTC.framework. While possible, Apple doesn't allow apps with nested frameworks to be submitted to the store. Now the app will link with WebRTC.framework directly so there is no framework nesting. A potential improvement here is to build WebRTC as a static library so it can then be embedded in JitsiMeet.framework and completely hidden from the app.
2017-06-19 16:00:33 +00:00
0BD6B4371EF82A6B00D1F4CD /* WebRTC.framework in Frameworks */ = {isa = PBXBuildFile; fileRef = 0BD6B4361EF82A6B00D1F4CD /* WebRTC.framework */; };
0BD6B4381EF82A6B00D1F4CD /* WebRTC.framework in Embed Frameworks */ = {isa = PBXBuildFile; fileRef = 0BD6B4361EF82A6B00D1F4CD /* WebRTC.framework */; settings = {ATTRIBUTES = (CodeSignOnCopy, RemoveHeadersOnCopy, ); }; };
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
13B07FBC1A68108700A75B9A /* AppDelegate.m in Sources */ = {isa = PBXBuildFile; fileRef = 13B07FB01A68108700A75B9A /* AppDelegate.m */; };
13B07FBD1A68108700A75B9A /* LaunchScreen.xib in Resources */ = {isa = PBXBuildFile; fileRef = 13B07FB11A68108700A75B9A /* LaunchScreen.xib */; };
13B07FBF1A68108700A75B9A /* Images.xcassets in Resources */ = {isa = PBXBuildFile; fileRef = 13B07FB51A68108700A75B9A /* Images.xcassets */; };
13B07FC11A68108700A75B9A /* main.m in Sources */ = {isa = PBXBuildFile; fileRef = 13B07FB71A68108700A75B9A /* main.m */; };
/* End PBXBuildFile section */
react-native-webrtc 0.53.1
2016-10-26 20:19:30 +00:00
/* Begin PBXCopyFilesBuildPhase section */
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE701EC5BC3C00EEFB41 /* Embed Frameworks */ = {
react-native-webrtc 0.53.1
2016-10-26 20:19:30 +00:00
isa = PBXCopyFilesBuildPhase;
buildActionMask = 2147483647;
dstPath = "";
dstSubfolderSpec = 10;
files = (
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE6F1EC5BC3C00EEFB41 /* JitsiMeet.framework in Embed Frameworks */,
[iOS] Link with WebRTC.framework at the top level Before, Jitsi Meet (the app) would only link with JitsiMeet.framework, which in turn embedded WebRTC.framework. While possible, Apple doesn't allow apps with nested frameworks to be submitted to the store. Now the app will link with WebRTC.framework directly so there is no framework nesting. A potential improvement here is to build WebRTC as a static library so it can then be embedded in JitsiMeet.framework and completely hidden from the app.
2017-06-19 16:00:33 +00:00
0BD6B4381EF82A6B00D1F4CD /* WebRTC.framework in Embed Frameworks */,
react-native-webrtc 0.53.1
2016-10-26 20:19:30 +00:00
);
name = "Embed Frameworks";
runOnlyForDeploymentPostprocessing = 0;
};
/* End PBXCopyFilesBuildPhase section */
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
/* Begin PBXFileReference section */
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE6D1EC5BC3C00EEFB41 /* JitsiMeet.framework */ = {isa = PBXFileReference; explicitFileType = wrapper.framework; path = JitsiMeet.framework; sourceTree = BUILT_PRODUCTS_DIR; };
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
0B412F1D1EDEE6E800B1A0A6 /* ViewController.h */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.h; path = ViewController.h; sourceTree = "<group>"; };
0B412F1E1EDEE6E800B1A0A6 /* ViewController.m */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.objc; path = ViewController.m; sourceTree = "<group>"; };
0B412F201EDEE95300B1A0A6 /* Main.storyboard */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = file.storyboard; name = Main.storyboard; path = Base.lproj/Main.storyboard; sourceTree = "<group>"; };
[iOS] Link with WebRTC.framework at the top level Before, Jitsi Meet (the app) would only link with JitsiMeet.framework, which in turn embedded WebRTC.framework. While possible, Apple doesn't allow apps with nested frameworks to be submitted to the store. Now the app will link with WebRTC.framework directly so there is no framework nesting. A potential improvement here is to build WebRTC as a static library so it can then be embedded in JitsiMeet.framework and completely hidden from the app.
2017-06-19 16:00:33 +00:00
0BD6B4361EF82A6B00D1F4CD /* WebRTC.framework */ = {isa = PBXFileReference; lastKnownFileType = wrapper.framework; name = WebRTC.framework; path = "../../node_modules/react-native-webrtc/ios/WebRTC.framework"; sourceTree = "<group>"; };
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
13B07F961A680F5B00A75B9A /* jitsi-meet.app */ = {isa = PBXFileReference; explicitFileType = wrapper.application; includeInIndex = 0; path = "jitsi-meet.app"; sourceTree = BUILT_PRODUCTS_DIR; };
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
13B07FAF1A68108700A75B9A /* AppDelegate.h */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.h; path = AppDelegate.h; sourceTree = "<group>"; };
13B07FB01A68108700A75B9A /* AppDelegate.m */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.objc; path = AppDelegate.m; sourceTree = "<group>"; };
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
13B07FB21A68108700A75B9A /* Base */ = {isa = PBXFileReference; lastKnownFileType = file.xib; name = Base; path = Base.lproj/LaunchScreen.xib; sourceTree = "<group>"; };
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
13B07FB51A68108700A75B9A /* Images.xcassets */ = {isa = PBXFileReference; lastKnownFileType = folder.assetcatalog; path = Images.xcassets; sourceTree = "<group>"; };
13B07FB61A68108700A75B9A /* Info.plist */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = text.plist.xml; path = Info.plist; sourceTree = "<group>"; };
13B07FB71A68108700A75B9A /* main.m */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.objc; path = main.m; sourceTree = "<group>"; };
B3B083EB1D4955FF0069CEE7 /* app.entitlements */ = {isa = PBXFileReference; lastKnownFileType = text.plist.entitlements; path = app.entitlements; sourceTree = "<group>"; };
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
/* End PBXFileReference section */
/* Begin PBXFrameworksBuildPhase section */
13B07F8C1A680F5B00A75B9A /* Frameworks */ = {
isa = PBXFrameworksBuildPhase;
buildActionMask = 2147483647;
files = (
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE6E1EC5BC3C00EEFB41 /* JitsiMeet.framework in Frameworks */,
[iOS] Link with WebRTC.framework at the top level Before, Jitsi Meet (the app) would only link with JitsiMeet.framework, which in turn embedded WebRTC.framework. While possible, Apple doesn't allow apps with nested frameworks to be submitted to the store. Now the app will link with WebRTC.framework directly so there is no framework nesting. A potential improvement here is to build WebRTC as a static library so it can then be embedded in JitsiMeet.framework and completely hidden from the app.
2017-06-19 16:00:33 +00:00
0BD6B4371EF82A6B00D1F4CD /* WebRTC.framework in Frameworks */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
);
runOnlyForDeploymentPostprocessing = 0;
};
/* End PBXFrameworksBuildPhase section */
/* Begin PBXGroup section */
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE711EC5BC4D00EEFB41 /* Frameworks */ = {
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
isa = PBXGroup;
children = (
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE6D1EC5BC3C00EEFB41 /* JitsiMeet.framework */,
[iOS] Link with WebRTC.framework at the top level Before, Jitsi Meet (the app) would only link with JitsiMeet.framework, which in turn embedded WebRTC.framework. While possible, Apple doesn't allow apps with nested frameworks to be submitted to the store. Now the app will link with WebRTC.framework directly so there is no framework nesting. A potential improvement here is to build WebRTC as a static library so it can then be embedded in JitsiMeet.framework and completely hidden from the app.
2017-06-19 16:00:33 +00:00
0BD6B4361EF82A6B00D1F4CD /* WebRTC.framework */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
);
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
name = Frameworks;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
sourceTree = "<group>";
};
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
13B07FAE1A68108700A75B9A /* src */ = {
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
isa = PBXGroup;
children = (
13B07FAF1A68108700A75B9A /* AppDelegate.h */,
13B07FB01A68108700A75B9A /* AppDelegate.m */,
13B07FB51A68108700A75B9A /* Images.xcassets */,
13B07FB61A68108700A75B9A /* Info.plist */,
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
13B07FB11A68108700A75B9A /* LaunchScreen.xib */,
13B07FB71A68108700A75B9A /* main.m */,
0B412F201EDEE95300B1A0A6 /* Main.storyboard */,
0B412F1D1EDEE6E800B1A0A6 /* ViewController.h */,
0B412F1E1EDEE6E800B1A0A6 /* ViewController.m */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
);
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
path = src;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
sourceTree = "<group>";
};
83CBB9F61A601CBA00E9B192 = {
isa = PBXGroup;
children = (
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
B3B083EB1D4955FF0069CEE7 /* app.entitlements */,
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE711EC5BC4D00EEFB41 /* Frameworks */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
83CBBA001A601CBA00E9B192 /* Products */,
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
13B07FAE1A68108700A75B9A /* src */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
);
indentWidth = 2;
sourceTree = "<group>";
tabWidth = 2;
};
83CBBA001A601CBA00E9B192 /* Products */ = {
isa = PBXGroup;
children = (
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
13B07F961A680F5B00A75B9A /* jitsi-meet.app */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
);
name = Products;
sourceTree = "<group>";
};
/* End PBXGroup section */
/* Begin PBXNativeTarget section */
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
13B07F861A680F5B00A75B9A /* jitsi-meet */ = {
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
isa = PBXNativeTarget;
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
buildConfigurationList = 13B07F931A680F5B00A75B9A /* Build configuration list for PBXNativeTarget "jitsi-meet" */;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
buildPhases = (
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0BBA83C41EC9F7600075A103 /* Run React packager */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
13B07F871A680F5B00A75B9A /* Sources */,
13B07F8C1A680F5B00A75B9A /* Frameworks */,
13B07F8E1A680F5B00A75B9A /* Resources */,
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B26BE701EC5BC3C00EEFB41 /* Embed Frameworks */,
B35383AD1DDA0083008F406A /* Adjust embedded framework architectures */,
0BB7DA181EC9E695007AAE98 /* Adjust ATS */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
);
buildRules = (
);
dependencies = (
);
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
name = "jitsi-meet";
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
productName = "Jitsi Meet";
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
productReference = 13B07F961A680F5B00A75B9A /* jitsi-meet.app */;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
productType = "com.apple.product-type.application";
};
/* End PBXNativeTarget section */
/* Begin PBXProject section */
83CBB9F71A601CBA00E9B192 /* Project object */ = {
isa = PBXProject;
attributes = {
Coding style consistency Includes automatic recommended Xcode project file fixes.
2017-02-15 17:19:36 +00:00
LastUpgradeCheck = 0820;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
ORGANIZATIONNAME = Facebook;
TargetAttributes = {
13B07F861A680F5B00A75B9A = {
DevelopmentTeam = BQNXB4G3KQ;
SystemCapabilities = {
com.apple.SafariKeychain = {
enabled = 1;
};
};
};
};
};
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
buildConfigurationList = 83CBB9FA1A601CBA00E9B192 /* Build configuration list for PBXProject "app" */;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
compatibilityVersion = "Xcode 3.2";
developmentRegion = English;
hasScannedForEncodings = 0;
knownRegions = (
en,
Base,
);
mainGroup = 83CBB9F61A601CBA00E9B192;
productRefGroup = 83CBBA001A601CBA00E9B192 /* Products */;
projectDirPath = "";
projectRoot = "";
targets = (
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
13B07F861A680F5B00A75B9A /* jitsi-meet */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
);
};
/* End PBXProject section */
/* Begin PBXResourcesBuildPhase section */
13B07F8E1A680F5B00A75B9A /* Resources */ = {
isa = PBXResourcesBuildPhase;
buildActionMask = 2147483647;
files = (
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B412F211EDEE95300B1A0A6 /* Main.storyboard in Resources */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
13B07FBF1A68108700A75B9A /* Images.xcassets in Resources */,
13B07FBD1A68108700A75B9A /* LaunchScreen.xib in Resources */,
);
runOnlyForDeploymentPostprocessing = 0;
};
/* End PBXResourcesBuildPhase section */
/* Begin PBXShellScriptBuildPhase section */
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0BB7DA181EC9E695007AAE98 /* Adjust ATS */ = {
isa = PBXShellScriptBuildPhase;
buildActionMask = 2147483647;
files = (
);
inputPaths = (
);
name = "Adjust ATS";
outputPaths = (
);
runOnlyForDeploymentPostprocessing = 0;
shellPath = /bin/sh;
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
shellScript = "../scripts/fixup-ats.sh";
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
};
0BBA83C41EC9F7600075A103 /* Run React packager */ = {
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
isa = PBXShellScriptBuildPhase;
buildActionMask = 2147483647;
files = (
);
inputPaths = (
);
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
name = "Run React packager";
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
outputPaths = (
);
runOnlyForDeploymentPostprocessing = 0;
shellPath = /bin/sh;
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
shellScript = "../scripts/run-packager.sh";
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
};
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
B35383AD1DDA0083008F406A /* Adjust embedded framework architectures */ = {
[iOS] Strip unwanted architectures from embedded frameworks
2016-11-14 14:32:24 +00:00
isa = PBXShellScriptBuildPhase;
buildActionMask = 2147483647;
files = (
);
inputPaths = (
);
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
name = "Adjust embedded framework architectures";
[iOS] Strip unwanted architectures from embedded frameworks
2016-11-14 14:32:24 +00:00
outputPaths = (
);
runOnlyForDeploymentPostprocessing = 0;
shellPath = /bin/sh;
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
shellScript = "../scripts/fixup-frameworks.sh";
[iOS] Strip unwanted architectures from embedded frameworks
2016-11-14 14:32:24 +00:00
};
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
/* End PBXShellScriptBuildPhase section */
/* Begin PBXSourcesBuildPhase section */
13B07F871A680F5B00A75B9A /* Sources */ = {
isa = PBXSourcesBuildPhase;
buildActionMask = 2147483647;
files = (
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
0B412F1F1EDEE6E800B1A0A6 /* ViewController.m in Sources */,
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
13B07FBC1A68108700A75B9A /* AppDelegate.m in Sources */,
13B07FC11A68108700A75B9A /* main.m in Sources */,
);
runOnlyForDeploymentPostprocessing = 0;
};
/* End PBXSourcesBuildPhase section */
/* Begin PBXVariantGroup section */
13B07FB11A68108700A75B9A /* LaunchScreen.xib */ = {
isa = PBXVariantGroup;
children = (
13B07FB21A68108700A75B9A /* Base */,
);
name = LaunchScreen.xib;
sourceTree = "<group>";
};
/* End PBXVariantGroup section */
/* Begin XCBuildConfiguration section */
13B07F941A680F5B00A75B9A /* Debug */ = {
isa = XCBuildConfiguration;
buildSettings = {
[iOS] Configuration-specific AppIcons While having configuration-specific AppIcons may be of questionable use, I'm more interested in using the Debug version for enterprise distribution and the Release version for AppStore distribution.
2017-11-15 22:02:57 +00:00
ASSETCATALOG_COMPILER_APPICON_NAME = AppIconDebug;
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
CODE_SIGN_ENTITLEMENTS = app.entitlements;
Fix the iOS enterprise deployment build
2016-10-17 23:57:15 +00:00
CURRENT_PROJECT_VERSION = 1;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
DEAD_CODE_STRIPPING = NO;
ENABLE_BITCODE = NO;
[iOS] Link with WebRTC.framework at the top level Before, Jitsi Meet (the app) would only link with JitsiMeet.framework, which in turn embedded WebRTC.framework. While possible, Apple doesn't allow apps with nested frameworks to be submitted to the store. Now the app will link with WebRTC.framework directly so there is no framework nesting. A potential improvement here is to build WebRTC as a static library so it can then be embedded in JitsiMeet.framework and completely hidden from the app.
2017-06-19 16:00:33 +00:00
FRAMEWORK_SEARCH_PATHS = (
"$(inherited)",
"../../node_modules/react-native-webrtc/ios",
);
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
HEADER_SEARCH_PATHS = (
"$(inherited)",
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include,
);
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
INFOPLIST_FILE = src/Info.plist;
[RN][iOS] Set deployment target to 9.0 According to Apple iOS devices with versions < 9.0 are 6%. https://developer.apple.com/support/app-store/
2017-01-12 22:20:03 +00:00
IPHONEOS_DEPLOYMENT_TARGET = 9.0;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
LD_RUNPATH_SEARCH_PATHS = "$(inherited) @executable_path/Frameworks";
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
LIBRARY_SEARCH_PATHS = "$(inherited)";
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
OTHER_LDFLAGS = (
"$(inherited)",
"-ObjC",
"-lc++",
);
PRODUCT_BUNDLE_IDENTIFIER = org.jitsi.JitsiMeet.ios;
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
PRODUCT_NAME = "jitsi-meet";
[iOS] iPad support
2017-01-12 22:24:01 +00:00
TARGETED_DEVICE_FAMILY = "1,2";
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
};
name = Debug;
};
13B07F951A680F5B00A75B9A /* Release */ = {
isa = XCBuildConfiguration;
buildSettings = {
[iOS] Configuration-specific AppIcons While having configuration-specific AppIcons may be of questionable use, I'm more interested in using the Debug version for enterprise distribution and the Release version for AppStore distribution.
2017-11-15 22:02:57 +00:00
ASSETCATALOG_COMPILER_APPICON_NAME = AppIconRelease;
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
CODE_SIGN_ENTITLEMENTS = app.entitlements;
Fix the iOS enterprise deployment build
2016-10-17 23:57:15 +00:00
CURRENT_PROJECT_VERSION = 1;
react-native-webrtc 0.53.1
2016-10-26 20:19:30 +00:00
ENABLE_BITCODE = NO;
[iOS] Link with WebRTC.framework at the top level Before, Jitsi Meet (the app) would only link with JitsiMeet.framework, which in turn embedded WebRTC.framework. While possible, Apple doesn't allow apps with nested frameworks to be submitted to the store. Now the app will link with WebRTC.framework directly so there is no framework nesting. A potential improvement here is to build WebRTC as a static library so it can then be embedded in JitsiMeet.framework and completely hidden from the app.
2017-06-19 16:00:33 +00:00
FRAMEWORK_SEARCH_PATHS = (
"$(inherited)",
"../../node_modules/react-native-webrtc/ios",
);
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
HEADER_SEARCH_PATHS = (
"$(inherited)",
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include,
);
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
INFOPLIST_FILE = src/Info.plist;
[RN][iOS] Set deployment target to 9.0 According to Apple iOS devices with versions < 9.0 are 6%. https://developer.apple.com/support/app-store/
2017-01-12 22:20:03 +00:00
IPHONEOS_DEPLOYMENT_TARGET = 9.0;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
LD_RUNPATH_SEARCH_PATHS = "$(inherited) @executable_path/Frameworks";
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
LIBRARY_SEARCH_PATHS = "$(inherited)";
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
OTHER_LDFLAGS = (
"$(inherited)",
"-ObjC",
"-lc++",
);
PRODUCT_BUNDLE_IDENTIFIER = org.jitsi.JitsiMeet.ios;
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
PRODUCT_NAME = "jitsi-meet";
[iOS] iPad support
2017-01-12 22:24:01 +00:00
TARGETED_DEVICE_FAMILY = "1,2";
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
};
name = Release;
};
83CBBA201A601CBA00E9B192 /* Debug */ = {
isa = XCBuildConfiguration;
buildSettings = {
ALWAYS_SEARCH_USER_PATHS = NO;
CLANG_CXX_LANGUAGE_STANDARD = "gnu++0x";
CLANG_CXX_LIBRARY = "libc++";
CLANG_ENABLE_MODULES = YES;
CLANG_ENABLE_OBJC_ARC = YES;
CLANG_WARN_BOOL_CONVERSION = YES;
CLANG_WARN_CONSTANT_CONVERSION = YES;
CLANG_WARN_DIRECT_OBJC_ISA_USAGE = YES_ERROR;
CLANG_WARN_EMPTY_BODY = YES;
CLANG_WARN_ENUM_CONVERSION = YES;
Automatic Xcode project file fixes
2017-01-22 21:56:40 +00:00
CLANG_WARN_INFINITE_RECURSION = YES;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
CLANG_WARN_INT_CONVERSION = YES;
CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
Automatic Xcode project file fixes
2017-01-22 21:56:40 +00:00
CLANG_WARN_SUSPICIOUS_MOVE = YES;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
CLANG_WARN_UNREACHABLE_CODE = YES;
CLANG_WARN__DUPLICATE_METHOD_MATCH = YES;
"CODE_SIGN_IDENTITY[sdk=iphoneos*]" = "iPhone Developer";
COPY_PHASE_STRIP = NO;
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
ENABLE_BITCODE = NO;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
ENABLE_STRICT_OBJC_MSGSEND = YES;
Automatic Xcode project file fixes
2017-01-22 21:56:40 +00:00
ENABLE_TESTABILITY = YES;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
GCC_C_LANGUAGE_STANDARD = gnu99;
GCC_DYNAMIC_NO_PIC = NO;
Automatic Xcode project file fixes
2017-01-22 21:56:40 +00:00
GCC_NO_COMMON_BLOCKS = YES;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
GCC_OPTIMIZATION_LEVEL = 0;
GCC_PREPROCESSOR_DEFINITIONS = (
"DEBUG=1",
"$(inherited)",
);
GCC_SYMBOLS_PRIVATE_EXTERN = NO;
GCC_WARN_64_TO_32_BIT_CONVERSION = YES;
GCC_WARN_ABOUT_RETURN_TYPE = YES_ERROR;
GCC_WARN_UNDECLARED_SELECTOR = YES;
GCC_WARN_UNINITIALIZED_AUTOS = YES_AGGRESSIVE;
GCC_WARN_UNUSED_FUNCTION = YES;
GCC_WARN_UNUSED_VARIABLE = YES;
HEADER_SEARCH_PATHS = (
"$(inherited)",
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include,
);
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
IPHONEOS_DEPLOYMENT_TARGET = 9.0;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
MTL_ENABLE_DEBUG_INFO = YES;
ONLY_ACTIVE_ARCH = YES;
SDKROOT = iphoneos;
};
name = Debug;
};
83CBBA211A601CBA00E9B192 /* Release */ = {
isa = XCBuildConfiguration;
buildSettings = {
ALWAYS_SEARCH_USER_PATHS = NO;
CLANG_CXX_LANGUAGE_STANDARD = "gnu++0x";
CLANG_CXX_LIBRARY = "libc++";
CLANG_ENABLE_MODULES = YES;
CLANG_ENABLE_OBJC_ARC = YES;
CLANG_WARN_BOOL_CONVERSION = YES;
CLANG_WARN_CONSTANT_CONVERSION = YES;
CLANG_WARN_DIRECT_OBJC_ISA_USAGE = YES_ERROR;
CLANG_WARN_EMPTY_BODY = YES;
CLANG_WARN_ENUM_CONVERSION = YES;
Automatic Xcode project file fixes
2017-01-22 21:56:40 +00:00
CLANG_WARN_INFINITE_RECURSION = YES;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
CLANG_WARN_INT_CONVERSION = YES;
CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
Automatic Xcode project file fixes
2017-01-22 21:56:40 +00:00
CLANG_WARN_SUSPICIOUS_MOVE = YES;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
CLANG_WARN_UNREACHABLE_CODE = YES;
CLANG_WARN__DUPLICATE_METHOD_MATCH = YES;
"CODE_SIGN_IDENTITY[sdk=iphoneos*]" = "iPhone Developer";
COPY_PHASE_STRIP = YES;
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
ENABLE_BITCODE = NO;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
ENABLE_NS_ASSERTIONS = NO;
ENABLE_STRICT_OBJC_MSGSEND = YES;
GCC_C_LANGUAGE_STANDARD = gnu99;
Automatic Xcode project file fixes
2017-01-22 21:56:40 +00:00
GCC_NO_COMMON_BLOCKS = YES;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
GCC_WARN_64_TO_32_BIT_CONVERSION = YES;
GCC_WARN_ABOUT_RETURN_TYPE = YES_ERROR;
GCC_WARN_UNDECLARED_SELECTOR = YES;
GCC_WARN_UNINITIALIZED_AUTOS = YES_AGGRESSIVE;
GCC_WARN_UNUSED_FUNCTION = YES;
GCC_WARN_UNUSED_VARIABLE = YES;
HEADER_SEARCH_PATHS = (
"$(inherited)",
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include,
);
[RN] Add initial Jitsi Meet SDK for iOS Ladies and gentlemen, allow me to introduce you to Jitsi Meet SDK for iOS, the mobile SDK which powers Jitsi Meet. The goal is to encapsulate the entire React Native app into a framework / SDK and offer an API for native (ObjC or Swift) applications to embed the Jitsi conferencing experience. While React Native can be embedded in native applications, I don't think it was designed to be embedded as part of a framework, 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: - Universal / deep linking needed to be wrapped to avoid the embedding app from linking with RN. - The bundle URL had to be manually constructed, since RN considers that all resources are in the main bundle, but in case of a framework that is not the case. - Custom fonts had to be manually loaded, since UIAppFonts doesn't work on the framework's Info.plist file. - The RN packager has to be manually triggered since the React project will no longer do it for us. - Custom App Transport Security rules were added since the builtin way to do it modifies the framework's Info.plist, which is useless in this case. At this stage, the Jitsi Meet application is just a small single view application which uses the Jitsi Meet SDK to create a single view which represents the entire application. Events and external conference handling are forthcoming.
2017-05-08 15:21:30 +00:00
IPHONEOS_DEPLOYMENT_TARGET = 9.0;
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
MTL_ENABLE_DEBUG_INFO = NO;
SDKROOT = iphoneos;
VALIDATE_PRODUCT = YES;
};
name = Release;
};
/* End XCBuildConfiguration section */
/* Begin XCConfigurationList section */
[RN] Rename jitsi-meet-react to jitsi-meet
2017-05-08 14:43:55 +00:00
13B07F931A680F5B00A75B9A /* Build configuration list for PBXNativeTarget "jitsi-meet" */ = {
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
isa = XCConfigurationList;
buildConfigurations = (
13B07F941A680F5B00A75B9A /* Debug */,
13B07F951A680F5B00A75B9A /* Release */,
);
defaultConfigurationIsVisible = 0;
defaultConfigurationName = Release;
};
[RN] Consistency in Jitsi Meet SDK for iOS 1. Aligns the project structure of Jitsi Meet SDK for iOS with that for Android for better comprehension. 2. The command `react-native run-ios` uses the last Xcode project or workspace in the list of these sorted in alphabetical order. Which limits our freedom in naming. Thus having only an Xcode project in the root directory of the iOS project structure gives us back the freedom in naming. 3. Allows the Podspec to work for the app project in addition to the sdk project because we need Crashlytics in the app which is integrated via Cocoapods as well. 4. Further removes references to JitsiKit in the source code for the sake of consistent naming.
2017-06-06 22:43:51 +00:00
83CBB9FA1A601CBA00E9B192 /* Build configuration list for PBXProject "app" */ = {
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 https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 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.
2016-10-05 14:36:59 +00:00
isa = XCConfigurationList;
buildConfigurations = (
83CBBA201A601CBA00E9B192 /* Debug */,
83CBBA211A601CBA00E9B192 /* Release */,
);
defaultConfigurationIsVisible = 0;
defaultConfigurationName = Release;
};
/* End XCConfigurationList section */
};
rootObject = 83CBB9F71A601CBA00E9B192 /* Project object */;
}