Skip to content

import of module 'glog.glog.log_severity' appears within namespace 'google' #26217

Closed

Description

@kovacs-tamas

I've faced with the following problem (google/glog#393)
Using RN for an SDK, created a pod file. The pod install works well, but during the xcode's build process i get the following error message.

Screenshot at Aug 27 14-43-57

I assume the problem caused by the swift 5.x version, i've never met this error before.

Environment

React Native version:
react-native-cli: 2.0.1
react-native: 0.60.5
pod version: 1.8.0.beta.1
osx 10.15 Beta (19A536g)
Xcode 11.0 beta 5 (11M382q)
Toolchain: Swift 5.1 Snapshot 2019-07-25 (a)

My pod file

source 'https://github.com/CocoaPods/Specs.git'
source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '9.0'
use_frameworks!

target 'XXXXX' do

  pod 'React', :path => '../../js/node_modules/react-native/'
  pod 'React-Core', :path => '../../js/node_modules/react-native/React'
  pod 'React-DevSupport', :path => '../../js/node_modules/react-native/React'
  pod 'React-RCTText', :path => '../../js/node_modules/react-native/Libraries/Text'
  pod 'React-RCTImage', :path => '../../js/node_modules/react-native/Libraries/Image'
  pod 'React-RCTNetwork', :path => '../../js/node_modules/react-native/Libraries/Network'
  pod 'React-RCTWebSocket', :path => '../../js/node_modules/react-native/Libraries/WebSocket'
  pod 'React-RCTLinking', :path => '../../js/node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTAnimation', :path => '../../js/node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../../js/node_modules/react-native/Libraries/Blob'
  pod 'React-RCTLinking', :path => '../../js/node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTActionSheet', :path => '../../js/node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTSettings', :path => '../../js/node_modules/react-native/Libraries/Settings'
  pod 'React-RCTVibration', :path => '../../js/node_modules/react-native/Libraries/Vibration'
  pod 'React-cxxreact', :path => '../../js/node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../../js/node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../../js/node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../../js/node_modules/react-native/ReactCommon/jsinspector'

  pod 'DoubleConversion', :podspec => '../../js/node_modules/react-native/third-party-podspecs/DoubleConversion.podspec', :modular_headers => false
  pod 'glog', :podspec => '../../js/node_modules/react-native/third-party-podspecs/glog.podspec', :modular_headers => false
  pod 'Folly', :podspec => '../../js/node_modules/react-native/third-party-podspecs/Folly.podspec', :modular_headers => false

  pod 'yoga', :path => '../../js/node_modules/react-native/ReactCommon/yoga'
  pod 'react-native-camera', subspecs: ['RCT', 'RN'], path: '../../js/node_modules/react-native-camera'
  pod 'react-native-image-picker', :path => '../../js/node_modules/react-native-image-picker'
  pod 'rn-fetch-blob', :path => '../../js/node_modules/rn-fetch-blob'
  pod 'react-native-image-resizer', :path => '../../js/node_modules/react-native-image-resizer'
  pod 'react-native-orientation', :path => '../../js/node_modules/react-native-orientation'
  pod 'RNDeviceInfo', :path => '../../js/node_modules/react-native-device-info'
  pod 'RNGestureHandler', :path => '../../js/node_modules/react-native-gesture-handler'
end

Activity

  1. ex3ndr commented on Sep 6, 2019

    @ex3ndr

    Same on non-beta XCode 10.3 and 0.61.rc-2

  2. ZeroOnet commented on Sep 10, 2019

    @ZeroOnet

    Same on 0.59.10 release? 😢

  3. ZeroOnet commented on Sep 10, 2019

    @ZeroOnet

    Same on 0.59.10 release? 😢

    Meanwhile, I need to use use_modular_headers!

  4. RZzero commented on Sep 13, 2019

    @RZzero

    Same issue here.

  5. intoxicated commented on Sep 17, 2019

    @intoxicated

    Same here. Tried to upgrade from 0.57.x to 60.x

  6. RZzero commented on Sep 17, 2019

    @RZzero

    In my case I unlinked all libraries with react-native unlink and added all to pods one by one to solve the issue.

  7. h2soheili commented on Sep 23, 2019

    @h2soheili

    Same on 0.59.10 release? 😢

    Meanwhile, I need to use use_modular_headers!

    i use_modular_headers! . due to lottie-react-native/lottie-react-native#511

  8. h2soheili commented on Sep 23, 2019

    @h2soheili

    In my case I unlinked all libraries with react-native unlink and added all to pods one by one to solve the issue.

    not worked . do you commented use_modular_headers! ?
    by commenting this ,i face with

    The following Swift pods cannot yet be integrated as static libraries:
    
    The Swift pod `lottie-react-native` depends upon `React`, which does not define modules.
    To opt into those targets generating module maps (which is necessary to import them from Swift 
    when building as static libraries), you may set `use_modular_headers!` globally 
    in your Podfile, or specify `:modular_headers => true` for particular dependencies.
    
    "react": "16.8.3",
    "react-native": "0.59.10",
    "lottie-ios": "^3.0.3",
    "lottie-react-native": "^3.1.1",
    
  9. czxtm commented on Sep 27, 2019

    @czxtm

    This solved it for me using use_modular_headers!:

    pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec', :modular_headers => false
    pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec', :modular_headers => false
    
  10. sickerin commented on Dec 18, 2019

    @sickerin

    Same on 0.59.10 release? 😢

    Meanwhile, I need to use use_modular_headers!

    i use_modular_headers! . due to react-native-community/lottie-react-native#511

    I'm in the exact position as you, did you solve it?

  11. stale commented on Mar 17, 2020

    @stale

    Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

  12. added
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Mar 17, 2020
  13. stale commented on Mar 24, 2020

    @stale

    Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

  14. locked as resolved and limited conversation to collaborators on Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugStaleThere has been a lack of activity on this issue and it may be closed soon.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions