Skip to content

Commit d51a041

Browse files
committed
update monitoring and ranging md files
1 parent c65a3e2 commit d51a041

2 files changed

Lines changed: 8 additions & 5 deletions

File tree

examples/samples/monitoring.ios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ If you don't:
1717

1818
> For monitoring you don't have the choice you have to request `Always` authorization wether you need background mode or not.
1919
20-
[See matching lines in sample example]()
20+
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/monitoring.ios.js#L36)
2121

2222
### 1 `Beacons.requestAlwaysAuthorization();` (**background and foreground use-case**)
2323

examples/samples/ranging.ios.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,6 @@ If you don't:
1818
You can request 2 kind of authorizations depending on the use case:
1919
> Do you need background capability or not?
2020
21-
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L35)
2221

2322
### 1.a `Beacons.requestWhenInUseAuthorization();` (**foreground** only use-case)
2423

@@ -29,6 +28,8 @@ Ensure to call
2928
Beacons.requestWhenInUseAuthorization();
3029
```
3130

31+
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L35)
32+
3233
#### in your iOS project
3334

3435
To be effective your `info.plist` file should have `Privacy - Location When In Use Usage Description` key defined (*empty value or not. It is better to define a value to a custom / more user-friendly message*).
@@ -49,6 +50,8 @@ Ensure to call
4950
Beacons.requestAlwaysAuthorization();
5051
```
5152

53+
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L35)
54+
5255
#### in your iOS project
5356

5457
To be effective your `info.plist` file should have `Privacy - Location Always Usage Description` key defined (*empty value or not. It is better to define a value to a custom / more user-friendly message*).
@@ -72,7 +75,7 @@ const region = { identifier, uuid };
7275
Beacons.startRangingBeaconsInRegion(region);
7376
```
7477

75-
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L40)
78+
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L41)
7679

7780
## 3- register events
7881

@@ -105,7 +108,7 @@ Note: beacons is an array of object:
105108
}
106109
```
107110
108-
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L55)
111+
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L50)
109112
110113
111114
## 4- on componentWillUnMount: unregister events and stop ranging
@@ -121,4 +124,4 @@ Beacons.stopRangingBeaconsInRegion();
121124
DeviceEventEmitter.remove();
122125
```
123126
124-
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L64)
127+
[See matching lines in sample example](https://github.com/MacKentoch/react-native-beacons-manager/blob/master/examples/samples/ranging.ios.js#L61)

0 commit comments

Comments
 (0)