status-im
/
react-native-cameraroll
mirror of https://github.com/status-im/react-native-cameraroll.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
react-native-cameraroll/ios/RNCCameraRoll.xcodeproj/project.pbxproj

291 lines
10 KiB
Plaintext
Raw Normal View History

Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
// !$*UTF8*$!
{
archiveVersion = 1;
classes = {
};
objectVersion = 46;
objects = {
/* Begin PBXBuildFile section */
in file renames
2019-02-24 04:29:24 +00:00
143879351AAD238D00F088A5 /* RNCCameraRollManager.m in Sources */ = {isa = PBXBuildFile; fileRef = 143879341AAD238D00F088A5 /* RNCCameraRollManager.m */; };
fix iOS library file reference
2019-02-24 05:48:37 +00:00
4F788CB822226740001DB9D2 /* RNCAssetsLibraryRequestHandler.m in Sources */ = {isa = PBXBuildFile; fileRef = 4F788CB722226740001DB9D2 /* RNCAssetsLibraryRequestHandler.m */; };
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
/* End PBXBuildFile section */
/* Begin PBXCopyFilesBuildPhase section */
58B5115B1A9E6B3D00147676 /* CopyFiles */ = {
isa = PBXCopyFilesBuildPhase;
buildActionMask = 2147483647;
dstPath = "include/$(PRODUCT_NAME)";
dstSubfolderSpec = 16;
files = (
);
runOnlyForDeploymentPostprocessing = 0;
};
/* End PBXCopyFilesBuildPhase section */
/* Begin PBXFileReference section */
in file renames
2019-02-24 04:29:24 +00:00
143879331AAD238D00F088A5 /* RNCCameraRollManager.h */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.h; lineEnding = 0; path = RNCCameraRollManager.h; sourceTree = "<group>"; xcLanguageSpecificationIdentifier = xcode.lang.objcpp; };
143879341AAD238D00F088A5 /* RNCCameraRollManager.m */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.objc; path = RNCCameraRollManager.m; sourceTree = "<group>"; };
fix iOS library file reference
2019-02-24 05:48:37 +00:00
4F788CB622226740001DB9D2 /* RNCAssetsLibraryRequestHandler.h */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.h; path = RNCAssetsLibraryRequestHandler.h; sourceTree = "<group>"; };
4F788CB722226740001DB9D2 /* RNCAssetsLibraryRequestHandler.m */ = {isa = PBXFileReference; fileEncoding = 4; lastKnownFileType = sourcecode.c.objc; path = RNCAssetsLibraryRequestHandler.m; sourceTree = "<group>"; };
in file renames
2019-02-24 04:29:24 +00:00
58B5115D1A9E6B3D00147676 /* libRNCCameraRoll.a */ = {isa = PBXFileReference; explicitFileType = archive.ar; includeInIndex = 0; path = libRNCCameraRoll.a; sourceTree = BUILT_PRODUCTS_DIR; };
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
/* End PBXFileReference section */
/* Begin PBXFrameworksBuildPhase section */
58B5115A1A9E6B3D00147676 /* Frameworks */ = {
isa = PBXFrameworksBuildPhase;
buildActionMask = 2147483647;
files = (
);
runOnlyForDeploymentPostprocessing = 0;
};
/* End PBXFrameworksBuildPhase section */
/* Begin PBXGroup section */
58B511541A9E6B3D00147676 = {
isa = PBXGroup;
children = (
fix iOS library file reference
2019-02-24 05:48:37 +00:00
4F788CB622226740001DB9D2 /* RNCAssetsLibraryRequestHandler.h */,
4F788CB722226740001DB9D2 /* RNCAssetsLibraryRequestHandler.m */,
in file renames
2019-02-24 04:29:24 +00:00
143879331AAD238D00F088A5 /* RNCCameraRollManager.h */,
143879341AAD238D00F088A5 /* RNCCameraRollManager.m */,
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
58B5115E1A9E6B3D00147676 /* Products */,
);
indentWidth = 2;
sourceTree = "<group>";
tabWidth = 2;
Standardize project indentation settings on 2 spaces Summary: Hi React Native folks! Love your work! To make contributing easier, this sets the indentation settings of all the Xcode projects to 2 spaces to match their contents. Closes https://github.com/facebook/react-native/pull/15275 Differential Revision: D5526462 Pulled By: javache fbshipit-source-id: cbf0a8a87a1dbe31fceed2f0fffc53839cc06e59
2017-07-31 12:08:51 +00:00
usesTabs = 0;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
};
58B5115E1A9E6B3D00147676 /* Products */ = {
isa = PBXGroup;
children = (
in file renames
2019-02-24 04:29:24 +00:00
58B5115D1A9E6B3D00147676 /* libRNCCameraRoll.a */,
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
);
name = Products;
sourceTree = "<group>";
};
/* End PBXGroup section */
/* Begin PBXNativeTarget section */
in file renames
2019-02-24 04:29:24 +00:00
58B5115C1A9E6B3D00147676 /* RNCCameraRoll */ = {
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
isa = PBXNativeTarget;
in file renames
2019-02-24 04:29:24 +00:00
buildConfigurationList = 58B511711A9E6B3D00147676 /* Build configuration list for PBXNativeTarget "RNCCameraRoll" */;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
buildPhases = (
58B511591A9E6B3D00147676 /* Sources */,
58B5115A1A9E6B3D00147676 /* Frameworks */,
58B5115B1A9E6B3D00147676 /* CopyFiles */,
);
buildRules = (
);
dependencies = (
);
in file renames
2019-02-24 04:29:24 +00:00
name = RNCCameraRoll;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
productName = RCTNetworkImage;
in file renames
2019-02-24 04:29:24 +00:00
productReference = 58B5115D1A9E6B3D00147676 /* libRNCCameraRoll.a */;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
productType = "com.apple.product-type.library.static";
};
/* End PBXNativeTarget section */
/* Begin PBXProject section */
58B511551A9E6B3D00147676 /* Project object */ = {
isa = PBXProject;
attributes = {
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
LastUpgradeCheck = 0940;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
ORGANIZATIONNAME = Facebook;
TargetAttributes = {
58B5115C1A9E6B3D00147676 = {
CreatedOnToolsVersion = 6.1.1;
};
};
};
in file renames
2019-02-24 04:29:24 +00:00
buildConfigurationList = 58B511581A9E6B3D00147676 /* Build configuration list for PBXProject "RNCCameraRoll" */;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
compatibilityVersion = "Xcode 3.2";
developmentRegion = English;
hasScannedForEncodings = 0;
knownRegions = (
en,
);
mainGroup = 58B511541A9E6B3D00147676;
productRefGroup = 58B5115E1A9E6B3D00147676 /* Products */;
projectDirPath = "";
projectRoot = "";
targets = (
in file renames
2019-02-24 04:29:24 +00:00
58B5115C1A9E6B3D00147676 /* RNCCameraRoll */,
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
);
};
/* End PBXProject section */
/* Begin PBXSourcesBuildPhase section */
58B511591A9E6B3D00147676 /* Sources */ = {
isa = PBXSourcesBuildPhase;
buildActionMask = 2147483647;
files = (
fix iOS library file reference
2019-02-24 05:48:37 +00:00
4F788CB822226740001DB9D2 /* RNCAssetsLibraryRequestHandler.m in Sources */,
in file renames
2019-02-24 04:29:24 +00:00
143879351AAD238D00F088A5 /* RNCCameraRollManager.m in Sources */,
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
);
runOnlyForDeploymentPostprocessing = 0;
};
/* End PBXSourcesBuildPhase section */
/* Begin XCBuildConfiguration section */
58B5116F1A9E6B3D00147676 /* 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;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_BLOCK_CAPTURE_AUTORELEASING = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_BOOL_CONVERSION = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_COMMA = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_CONSTANT_CONVERSION = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_DEPRECATED_OBJC_IMPLEMENTATIONS = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_DIRECT_OBJC_ISA_USAGE = YES_ERROR;
CLANG_WARN_EMPTY_BODY = YES;
CLANG_WARN_ENUM_CONVERSION = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_INFINITE_RECURSION = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_INT_CONVERSION = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_NON_LITERAL_NULL_CONVERSION = YES;
Enable -Wimplicit-retain-self en sync warning config for all projects Summary: This is enforced for all of our internal iOS code and a common cause of import failures. cc janicduplessis Closes https://github.com/facebook/react-native/pull/13124 Differential Revision: D4765016 fbshipit-source-id: 7c8248c98bca0fa6bad24d5a52b666243375e0db
2017-03-23 21:58:20 +00:00
CLANG_WARN_OBJC_IMPLICIT_RETAIN_SELF = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_OBJC_LITERAL_CONVERSION = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_RANGE_LOOP_ANALYSIS = YES;
CLANG_WARN_STRICT_PROTOTYPES = YES;
CLANG_WARN_SUSPICIOUS_MOVE = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_UNREACHABLE_CODE = YES;
CLANG_WARN__DUPLICATE_METHOD_MATCH = YES;
COPY_PHASE_STRIP = NO;
ENABLE_STRICT_OBJC_MSGSEND = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
ENABLE_TESTABILITY = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
GCC_C_LANGUAGE_STANDARD = gnu99;
GCC_DYNAMIC_NO_PIC = NO;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
GCC_NO_COMMON_BLOCKS = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +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_INITIALIZER_NOT_FULLY_BRACKETED = YES;
GCC_WARN_SHADOW = YES;
GCC_WARN_UNDECLARED_SELECTOR = YES;
GCC_WARN_UNINITIALIZED_AUTOS = YES_AGGRESSIVE;
GCC_WARN_UNUSED_FUNCTION = YES;
GCC_WARN_UNUSED_VARIABLE = YES;
iOS OSS: deployment target 8.0 => 9.0 Summary: Moving target deployment to iOS 9.0+ from now on, removing customization for iOS 8. Reviewed By: shergin Differential Revision: D8053439 fbshipit-source-id: 292c58f15c6e6caf8b28d15c1521812d6ed675c5
2018-05-22 08:08:20 +00:00
IPHONEOS_DEPLOYMENT_TARGET = 9.0;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
MTL_ENABLE_DEBUG_INFO = YES;
ONLY_ACTIVE_ARCH = YES;
SDKROOT = iphoneos;
Redo exported headers and include paths for opensource Summary: Xcode really sucks, per some discussion on https://github.com/facebook/react-native/commit/e1577df1fd70049ce7f288f91f6e2b18d512ff4d and https://developer.apple.com/library/content/technotes/tn2215/_index.html, if you use the headers phase, and mark headers in your static library as public, they will actually end up in the final package that's built and you can't submit to the app store! This changes our xcode setup to use a copy files phase instead. I've also changed the header include path to be $(BUILT_PRODUCTS_DIR)/include, which is added to the include path by Xcode by default, so 3rd party libraries should not be impacted by these changes anymore. Reviewed By: mkonicek Differential Revision: D4291607 fbshipit-source-id: 969b9ebcbeb8161f85427f8c429e198d9d0fae30
2016-12-07 23:26:21 +00:00
SKIP_INSTALL = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
WARNING_CFLAGS = (
"-Werror",
"-Wall",
iOS: disable deprecation warning for Xcode 9.3.1+ for now Summary: This is to unbreak builds due to deprecated methods. Cocoapods build seems unaffected. Reviewed By: mmmulani Differential Revision: D8060139 fbshipit-source-id: a4302d649dd75d29d293aeffdcc352bf09b0c504
2018-05-22 08:08:22 +00:00
"-Wno-deprecated-declarations",
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
);
};
name = Debug;
};
58B511701A9E6B3D00147676 /* 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;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_BLOCK_CAPTURE_AUTORELEASING = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_BOOL_CONVERSION = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_COMMA = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_CONSTANT_CONVERSION = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_DEPRECATED_OBJC_IMPLEMENTATIONS = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_DIRECT_OBJC_ISA_USAGE = YES_ERROR;
CLANG_WARN_EMPTY_BODY = YES;
CLANG_WARN_ENUM_CONVERSION = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_INFINITE_RECURSION = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_INT_CONVERSION = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_NON_LITERAL_NULL_CONVERSION = YES;
Enable -Wimplicit-retain-self en sync warning config for all projects Summary: This is enforced for all of our internal iOS code and a common cause of import failures. cc janicduplessis Closes https://github.com/facebook/react-native/pull/13124 Differential Revision: D4765016 fbshipit-source-id: 7c8248c98bca0fa6bad24d5a52b666243375e0db
2017-03-23 21:58:20 +00:00
CLANG_WARN_OBJC_IMPLICIT_RETAIN_SELF = YES;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_OBJC_LITERAL_CONVERSION = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_OBJC_ROOT_CLASS = YES_ERROR;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
CLANG_WARN_RANGE_LOOP_ANALYSIS = YES;
CLANG_WARN_STRICT_PROTOTYPES = YES;
CLANG_WARN_SUSPICIOUS_MOVE = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
CLANG_WARN_UNREACHABLE_CODE = YES;
CLANG_WARN__DUPLICATE_METHOD_MATCH = YES;
COPY_PHASE_STRIP = YES;
ENABLE_NS_ASSERTIONS = NO;
ENABLE_STRICT_OBJC_MSGSEND = YES;
GCC_C_LANGUAGE_STANDARD = gnu99;
Update Xcode projects (#19574) Summary: @public A few people have been complaining, including me, that when we compile a react native project, there are a lot of warnings from xcode, suggesting to update the project build settings to the new recommendations. I took the liberty to actually update the xcode projects, so we can finally have these gone, as well as replace some deprecated methods with the new suggested ones. [IOS] [MINOR] [Xcode] - updated the Xcode projects with the latest suggestions from Xcode 9.3, and replaced a few deprecated methods of iOS with their new replacements. Closes https://github.com/facebook/react-native/pull/19574 Reviewed By: shergin Differential Revision: D8530135 Pulled By: hramos fbshipit-source-id: b9c9ede0e07760cb2207caa6b468bd5c241848dc
2018-06-20 06:43:39 +00:00
GCC_NO_COMMON_BLOCKS = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
GCC_WARN_64_TO_32_BIT_CONVERSION = YES;
GCC_WARN_ABOUT_RETURN_TYPE = YES_ERROR;
GCC_WARN_INITIALIZER_NOT_FULLY_BRACKETED = YES;
GCC_WARN_SHADOW = YES;
GCC_WARN_UNDECLARED_SELECTOR = YES;
GCC_WARN_UNINITIALIZED_AUTOS = YES_AGGRESSIVE;
GCC_WARN_UNUSED_FUNCTION = YES;
GCC_WARN_UNUSED_VARIABLE = YES;
iOS OSS: deployment target 8.0 => 9.0 Summary: Moving target deployment to iOS 9.0+ from now on, removing customization for iOS 8. Reviewed By: shergin Differential Revision: D8053439 fbshipit-source-id: 292c58f15c6e6caf8b28d15c1521812d6ed675c5
2018-05-22 08:08:20 +00:00
IPHONEOS_DEPLOYMENT_TARGET = 9.0;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
MTL_ENABLE_DEBUG_INFO = NO;
SDKROOT = iphoneos;
Redo exported headers and include paths for opensource Summary: Xcode really sucks, per some discussion on https://github.com/facebook/react-native/commit/e1577df1fd70049ce7f288f91f6e2b18d512ff4d and https://developer.apple.com/library/content/technotes/tn2215/_index.html, if you use the headers phase, and mark headers in your static library as public, they will actually end up in the final package that's built and you can't submit to the app store! This changes our xcode setup to use a copy files phase instead. I've also changed the header include path to be $(BUILT_PRODUCTS_DIR)/include, which is added to the include path by Xcode by default, so 3rd party libraries should not be impacted by these changes anymore. Reviewed By: mkonicek Differential Revision: D4291607 fbshipit-source-id: 969b9ebcbeb8161f85427f8c429e198d9d0fae30
2016-12-07 23:26:21 +00:00
SKIP_INSTALL = YES;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
VALIDATE_PRODUCT = YES;
WARNING_CFLAGS = (
"-Werror",
"-Wall",
iOS: disable deprecation warning for Xcode 9.3.1+ for now Summary: This is to unbreak builds due to deprecated methods. Cocoapods build seems unaffected. Reviewed By: mmmulani Differential Revision: D8060139 fbshipit-source-id: a4302d649dd75d29d293aeffdcc352bf09b0c504
2018-05-22 08:08:22 +00:00
"-Wno-deprecated-declarations",
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
);
};
name = Release;
};
58B511721A9E6B3D00147676 /* Debug */ = {
isa = XCBuildConfiguration;
buildSettings = {
CLANG_STATIC_ANALYZER_MODE = deep;
iOS: disable deprecation warning for Xcode 9.3.1+ for now Summary: This is to unbreak builds due to deprecated methods. Cocoapods build seems unaffected. Reviewed By: mmmulani Differential Revision: D8060139 fbshipit-source-id: a4302d649dd75d29d293aeffdcc352bf09b0c504
2018-05-22 08:08:22 +00:00
LIBRARY_SEARCH_PATHS = "$(inherited)";
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
OTHER_LDFLAGS = "-ObjC";
in file renames
2019-02-24 04:29:24 +00:00
PRODUCT_NAME = RNCCameraRoll;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
RUN_CLANG_STATIC_ANALYZER = YES;
};
name = Debug;
};
58B511731A9E6B3D00147676 /* Release */ = {
isa = XCBuildConfiguration;
buildSettings = {
CLANG_STATIC_ANALYZER_MODE = deep;
iOS: disable deprecation warning for Xcode 9.3.1+ for now Summary: This is to unbreak builds due to deprecated methods. Cocoapods build seems unaffected. Reviewed By: mmmulani Differential Revision: D8060139 fbshipit-source-id: a4302d649dd75d29d293aeffdcc352bf09b0c504
2018-05-22 08:08:22 +00:00
LIBRARY_SEARCH_PATHS = "$(inherited)";
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
OTHER_LDFLAGS = "-ObjC";
in file renames
2019-02-24 04:29:24 +00:00
PRODUCT_NAME = RNCCameraRoll;
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
RUN_CLANG_STATIC_ANALYZER = NO;
};
name = Release;
};
/* End XCBuildConfiguration section */
/* Begin XCConfigurationList section */
in file renames
2019-02-24 04:29:24 +00:00
58B511581A9E6B3D00147676 /* Build configuration list for PBXProject "RNCCameraRoll" */ = {
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
isa = XCConfigurationList;
buildConfigurations = (
58B5116F1A9E6B3D00147676 /* Debug */,
58B511701A9E6B3D00147676 /* Release */,
);
defaultConfigurationIsVisible = 0;
defaultConfigurationName = Release;
};
in file renames
2019-02-24 04:29:24 +00:00
58B511711A9E6B3D00147676 /* Build configuration list for PBXNativeTarget "RNCCameraRoll" */ = {
Moved CameraRoll-related classes into CameraRoll folder instead of Image Summary: The CameraRoll-related APIs were mixed in with the Image classes due to legacy coupling issues. Now that the APIs have been decoupled, it makes more sense for the CameraRoll classes to live in a separate library. This will be a breaking change for apps using the CameraRoll or related APIs. Fix is to add the RCTCameraRoll lib to your project.
2015-09-08 15:58:13 +00:00
isa = XCConfigurationList;
buildConfigurations = (
58B511721A9E6B3D00147676 /* Debug */,
58B511731A9E6B3D00147676 /* Release */,
);
defaultConfigurationIsVisible = 0;
defaultConfigurationName = Release;
};
/* End XCConfigurationList section */
};
rootObject = 58B511551A9E6B3D00147676 /* Project object */;
}