Move Android and iOS folders.

[DylanVann]

This is a breaking change.

I think this should be done to:

• Use a more standard React Native package directory structure.
• Reduce complexity (no postinstall).
• Reduce the probability of issues related to automatic linking and symlinking.

See: #12 (comment)

There are also several other open issues related to symlinks.

[markhu]

As someone unfamiliar with .podspec I had to check at https://guides.cocoapods.org/syntax/podspec.html to assure myself that these curly braces weren't a problem here.

[DylanVann]

Yeah, other project actually tend to use ios/**/*.{h,m}.

[jsispal]

Thanks @DylanVann - this fixes the build issues (local and automated). Would be great to get this PR merged in 👍

[f0rr0]

can this be merged? @markhu @rjpizarro

[DylanVann]

I suppose someone has to step up and ask to be a maintainer. I would be willing to say I'd merge a couple things, publish the package, and not break anything, but I couldn't commit to being highly available to work on this, especially considering I think react-native-reanimated will potentially supercede this package.

[evanjmg]

Please merge this to fix symlinks

[mnlbox]

Please merge this as soon as possible. I'm using wix-ui-lib and can't assembleRelease because of this error:

FAILURE: Build failed with an exception.

* What went wrong:
Failed to capture snapshot of input files for task ':app:bundleReleaseJsAndAssets' property '$1' during up-to-date check.
> Could not list contents of '/home/myusername/myprojects/node_modules/react-native-interactable/{ios,android}'. Couldn't follow symbolic link.

[traxx10]

Am also getting the same issue

[xkrsz]

We're also experiencing this issue:

Could not list contents of '...react-native-interactable...'. Couldn't follow symbolic link.

[HarishJangra]

Build Succesful with these changes

[rotemmiz]

I am closing the PR as a part of an effort to cleanup and revive the project. If this issue persists after v1.0.0, you are more than welcome to reintroduce the PR.

Thanks for your contribution.

[DylanVann]

I don't think closing PRs that fix persistent issues and make setup easier for people is a good way to go about "reviving the project".

I won't be reintroducing the PR.

[rotemmiz]

No need to reintroduce the PR, this is already solved in v1.0.0-alpha.1
https://www.npmjs.com/package/react-native-interactable/v/1.0.0-alpha.1

V1 is coming soon

[DylanVann]

Yeah I saw that, although you didn't mention it here. I understand closing PRs if you have merged another superior fix, but just closing PRs to "cleanup the project" strikes me as inconsiderate.

You may want to check that react-native link works well with whatever fix you implemented.

[rotemmiz]

The project was not maintained for more than a year, simply because we couldn't find time for it, and no maintainer jumped on the opportunity. The repo was even left out of Wix's apps, and we wanted it back in.
There were close to a hundred open issues and PRs and we simply couldn't handle all of those individualy.

We want to create quality open source projects, and community around it as well, I hope you didn't take this personally as it surely wasn't our intention to dismiss the work done by you or anyone else from the community.

Regarding your comment re link, we will, thanks!

[DylanVann]

Trust me I can understand wanting to close all open issues and PRs on a project. I would resist the urge though, because people put time and effort into reporting issues and trying to make contributions.

I'm definitely guilty of ignoring PRs and issues, but I'd favor that over closing them without giving a reason. Anyways, no hard feelings, open source is hard 🤷‍♂️