9c2a5cdbc3
Update documentation for PermissionsAndroid
...
Summary:
<!--
Thank you for sending the PR! We appreciate you spending the time to work on these changes.
Help us understand your motivation by explaining why you decided to make this change.
You can learn more about contributing to React Native here: http://facebook.github.io/react-native/docs/contributing.html
Happy contributing!
-->
Current documentation: [https://facebook.github.io/react-native/docs/permissionsandroid.html ](https://facebook.github.io/react-native/docs/permissionsandroid.html )
PermissionsAndroid must be imported for the example to work, otherwise the error "Reference Error: can't find variable PermissionsAndroid" will be shown.
https://stackoverflow.com/questions/42434124/why-permissionandroid-doesnt-work
None - Just documentation changes.
Closes https://github.com/facebook/react-native/pull/15505
Differential Revision: D5643004
Pulled By: TheSavior
fbshipit-source-id: 5ed81fd0120270da9ab180dd3f1cb569544e0520
2017-08-16 15:01:51 -07:00
0c9b41f2c0
Include Create React Native App in Getting Started
...
Summary:
cc hramos
Create React Native App was designed to reduce "time to hello world" to 5-10 minutes for React Native apps. This PR would make CRNA the first way to get started that new users encounter. Included also is some text to help advanced users navigate the question of whether to use CRNA or whether to go straight to `react-native init`. It also includes a new banner for the iOS and Android guides, since they do not apply to CRNA users.
Changes are only to the website, screenshots below. This branch was created from the last CI-passing master commit this morning, dependencies were freshly installed and these screenshots are from a clean build.
[The Getting Started page](https://www.dropbox.com/s/1s7f3wu3oxr6gpo/Screenshot%202017-04-04%2015.12.29.png?dl=0 )
[The "native builds only" banner](https://www.dropbox.com/s/nyv51xdiibdkn57/Screenshot%202017-04-04%2015.13.25.png?dl=0 )
[Pages which still apply to CRNApps have no banner](https://www.dropbox.com/s/qgl0h6uzynqkmy2/Screenshot%202017-04-04%2015.14.10.png?dl=0 )
<details>
* [x] Decide how to handle native code & react-native-cli references outside of the `banner: ejected` guides
* [x] [Debugging: Accessing Console Logs](https://facebook.github.io/react-native/docs/debugging.html#accessing-console-logs ) isn't needed in CRNA (logs are forwarded alongside packager output)
* [x] [Debugging: With Stetho](https://facebook.github.io/react-native/docs/debugging.html#debugging-with-stetho-http-facebook-github-io-stetho-on-android ) requires native code
* [x] [Debugging: Debugging Native Code](https://facebook.github.io/react-native/docs/debugging.html#debugging-native-code ) is native-only
* [x] [AppRegistry](https://facebook.github.io/react-native/docs/appregistry.html ) only applies to ejected apps, since this is generated from code, I don't think we can set `banner: ejected`?
* [x] [Linking](https://facebook.github.io/react-native/docs/linking.html ) involves changing Android manifests and other native-side things
* [x] [PermissionsAndroid](https://facebook.github.io/react-native/docs/permissionsandroid.html ) may be flaky in the Expo client, I can't recall (cc jesseruder)
* [x] [PushNotificationIOS](https://facebook.github.io/react-native/docs/pushnotificationios.html ) won't work inside Expo, as it has to [handle its own push notifs](https://docs.expo.io/versions/v15.0.0/guides/push-notifications.html )
* [x] [Geolocation](https://facebook.github.io/react-native/docs/geolocation.html ) requires a polyfill that will most likely ship with next week's release, but that won't have any manifest changes necessary
* [ ] Figure out a strategy to handle the fact that CRNA will lag stable RN releases by ~1 week
* [x] Confirm linking out to CRNA docs is an OK strategy as opposed to moving ejecting, etc. docs in-tree
* [ ] Answer questions (I'll add some review comments to call out a few things)
</details>
Closes https://github.com/facebook/react-native/pull/13303
Differential Revision: D4950661
Pulled By: hramos
fbshipit-source-id: 3dd43828f38ca6ede3f2b0683608c56420dc6525
2017-04-26 07:16:18 -07:00
1fa95ed390
inline a bunch of NativeModule requires
...
Reviewed By: shergin
Differential Revision: D4578180
fbshipit-source-id: 3764ffd32eb7e4698e928740bc72bbad02876894
2017-02-17 16:49:38 -08:00
9338fbd781
Update PermissionsAndroid docs to use new APIs
...
Summary:
It seems that the `requestPermission` and `checkPermission` APIs from PermissionsAndroid have been deprecated in react-native 0.40.0., but they are still used in the description and example.
This commit updates the description and the example to use the new APIs.
Closes https://github.com/facebook/react-native/pull/11722
Differential Revision: D4392031
Pulled By: ericvicenti
fbshipit-source-id: e3ceebb1ef557e05dab40bb883013be4ec80bed6
2017-01-09 00:43:31 -08:00
51efaab120
Handle "Never Ask Again" in permissions and add requestMultiplePermissions
...
Summary:
In order to get featured in the Google Play Store, we had to handle a few specific cases with permissions based on feedback from the editorial team.
First, which was previously possible with this permissions module was bumping the sdk to version 23.
The second is requesting multiple permissions at one time. In order for the camera + upload to work, we needed to request both camera permissions + media storage in one flow.
The last is handling the case where the user checks the "Never Ask Again" box. This will only appear after a user denies a permission once and is then prompted again. The logic for handling this case is taken from here: http://stackoverflow.com/questions/31928868/how-do-we-distinguish-never-asked-from-stop-asking-in-android-ms-runtime-permis/35495372#35495372
We were also seeing a few crashes similar to #10009 due to `onRequestPermissionsResult` being called before `onResume` (http://stackoverflow.com/questions/35205643/why-is-onresume-called-after-onrequestpermissionsresult ), so I delaye
Closes https://github.com/facebook/react-native/pull/10221
Differential Revision: D4232551
fbshipit-source-id: fee698d1c48a2d86623cb87996f3d17f4c10a62e
2016-11-24 22:43:28 -08:00
74c32e2609
Docs fix: remove confusing typo
...
Summary:
Explain the **motivation** for making this change. What existing problem does the pull request solve?
Copy&paste from the example in the documentation will cause exception because there is no `AndroidPermissions` object. To avoid confusion we should refer to `PermissionsAndroid` instead since this is how this module is named in the API.
Closes https://github.com/facebook/react-native/pull/9956
Differential Revision: D3889080
Pulled By: hramos
fbshipit-source-id: 8f30d8f51ffee1321088a16a1b454ab163a746a2
2016-09-19 14:46:12 -07:00
6df41d5184
Change Android Permission Module to use promises
...
Summary:
This is a follow-up to #9292 satya164
Closes https://github.com/facebook/react-native/pull/9325
Differential Revision: D3723568
fbshipit-source-id: d553a70bde53ed5d7c1f5f544c85c5c5935e3ca4
2016-08-16 12:58:39 -07:00
0fb2ccfcc3
Add JS library for requesting Android M Permissions
...
Summary:
Explain the **motivation** for making this change. What existing problem does the pull request solve?
The Android permissions native module was open sourced recently (b7352b4667https://github.com/facebook/react-native/pull/9292
Differential Revision: D3716303
Pulled By: andreicoman11
fbshipit-source-id: cd40b8757fdf70ea8faecfb58caa00e99a99789e
2016-08-15 05:58:33 -07:00
Phạm Huy Hoàng
Adam Perry
Aaron Chiu
Peter Juras
Connor McEwen
Stanisław Wasiutyński
