Skip to content
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.

Project abandoned? #25

Open
geraintwhite opened this issue May 18, 2020 · 7 comments
Open

Project abandoned? #25

geraintwhite opened this issue May 18, 2020 · 7 comments

Comments

@geraintwhite
Copy link

There are a number of critical pull requests that need merging for this module to work properly (#13 and #20).

What can we do to get these merged @williambout and a new version released?

Perhaps the project needs more maintainers? I'm happy to help out and I'm sure others are too.

@geraintwhite
Copy link
Author

geraintwhite commented May 18, 2020

In the meantime I've published a fork including those two pull requests under @grit96/react-native-proximity.

@michaelhzh
Copy link

michaelhzh commented Jul 23, 2020

Sorry, I believe the previous issue has been resolved. However, I do have a new issue where when I try to use this application on IOS systems, during the pod install stage it keeps on giviing me the following error message telling me that podspec is nowhere to be found:
[!] No podspec found for @grit96 in ../node_modules/@grit96/react-native-proximity

My belief is that this is due to the naming convention for node_module file; however,I was unable to fix it after number of change.
I am wondering if you have encounter this before can might be able to provide me with some insights to how I can deal with it. Thanks!

@brianomchugh
Copy link

Sorry, I believe the previous issue has been resolved. However, I do have a new issue where when I try to use this application on IOS systems, during the pod install stage it keeps on giviing me the following error message telling me that podspec is nowhere to be found:
[!] No podspec found for @grit96 in ../node_modules/@grit96/react-native-proximity

My belief is that this is due to the naming convention for node_module file; however,I was unable to fix it after number of change.
I am wondering if you have encounter this before can might be able to provide me with some insights to how I can deal with it. Thanks!

Ever solve this?

@stephanoparaskeva
Copy link

There are a number of critical pull requests that need merging for this module to work properly (#13 and #20).

What can we do to get these merged @williambout and a new version released?

Perhaps the project needs more maintainers? I'm happy to help out and I'm sure others are too.

Hey Grit, there's some more PR's that need merging, particularly ones that relate to RN 0.6+ and IOS new version, related to autolinking issues etc

@williambout
Copy link
Owner

Hi all, for some reason I wasn't receiving email notifications from GitHub anymore.
I can't maintain this project unfortunately but I'm open to adding maintainers to make sure the library is compatible with the latest versions of React Native.

@stephanoparaskeva
Copy link

stephanoparaskeva commented Feb 22, 2021

Hi all, for some reason I wasn't receiving email notifications from GitHub anymore.
I can't maintain this project unfortunately but I'm open to adding maintainers to make sure the library is compatible with the latest versions of React Native.

Hey dude, can you do one final review and merge all remaining PR's, then I guess make myself and @grit96 maintainers so we can carry this on?

Also is there a chance we can have some small documentation on how to maintain, test, deploy this to npm?

@geraintwhite
Copy link
Author

I'm happy to help - a first step would be to get a new version published on npm and merge the critical PRs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants