Skip to content

Commit 4631e57

Browse files
authored
Move enable native API callout as step (#2679)
1 parent 9dbc983 commit 4631e57

File tree

5 files changed

+18
-11
lines changed

5 files changed

+18
-11
lines changed
Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1 @@
1-
> [!IMPORTANT]
2-
> Ensure that the Native API is enabled to integrate Clerk in your native application. In the Clerk Dashboard, navigate to the [**Native Applications**](https://dashboard.clerk.com/last-active?path=/native-applications) page.
1+
In the Clerk Dashboard, navigate to the [**Native Applications**](https://dashboard.clerk.com/last-active?path=/native-applications) page and ensure that the Native API is enabled. This is required to integrate Clerk in your native application.

docs/getting-started/quickstart.android.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,11 @@ sdk: android
2020
]}
2121
/>
2222

23-
<Include src="_partials/native-api-callout" />
24-
2523
<Steps>
24+
## Enable Native API
25+
26+
<Include src="_partials/native-api-callout" />
27+
2628
## Create an Android Project
2729

2830
1. Create a new Android project in Android Studio using the **Empty Activity** template. This tutorial uses `MyClerkApp` as the app name. If you choose a different name, be sure to update any code examples accordingly to match your app's name.

docs/getting-started/quickstart.chrome-extension.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,11 @@ sdk: chrome-extension
2020
]}
2121
/>
2222

23-
<Include src="_partials/native-api-callout" />
24-
2523
<Steps>
24+
## Enable Native API
25+
26+
<Include src="_partials/native-api-callout" />
27+
2628
## Configure your authentication options
2729

2830
When creating your Clerk application in the Clerk Dashboard, your authentication options will depend on how you configure your Chrome Extension. Chrome Extensions can be used as a popup, a side panel, or in conjunction with a web app. Popups and side panels have limited authentication options. [Learn more about what options are available.](/docs/reference/chrome-extension/overview#authentication-options)

docs/getting-started/quickstart.expo.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,11 @@ sdk: expo
2525
]}
2626
/>
2727

28-
<Include src="_partials/native-api-callout" />
29-
3028
<Steps>
29+
## Enable Native API
30+
31+
<Include src="_partials/native-api-callout" />
32+
3133
## Install `@clerk/clerk-expo`
3234

3335
The [Clerk Expo SDK](/docs/reference/expo/overview) gives you access to prebuilt components, hooks, and helpers to make user authentication easier.

docs/getting-started/quickstart.ios.mdx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,11 @@ icon: "clerk",
1414
]}
1515
/>
1616

17-
<Include src="_partials/native-api-callout" />
18-
1917
<Steps>
18+
## Enable Native API
19+
20+
<Include src="_partials/native-api-callout" />
21+
2022
## Create an iOS Project
2123

2224
To get started using Clerk with iOS, create a new project in Xcode. Select SwiftUI as your interface and Swift as your language.
@@ -29,7 +31,7 @@ icon: "clerk",
2931

3032
## Add your Native Application
3133

32-
Add your iOS application to the [**Native Applications**](https://dashboard.clerk.com/last-active?path=/native-applications) page in the Clerk dashboard. You will need your iOS app's **App ID Prefix** and **Bundle ID**.
34+
Add your iOS application to the [**Native Applications**](https://dashboard.clerk.com/last-active?path=/native-applications) page in the Clerk Dashboard. You will need your iOS app's **App ID Prefix** and **Bundle ID**.
3335

3436
## Add associated domain capability
3537

0 commit comments

Comments
 (0)