Raviraj

Google has moved away from having same google play service version, I think if the google provided getCurrentLocation works more robust, I think its worth the change.

> I'll try implementing this. I'm currently rewriting the android implementation to add support for android's default location manager api if google play service is not available. You can check...

I feel a wrapper library cannot add all nuances of how the underlying library works and its best practices, then the readme will become too big, unreadable in a glance...

This issue occurs when you try to turn location tracking off/on when switching background/foreground with user not having proper location settings and option 'showLocationDialog' enabled.'showLocationDialog' itself fires appstate change affecting...

Yes, but I don't know where to solve this problem, inside lib or lib consumer. If inside lib then we have to provide some option for android like 'canTrackInBackground: true/false'....

Better we discuss the flow and api design before implementing.

The issue happens when you start using `showLocationDialog` and when this dialog shows it will trigger appState change, but we will never know. This will create lot of subtle issues...

@anastely Apple will only bundle swift core library on older versions of iOS and also only required files. The true size of the app downloaded can be found in TestFlight....

@pepibumur idea is pretty cool, but my concern is can a manifest file satisfy all use cases provided by Xcode and gradle like Build Settings, Build Phases, custom gradle tasks...

Use `display: 'inline'` for iOS this will show the picker directly on screen, now design your input fields the way you want, then onPress show this `DateTimePicker` in a modal...