You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the deployment target bumped to 11.0, remove all @available
guards for macOS 10.16/11.0 and their else branches:
- ScreenAuthStatus: use CGPreflightScreenCaptureAccess directly
- AskForScreenCaptureAccess: remove CGDisplayStreamCreate fallback
- PhotosAuthStatus: always use authorizationStatusForAccessLevel:
- AskForPhotosAccess: always use requestAuthorizationForAccessLevel:
- MusicLibraryAuthStatus: always use SKCloudServiceController
- AskForMusicLibraryAccess: remove pre-11.0 authorized fallback
- Remove API_AVAILABLE annotations that are now always satisfied
Also remove outdated README notes about pre-11.0 behavior.
Copy file name to clipboardExpand all lines: README.md
-27Lines changed: 0 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,15 +75,6 @@ Return Value Descriptions:
75
75
-`limited` - The application is authorized for limited access to `type` data. Currently only applicable to the `photos` type.
76
76
- 'provisional' - The application is provisionally authorized to access `type` data. Currently only applicable to the `notifications` type.
77
77
78
-
**Notes:**
79
-
80
-
- Access to `bluetooth` will always return a status of `authorized` prior to macOS 10.15, as the underlying API was not introduced until that version.
81
-
- Access to `camera` and `microphone` will always return a status of `authorized` prior to macOS 10.14, as the underlying API was not introduced until that version.
82
-
- Access to `input-monitoring` will always return a status of `authorized` prior to macOS 10.15, as the underlying API was not introduced until that version.
83
-
- Access to `music-library` will always return a status of `authorized` prior to macOS 11.0, as the underlying API was not introduced until that version.
84
-
- Access to `screen` will always return a status of `authorized` prior to macOS 10.15, as the underlying API was not introduced until that version.
85
-
- Access to `speech-recognition` will always return a status of `authorized` prior to macOS 10.15, as the underlying API was not introduced until that version.
**Note:**`status` will be resolved back as `authorized` prior to macOS 10.15, as the underlying API was not introduced until that version.
228
-
229
218
### `permissions.askForRemindersAccess()`
230
219
231
220
Returns `Promise<String>` - Whether or not the request succeeded or failed; can be `authorized` or `denied`.
@@ -315,10 +304,6 @@ Your app must provide an explanation for its use of capture devices using the `N
315
304
<string>Your reason for wanting to access the Camera</string>
316
305
```
317
306
318
-
**Note:**
319
-
320
-
-`status` will be resolved back as `authorized` prior to macOS 10.14, as the underlying API was not introduced until that version.
321
-
322
307
Example:
323
308
324
309
```js
@@ -358,10 +343,6 @@ Checks the authorization status for input monitoring access. If the status check
358
343
-`not determined` - A dialog will be displayed directing the user to the `Security & Privacy` System Preferences window , where the user can approve your app to monitor keyboard events in the background. The Promise is resolved as `denied`.
359
344
-`denied` - The `Security & Privacy` System Preferences window is opened with the Input Monitoring privacy key highlighted. On open of the `Security & Privacy` window, the Promise is resolved as `denied`.
360
345
361
-
**Note:**
362
-
363
-
-`status` will be resolved back as `authorized` prior to macOS 10.15, as the underlying API was not introduced until that version.
364
-
365
346
Example:
366
347
367
348
```js
@@ -389,10 +370,6 @@ Your app must provide an explanation for its use of capture devices using the `N
389
370
<string>Your reason for wanting to access the Microphone</string>
390
371
```
391
372
392
-
**Note:**
393
-
394
-
-`status` will be resolved back as `authorized` prior to macOS 10.14, as the underlying API was not introduced until that version.
395
-
396
373
Example:
397
374
398
375
```js
@@ -418,10 +395,6 @@ Your app must provide an explanation for its use of the music library using the
418
395
<string>Your reason for wanting to access the user’s media library.</string>
419
396
```
420
397
421
-
**Note:**
422
-
423
-
-`status` will be resolved back as `authorized` prior to macOS 11.0, as the underlying API was not introduced until that version.
0 commit comments