haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
jiti-meet/ios/Podfile

68 lines
2.1 KiB
Plaintext
Raw Normal View History

ios: drop iOS 9 support WebRTC no longer actively fixes iOS 9 issues.
2018-12-05 12:55:32 +00:00
platform :ios, '10.0'
[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
workspace 'jitsi-meet'
rn: add Firebase integration This is done at the app level, not the SDK. Currently 2 Firebase services are used: - Crashlytics - Dynamic Links They are enabled in tandem, if the appropriate Google services file (GoogleService-Info.plist on iOS or google-services.json on Android) is found. Each service needs to be individually enabled in the Firebase console.
2018-12-28 09:38:56 +00:00
target 'jitsi-meet' do
project 'app/app.xcodeproj'
ios: pin all pod dependencies
2019-03-21 15:47:03 +00:00
pod 'Crashlytics', '~> 3.12.0'
pod 'Fabric', '~> 1.9.0'
pod 'Firebase/Core', '~> 5.18.0'
pod 'Firebase/DynamicLinks', '~> 5.18.0'
rn: add Firebase integration This is done at the app level, not the SDK. Currently 2 Firebase services are used: - Crashlytics - Dynamic Links They are enabled in tandem, if the appropriate Google services file (GoogleService-Info.plist on iOS or google-services.json on Android) is found. Each service needs to be individually enabled in the Firebase console.
2018-12-28 09:38:56 +00:00
end
[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
target 'JitsiMeet' do
[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
project 'sdk/sdk.xcodeproj'
[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
pod 'React', :path => '../node_modules/react-native', :subspecs => [
'Core',
[iOS] Fix warning about RCTBatchedBridge deprecation It's removed in RN >= 0.55. This aligns the project with the official documentation: https://facebook.github.io/react-native/docs/integration-with-existing-apps.html#configuring-cocoapods-dependencies
2018-05-21 13:50:04 +00:00
'CxxBridge',
feat(web/RN): update React to v16 and React Native to 0.49
2017-10-24 22:26:56 +00:00
'DevSupport',
[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
'RCTActionSheet',
'RCTAnimation',
'RCTImage',
'RCTLinkingIOS',
'RCTNetwork',
'RCTText',
'RCTWebSocket',
]
feat(web/RN): update React to v16 and React Native to 0.49
2017-10-24 22:26:56 +00:00
pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
[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
[iOS] Fix warning about RCTBatchedBridge deprecation It's removed in RN >= 0.55. This aligns the project with the official documentation: https://facebook.github.io/react-native/docs/integration-with-existing-apps.html#configuring-cocoapods-dependencies
2018-05-21 13:50:04 +00:00
pod 'DoubleConversion',
:podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
[RN] Update react-native to 0.55.4 Also bump React to 16.3.2, since it's required.
2018-05-22 12:05:01 +00:00
pod 'glog',
:podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
[iOS] Fix warning about RCTBatchedBridge deprecation It's removed in RN >= 0.55. This aligns the project with the official documentation: https://facebook.github.io/react-native/docs/integration-with-existing-apps.html#configuring-cocoapods-dependencies
2018-05-21 13:50:04 +00:00
pod 'Folly',
:podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
feat(amplitude): add mobile implementation
2019-01-24 15:37:55 +00:00
pod 'Amplitude-iOS', '~> 4.0.4'
ios: pin all pod dependencies
2019-03-21 15:47:03 +00:00
pod 'ObjectiveDropboxOfficial', '~> 3.9.4'
feat(dropbox): Implement react-native module.
2018-09-24 23:22:00 +00:00
[RN] Cache avatars and provide a default in case load fails Avatars are cached to the filesystem and loaded from there when requested again. The cache is cleaned after a conference ends and on application startup (defensive move). In addition, implement a fully local avatar system, which is used as a fallback when loading a remote avatar fails. It can also be forced using a prop. The fully local avatars use a user icon as a mask and apply a background color qhich is picked by hashing the URI passed to the avatar. If no URI is passed a random color is chosen. A grace period of 1 second is also implemented so a default local avatar will be rendered if an Avatar component is mounted but has no URI. If a URI is specified later on, it will be loaded and displayed. In case loading the remote avatar fails, the locally generated one will be used.
2017-07-21 14:41:01 +00:00
pod 'react-native-background-timer',
:path => '../node_modules/react-native-background-timer'
rn: add DialInSummary
2019-05-07 14:50:57 +00:00
pod 'react-native-calendar-events',
:path => '../node_modules/react-native-calendar-events'
[RN] Replace cached image implementation Use react-native-fastimage, which uses 2 full-native image impleentations using well known and mature (native) libraries. This gets us rid of 2 libraries which were observerd as a source of bugs and created trouble with dependencies: react-native-fetch-blob and react-native-img-cache. They are also no longer well maintained.
2018-07-31 09:44:48 +00:00
pod 'react-native-fast-image',
:path => '../node_modules/react-native-fast-image'
[RN] Cache avatars and provide a default in case load fails Avatars are cached to the filesystem and loaded from there when requested again. The cache is cleaned after a conference ends and on application startup (defensive move). In addition, implement a fully local avatar system, which is used as a fallback when loading a remote avatar fails. It can also be forced using a prop. The fully local avatars use a user icon as a mask and apply a background color qhich is picked by hashing the URI passed to the avatar. If no URI is passed a random color is chosen. A grace period of 1 second is also implemented so a default local avatar will be rendered if an Avatar component is mounted but has no URI. If a URI is specified later on, it will be loaded and displayed. In case loading the remote avatar fails, the locally generated one will be used.
2017-07-21 14:41:01 +00:00
pod 'react-native-keep-awake',
:path => '../node_modules/react-native-keep-awake'
rn: add DialInSummary
2019-05-07 14:50:57 +00:00
pod 'react-native-webview',
:path => '../node_modules/react-native-webview'
[RN] Add conference navigation bar
2019-01-30 15:43:57 +00:00
pod 'BVLinearGradient',
:path => '../node_modules/react-native-linear-gradient'
[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
pod 'react-native-webrtc', :path => '../node_modules/react-native-webrtc'
[RN] Add Google Sign In to live streaming
2018-08-10 10:30:00 +00:00
pod 'RNGoogleSignin',
:path => '../node_modules/react-native-google-signin'
feat: add join/leave sounds on mobile Adds base/sounds feature which allows other features to register a sound source under specified id. A new SoundsCollection component will then render corresponding HTMLAudioElement for each such sound. Once "setRef" callback is called by the HTMLAudioElement, this element will be added to the Redux store. When that happens sound can be played through the new 'playSound' action which will call play() method on the stored HTMLAudioElement instance.
2018-02-26 19:37:12 +00:00
pod 'RNSound', :path => '../node_modules/react-native-sound'
[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
pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons'
watchos: add watchOS app Co-authored-by: Pawel Domas <pawel.domas@jitsi.org>
2017-09-27 08:29:42 +00:00
pod 'RNWatch', :path => '../node_modules/react-native-watch-connectivity'
[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
end
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
ios: enable bitcode Time has come. We need to enable bitcode. It's optional for iOS targets, but mandatory for the entire project if there is a watchOS target. Since we have a watchOS target, it's time to enable it.
2019-05-03 13:44:05 +00:00
config.build_settings['ENABLE_BITCODE'] = '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
end
end
end