jeanregisser / react-native-popover

A <Popover /> component for react-native
660 stars 176 forks source link

Unable to resolve module StyleSheetRegistry #6

Open lintonye opened 9 years ago

lintonye commented 9 years ago

Similar to this, except that it's an error which causes the build in XCode to fail.

This error occurs as of React Native 0.14.2. It works with 0.13.2.

After commenting out the code that uses StyleSheetRegistry, you'll get another similar error regarding `Dimensions'.

harakhovich commented 9 years ago

Getting the same error.

jeanregisser commented 9 years ago

Thanks for reporting! I havent had the time to update it for RN 0.14 Feel free to send a PR, or I'll fix it in the coming week.

albertwchang commented 8 years ago

It seems the issue has been resolved by virtue of v0.3.0. However, this version is only available when cloning the repo, not NPM downloading...

tuneZola commented 8 years ago

+1 I am getting this error also.

wangdayewjf commented 8 years ago

+1 i have the same problem now

ericraio commented 8 years ago

@jeanregisser just needs to update NPM...

In this issue here https://github.com/jeanregisser/react-native-popover/issues/8, there is a remedy for this issue

ahmed1490 commented 8 years ago

+1

ashokseervidev commented 8 years ago

Hi All,

I am new to React-Native.

I am getting same error.

Can anyone explain me steps to resolve this issue.

"dependencies": {
      "react": "^15.0.2",
    "react-native": "^0.26.2",
    "react-native-popover": "^0.2.0",
  }

After Updating "react-native-popover": "^0.2.0" with "react-native-popover": "git+https://github.com/jeanregisser/react-native-popover.git" issue is resolved.

Thanks to @ericraio, @achang28 and @aforty.

After updating react-native-popover to V0.3.0 i am getting undefined is not an object("evaluating "PropTypes.bool") error.

Can any body help me to resolve this issue.

chrisciszak commented 8 years ago

+1

aforty commented 8 years ago

@agilityworks-uk's fork of this seems to be further along. I haven't tried it myself but we should probably all go concentrate dev efforts there.

https://github.com/agilityworks-uk/react-native-popover

duranmla commented 8 years ago

@aforty that is a better idea, I haven't seem too much participation of the owner recently and will be awesome if all of us contribute with this in a centric place. However, seems like agilitworks doesn't accept issues, so maybe it is not the right place to go don't you think?

ajoshdee commented 8 years ago

Question: How to have different message for different popovers in a view. I don't want my message to have only "content"

npomfret commented 8 years ago

How do i add agilityworks-uk version into package.json? I tried

"react-native-popover": "git://github.com/agilityworks-uk/react-native-popover.git#release\/2.2",

But its not correct. What's the syntax?

aforty commented 8 years ago
"@taw/react-native-popover": "git+https://github.com/agilityworks-uk/react-native-popover.git#release\/2.2",

or

npm i --save git+https://github.com/agilityworks-uk/react-native-popover.git#release\/2.2
npomfret commented 8 years ago

Thanks, I tried and still nothing. It's just not appearing in my node_modules dir. I see this after install:

├── @taw/react-native-popover@2.2.0  extraneous (git+https://github.com/agilityworks-uk/react-native-popover.git#eca65b548829fbc7e66ba2024da74b99ab7e7167)
└── UNMET PEER DEPENDENCY react-native@0.32.0

I'm using rn 0.32.0

npomfret commented 8 years ago

Ah, when I tried your second approach it did this (which worked)

"@taw/react-native-popover": "git+https://github.com/agilityworks-uk/react-native-popover.git#release/2.2",
Lokesh235 commented 7 years ago

I took the latest from git but still not working, getting unable to resolve StyleSheetRegistry error

npm i --save git+https://github.com/agilityworks-uk/react-native-popover.git#release/2.2

I am using react-native v0.33

YasirSherzad commented 7 years ago

@Lokesh235 you need to import like this

import Popover from ''@taw/react-native-popover''
yeomann commented 6 years ago

2018 and issue is still there waoo

yanko-ivanov commented 6 years ago

October and still going strong it seems. Just googled my way to this discussion. :D