|
|
@@ -107,7 +107,13 @@ Then update your `Info.plist` with wanted permissions usage descriptions:
|
|
107
|
107
|
|
|
108
|
108
|
1. Check that you linked **at least one** permission handler.
|
|
109
|
109
|
2. Clean up Xcode stale data with `npx react-native-clean-project --remove-iOS-build --remove-iOS-pods`
|
|
110
|
|
-3. If you use `use_frameworks!`, replace it by `use_modular_headers!` - see [this blog post](http://blog.cocoapods.org/CocoaPods-1.5.0) for more details
|
|
|
110
|
+3. If you use `use_frameworks!`, replace it by `use_modular_headers!` - see [this blog post](http://blog.cocoapods.org/CocoaPods-1.5.0) for more details. [Create empty Swift file in XCode](https://stackoverflow.com/questions/52536380/why-linker-link-static-libraries-with-errors-ios/56176956#56176956). Then add ":modular_headers => false" to Pods with build errors:
|
|
|
111
|
+
|
|
|
112
|
+```ruby
|
|
|
113
|
+pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec', :modular_headers => false
|
|
|
114
|
+pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec', :modular_headers => false
|
|
|
115
|
+```
|
|
|
116
|
+
|
|
111
|
117
|
4. If you use `use_frameworks!` but **can't** replace it with `use_modular_headers!`, check the following workaround:
|
|
112
|
118
|
|
|
113
|
119
|
```ruby
|
Mathieu Acthernoene
5 år sedan