Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: global.pokeSamplingProfiler is not a function when trying to open debugger #25142

Closed
range-of-motion opened this issue Jun 4, 2019 · 5 comments
Labels
Bug Platform: Linux Building on Linux. Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@range-of-motion
Copy link

React Native version:

  React Native Environment Info:
    System:
      OS: Linux 4.15 Ubuntu 18.04.2 LTS (Bionic Beaver)
      CPU: (4) x64 Intel(R) Core(TM) i5-6500T CPU @ 2.50GHz
      Memory: 443.54 MB / 15.53 GB
      Shell: 4.4.19 - /bin/bash
    Binaries:
      Node: 8.10.0 - /usr/bin/node
      Yarn: 1.16.0 - /usr/bin/yarn
      npm: 3.5.2 - /usr/bin/npm
    SDKs:
      Android SDK:
        API Levels: 22, 23, 26, 27, 28
        Build Tools: 28.0.3
        System Images: android-27 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.3 AI-182.5107.16.33.5264788
    npmPackages:
      react: 16.8.3 => 16.8.3 
      react-native: 0.59.1 => 0.59.1 

Steps To Reproduce

  1. Run my app
  2. Try to use remote debugger

Describe what you expected to happen:

Debugger should have opened. This happened instead.

Screenshot from 2019-06-04 14-27-47

@range-of-motion range-of-motion changed the title TypeError: global.pokeSamplingProfer is not a function when trying to open debugger TypeError: global.pokeSamplingProfiler is not a function when trying to open debugger Jun 4, 2019
@react-native-bot react-native-bot added the Platform: Linux Building on Linux. label Jun 4, 2019
@range-of-motion
Copy link
Author

FYI if anyone runs into this, clear your cache and try again.

@kaitlynbrown
Copy link

Clearing cache doesn't resolve the issue.

Also, even if clearing your cache were a workaround, this is still a major bug that needs to be addressed, so why is this issue closed?

@range-of-motion
Copy link
Author

Fuck do I know? I opened this issue, and then closed it because my issue got resolved. If it doesn't work for you, just re-open it and continue? I'm not stopping you 🤷‍♂

@stale
Copy link

stale bot commented Jan 27, 2020

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 stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Jan 27, 2020
@range-of-motion
Copy link
Author

Yeah this isn't an issue for me. As I said––clear cache, reinstall, and try again.

@facebook facebook locked as resolved and limited conversation to collaborators Jan 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Platform: Linux Building on Linux. Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

3 participants