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

47 lines
1.2 KiB
Plaintext
Raw Normal View History

feat(rn) update React Native to version 0.63 I'm updating to RN 0.63 instead of the latest (0.66 at the time of this writing) so we can update the navigation related libraries to their latest versions, and then proceed with the larger leap towards the latest RN.
2022-01-06 12:48:08 +00:00
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
feat(ios) drop support for iOS 11
2021-03-05 11:07:25 +00:00
platform :ios, '12.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'
feat(rn) update React Native to version 0.63 I'm updating to RN 0.63 instead of the latest (0.66 at the time of this writing) so we can update the navigation related libraries to their latest versions, and then proceed with the larger leap towards the latest RN.
2022-01-06 12:48:08 +00:00
feat(rn) switch to XCFramework and WebRTC M87
2020-11-18 14:17:00 +00:00
install! 'cocoapods', :deterministic_uuids => false
[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
feat(ios) rename SDK target to JitsiMeetSDK Swift has a longstanding bug where a framework and a type cannot be named the same. We have somehow managed to not run into this, but it now seems to be hitting us. Since this is a breaking change, this starts the road for SDK 3.0.
2020-12-17 08:40:29 +00:00
target 'JitsiMeet' do
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
project 'app/app.xcodeproj'
fix(crashlytics) add missing dependency Looks like the "Firebase Analytics" dependency is needed when migrating to the new Firebase Crashlytics SDK. We are only interested in the "latest iversion crash-free users" stat, which seems to require this. The documentartion is somewhat confusing though.
2020-09-29 12:24:44 +00:00
pod 'Firebase/Analytics', '~> 6.33.0'
pod 'Firebase/Crashlytics', '~> 6.33.0'
pod 'Firebase/DynamicLinks', '~> 6.33.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
feat(ios) rename SDK target to JitsiMeetSDK Swift has a longstanding bug where a framework and a type cannot be named the same. We have somehow managed to not run into this, but it now seems to be hitting us. Since this is a breaking change, this starts the road for SDK 3.0.
2020-12-17 08:40:29 +00:00
target 'JitsiMeetSDK' 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: use new AsyncStorage package It was extracted from the RN core to a community maintained package.
2019-05-08 12:51:14 +00:00
# React Native and its dependencies
#
feat(rn) update React Native to version 0.63 I'm updating to RN 0.63 instead of the latest (0.66 at the time of this writing) so we can update the navigation related libraries to their latest versions, and then proceed with the larger leap towards the latest RN.
2022-01-06 12:48:08 +00:00
config = use_native_modules!
feat(rn) update React Native to version 0.66
2022-01-14 10:44:02 +00:00
use_react_native!(
:path => config["reactNativePath"],
:hermes_enabled => false
)
rn: use new AsyncStorage package It was extracted from the RN core to a community maintained package.
2019-05-08 12:51:14 +00:00
# Native pod dependencies
#
fix(ios) make sure arm64 sim is not excluded Also update native dependencies.
2022-02-21 13:44:27 +00:00
pod 'CocoaLumberjack', '3.7.2'
pod 'ObjectiveDropboxOfficial', '6.2.3'
[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|
feat(rn) update React Native to version 0.66
2022-01-14 10:44:02 +00:00
react_native_post_install(installer)
feat(rn,deps) update React Native to 0.67
2022-04-05 12:11:09 +00:00
__apply_Xcode_12_5_M1_post_install_workaround(installer)
[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
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'
ios: support building with Xcode 11
2019-10-03 08:24:00 +00:00
config.build_settings['SUPPORTS_MACCATALYST'] = 'NO'
feat(ios) drop support for iOS 11
2021-03-05 11:07:25 +00:00
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.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
end
end
end