fix: Pod install issue & listener conflict with document picker library

[rinku-k]

The pull request contains below fix -

1. Pod demo swift added - helps users to run 'pod install' inside the library directly
   iOS Error: Cant find Pods.xcodeproject and can't able to pod install too #23

2. Conflict with listener
   File-selector plugin is listening to document-picker file selection and throwing error causing app crash in some mobiles.

[prscX]

Thanks @Rinkuk1993 for the Effort and PR.

• w.r.t first point: the fix is for pod installation? Could you please share the exception which you were getting.

• second point: fix w.r.t conflict with listener looks good.

Thanks
</ Pranav >

[rinku-k]

For the first point -
You can check this thread #23
#28

Normally people are not able to do pod install inside the library due to unavailability of swift file.
They have to manually create one from Xcode(normally people don't know how to do it).
For reference - check my comment on the issue thread #23

This fix will simply remove unwanted confusion.

Thanks

[rinku-k]

Is there an issue merging the changes? I am not sure about the status of this PR since there is no response

[crutchcorn]

I get the following error for this PR for iOS usage:

[!] The `RNFileSelector` pod failed to validate due to 1 error:
    - ERROR | attributes: Missing required attribute `homepage`.
    - WARN  | source: The version should be included in the Git tag.
    - WARN  | description: The description is equal to the summary.

[crutchcorn]

All it took to solve this issue was to change the podspec file:

  s.homepage     = "https://github.com/prscX/react-native-file-selector"

Then the iOS issue was resolved

[rinku-k]

Conflict with listener
File-selector plugin is listening to document-picker file selection and throwing error causing app crash in some mobiles.

I see that someone has already added PR for the above fix due to my inactivity. Since the code is same, I have removed my code.

Pod demo swift added - helps users to run 'pod install' inside the library directly
#23

If issue #23 is also fixed in another PR, let's close or discard this one.