Developer menu stop working after upgrade to "react-native": "0.57.8"

[ifyapishore]

Environment

React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: (4) x64 Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz
Memory: 30.45 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.6.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.5.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
IDEs:
Android Studio: 3.1 AI-173.4720617
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: 0.57.8 => 0.57.8
npmGlobalPackages:
react-native-cli: 2.0.1

Description

CMD-R and CMD-D stop working

Pods file
pod 'React', path: '../node_modules/react-native', :subspecs => [ 'Core', 'CxxBridge', 'RCTText', 'RCTNetwork', 'RCTWebSocket', # needed for debugging 'RCTImage', 'RCTNetwork', # Add any other subspecs you want to use in your project 'DevSupport' ]

Emulator iPhoneX, IOS 12.1

Reproducible Demo

upgrade to 0.57.8

[react-native-bot]

It looks like you are using an older version of React Native. Please update to the latest release, v0.58 and verify if the issue still exists.

The "⏪Old Version" label will be removed automatically once you edit your original post with the results of running react-native info on a project using the latest release.

[ifyapishore]

Excellent!

I spend two weeks to upgrade to 0.57.8, went through dependency hell and finally was able to make new build and now you are proposing to do it again?

I have no any guarantee that 0.58 will work at all.

[hramos]

I'm sorry you feel that way. This is an automated script that checks new issues to make sure we focus on the latest release, as to ensure the issue is something that is still actively affecting people who are on the latest version. That said, I'd be surprised if the dev menu did indeed get broken in 0.57.8, and so far I have not seen reports of this happening in 0.58.2.

[nol13]

Did you upgrade to xcode 10 at the same time? Had issue here where the keyboard shortcut for shake gesture wasn't working after xcode upgrade, but shake gesture from menu worked fine. It did mysteriously start working again shortly thereafter though. (wasn't on my comp but don't think he had to do anything special to fix, this is actually the one thing I use touchbar shortcuts for)

[gazedash]

@nol13 no, it doesnt work, I use Xcode 10 and react-native 0.57.8

Can confirm this issue is reproducible

It seems that if I use comment use_frameworks! in Podfile, dev menu works.
Although that doesn't solve the problem because I need Swift AND dev menu.

@ifyapishore if you have "use_frameworks!" line in Podfile, comment it out and see if it works...

[evang9410]

This is still occurring on 0.59.3 while using use_frameworks! in pod file.

[ifyapishore]

Confirmed!

…

On Tue, Apr 9, 2019, 01:10 Evan Glicakis ***@***.***> wrote: This is still occurring on 0.59.3 while using use_frameworks! in pod file. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#23174 (comment)>, or mute the thread <https:/notifications/unsubscribe-auth/AQO5Ycc1u-9NbE5_cNtxxWdxeCVVH-H5ks5ve4YsgaJpZM4aUsgN> .

[KingAmo]

@hramos the same problem，cannot open developer menu in anyway，react-native: 0.59.8，i have use_frameworks! in Podfile

• react native info

  React Native Environment Info:
    System:
      OS: macOS 10.14.5
      CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
      Memory: 47.24 MB / 8.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 12.3.1 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.9.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 23, 28
        Build Tools: 28.0.3
    IDEs:
      Android Studio: 3.4 AI-183.6156.11.34.5522156
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.8 => 0.59.8
    npmGlobalPackages:
      react-native-cli: 2.0.1

• Podfile

# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'ReactNativeAppDemo' do
  # Pods for ReactNativeAppDemo
  pod 'React', :path => '../node_modules/react-native', :subspecs => [
  'Core',
  'CxxBridge',
  'DevSupport',
  'RCTText',
  'RCTNetwork',
  'RCTWebSocket',
  'RCTAnimation'
  ]
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
  
  pod 'react-native-baidu-map', :podspec => '../node_modules/react-native-baidu-map/ios/react-native-baidu-map.podspec'
  
  pod 'AppCenter/Crashes', '~> 2.0.1'
  pod 'AppCenter/Analytics', '~> 2.0.1'
  pod 'AppCenterReactNativeShared', '~> 2.0.0'
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  
  

  platform :ios, '9.0'
  target 'ReactNativeAppDemoTests' do
    inherit! :search_paths
    # Pods for testing
  end

end

target 'ReactNativeAppDemo-tvOS' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  # Pods for ReactNativeAppDemo-tvOS

  target 'ReactNativeAppDemo-tvOSTests' do
    inherit! :search_paths
    # Pods for testing
  end

end

[KingAmo]

#20354

[KingAmo]

#19825

[KingAmo]

#13799

[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.

[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.