Is airbnb still on this project?

[henrikra]

I feel like this library has been abandoned since the collaborators are not fixing even the critical bugs. There is 502 issues and 37 prs open. This is not normal. There are at least two very critical bugs caused this library to crash for many users. They are these: #271 #1227

Could you please tell if you are not going to do this project very often? If yes could you consider adding collaborators who are actually active and who do reviews prs and make new releases

[hrastnik]

It's gets worse... The official RN docs recommends this component since their MapView component is depracated and supports only iOS.

Source: https://facebook.github.io/react-native/docs/mapview.html

[tim-phillips]

A software engineer at airbnb committed to master 24 days ago.

https://github.com/airbnb/react-native-maps/commits/master

[henrikra]

@babenzele Yeah that is the problem :D

[tim-phillips]

What's the problem? 24 days too long for comfort? OSS projects don't fix themselves, take a dive in there and submit a PR.

[Exilz]

The problem is not the lack of commit for airbnb themselves. As you said, community can take care of this project and fix the most important stuff. We don't expect them to dedicate an employee's time adding feature to a community plugin.
As @henrikra said, the pull requests aren't supervised enough. Very interesting changes have been submitted ages ago and still nothing happened.

[tim-phillips]

Hmm, let's try get some good ones merged. Could you link some of the better ones?

[henrikra]

@babenzele All PR's related to crashes are priority one in my opinion. Since if the maps is crashing often the features does not matter :)

[tim-phillips]

Only one PR comes up when I search "crash" (#1273) and it was opened 5 days ago.

https://github.com/airbnb/react-native-maps/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aopen%20crash

[alreadysabbir]

Critical PR like #1249 #1193 #1226 #1200 is not yet merged!
Please add more collaborator at least!

[alreadysabbir]

Not even docs improvement PR 😞

[henrikra]

@babenzele For example #1287 this issue is making whole map crash on RN 0.44

[jeveloper]

@lelandrichardson Leland, would you consider moving the project to community or add collaborators . Thank you

[gshotwell]

+1

[Falconerd]

I was having huge issues getting this to work reliably across both platforms. I ended up using these versions:

react-native@0.42.3
react-native-maps@0.13.0

Hopefully that helps someone.

[kelset]

I have it working properly with RN 0.43, but can't figure out a way to make it work with 0.44.
I agree on the more collabs need.

(To give a glimmer of hope, a while back Leland told me that they were preparing a huge release for RNMaps but I can't find the tweet anymore)

[james2406]

It looks like a few commits were made to the master branch, which should fix the 0.44 issue 4b861c9

[felipecsl]

[Airbnb engineer here]
Indeed we're very resource constrained right now and have not given this library the attention it needs/deserves. I'll help triaging issues/PRs in the next couple days and we'll look into adding more contributors soon. Please bear with us in the meantime 😄

[jeveloper]

Thanks @felipecsl , appreciate you letting us know and thanks to AirBnB

btw , the current committs in the past 24 hours resolved a breaking problem for RN 44, any chance you can tag a version and push it up to npm , that would be great.

[felipecsl]

@christopherdro it seems like you already uploaded 0.15.0 to next 4 days ago? I just promoted that to latest!

[EricPKerr]

@felipecsl @lelandrichardson This deserves to have a much larger discussion, but I feel like this issue should be re-opened. There are a dozen issues that mention initialRegion,region, and onRegionChange alone, and they've become noticeably more problematic with onMapReady hacks all over the place.

This should be moved to react-native-community (or even RN core) so more people can openly contribute and make this better. It's too critical of a project to not have more active core members triaging Issues and Pull Requests.

[felipecsl]

@EricPKerr reopening this issue will not help with fixing those problems you mentioned. We're happy to add more contributors to the project and/or move it to a different org (eg.: react-native-community, as you suggested). If anyone is familiar with the code, is using it in production and is committed to maintaining/improving this, please step forward and we'll be happy to work with you to add as maintainers. If you prefer moving it, I can help with that too!

[alvelig]

@felipecsl ME! (stepping forward) At least iOS is familiar to me. And I am using it for production in several apps.

[felipecsl]

@alvelig the current plan is to move this repo to the react-community org. We're waiting on someone with enough permissions to help with that transition.