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
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/includes/best-practices-native.md
+24-16Lines changed: 24 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,29 +17,40 @@ This section provides information about best practices associated with the Azure
17
17
18
18
## Supported platforms
19
19
20
-
### Android Calling SDK support
20
+
These are the minimum OS requirements for each platform to ensure optimal functionality of the Calling Native SDKs.
21
21
22
-
- Support for Android API Level 21 or Higher.
23
-
- Support for Java 7 or higher.
24
-
- Support for Android Studio 2.0.
25
-
-**Android Auto** and **IoT devices running Android** are currently not supported.
26
-
27
-
### iOS Calling SDK support
22
+
# [iOS](#tab/ios)
28
23
29
24
- Support for iOS 10.0+ at build time, and iOS 12.0+ at run time.
30
25
- Xcode 12.0+.
31
26
- Support for **iPadOS** 13.0+.
32
27
33
-
### Windows SDK
28
+
# [Android](#tab/android)
29
+
30
+
- Support for Android API Level 21 or Higher.
31
+
- Support for Java 7 or higher.
32
+
- Support for Android Studio 2.0.
33
+
-**Android Auto** and **IoT devices running Android** are currently not supported.
34
+
35
+
# [Windows](#tab/windows)
34
36
35
37
- Support for UWP (Universal Windows Platform).
36
38
- Support for WinUI 3.
37
39
40
+
---
41
+
38
42
## App request device permissions
39
43
40
-
### Android permission
44
+
To use the Calling Native SDKs for making or receiving calls, it's necessary to authorize each platform to access device resources. As a developer, you should prompt the user for access and ensure that it is enabled. The consumer will authorize these access rights, so it's important to verify that they have been granted permission previously.
45
+
46
+
# [iOS](#tab/ios)
47
+
48
+
-`NSMicrophoneUsageDescription` for microphone access.
49
+
-`NSCameraUsageDescription` for camera access.
50
+
51
+
# [Android](#tab/android)
41
52
42
-
In order to request permissions required to make a call, they must be declared in the Application Manifest (`app/src/main/AndroidManifest.xml`). Replace the content of file with the following code:
53
+
In the Application Manifest (`app/src/main/AndroidManifest.xml`). Replace the content of file with the following code:
-`NSMicrophoneUsageDescription` for microphone access.
58
-
-`NSCameraUsageDescription` for camera access.
59
-
60
-
### Windows permissions
66
+
# [Windows](#tab/windows)
61
67
62
68
Go to `Package.appxmanifest` and select capabilities:
63
69
64
70
-`Internet (Client)` & `Internet (Client & Server)` for network access.
65
71
-`Microphone` to access the audio feed of the microphone.
66
72
-`Webcam` to access the video feed of the camera.
67
73
74
+
---
75
+
68
76
## Configure the logs
69
77
70
78
Implementing **logging** as per the [logs file retrieval tutorial](../../tutorials/log-file-retrieval-tutorial.md) is more critical than ever. Detailed logs help in diagnosing issues specific to device models or OS versions that meet the minimum SDK criteria. We encourage to the developers that start configuring the Logs API without the logs the Microsoft Support team **won't be able** to help debug and troubleshoot the calls.
0 commit comments