Skip to content

Commit

Permalink
fixing broken links and bad redirects (#7469)
Browse files Browse the repository at this point in the history
* redirects

* added specificity

* redirects as of 5/1/24

* fix broken links found from screaming frog

* updated redirects

* fix

---------

Co-authored-by: katiegoines <katiegoines@gmail.com>
  • Loading branch information
katiegoines and katiegoines committed May 3, 2024
1 parent 590a3d5 commit dec20d3
Show file tree
Hide file tree
Showing 11 changed files with 9,781 additions and 20 deletions.
9,763 changes: 9,762 additions & 1 deletion redirects.json

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ This call sends information about the current user (which could be unauthenticat

You can provide `name`, `email` and `plan`, as well as location information with `AnalyticsUserProfile.Location`. You can also send additional custom attributes using `AnalyticsProperties`.

If the user is signed in through [Amplify.Auth.signIn](/[platform]/build-a-backend/auth/enable-sign-up/#sign-in), then you can retrieve the current user's ID as shown below:
If the user is signed in through [Amplify.Auth.signIn](/[platform]/build-a-backend/auth/connect-your-frontend/sign-in/), then you can retrieve the current user's ID as shown below:

```swift

Expand Down Expand Up @@ -253,7 +253,7 @@ This API sends information about the current user to Amazon Pinpoint.

Additional information such as the user's name, email, location, and device can be included by specifying the `UserProfile`. Custom attributes can also be included by setting `UserProfile.customProperties`.

If the user was signed in through [signIn](/[platform]/prev/build-a-backend/auth/enable-sign-up/) you can retrieve the current user's ID as shown below:
If the user was signed in through [signIn](/[platform]/build-a-backend/auth/connect-your-frontend/sign-up/) you can retrieve the current user's ID as shown below:

```js title="src/index.js"
import { identifyUser } from 'aws-amplify/analytics';
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ RxAmplify.Analytics.flushEvents();
</Block>
</BlockSwitcher>

When flushing events, a [Hub event](/[platform]/build-a-backend/utilities/hub/) is sent containing the events which were successfully sent to the Pinpoint service. To receive a list of these events, subscribe to the `HubChannel.ANALYTICS` channel and handle an event of the type `AnalyticsChannelEventName.FLUSH_EVENTS`.
When flushing events, a [Hub event](/[platform]/build-a-backend/auth/connect-your-frontend/listen-to-auth-events/) is sent containing the events which were successfully sent to the Pinpoint service. To receive a list of these events, subscribe to the `HubChannel.ANALYTICS` channel and handle an event of the type `AnalyticsChannelEventName.FLUSH_EVENTS`.

## Authentication events

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -414,7 +414,7 @@ framework may be used in order to display maps on macOS applications.

</Callout>

First, ensure you've provisioned an Amazon Location Service Map resource and configured your app using the instructions in either [Configure maps](/[platform]/build-a-backend/more-features/geo/configure-maps/) or [Use existing resources](/[platform]/build-a-backend/more-features/geo/existing-resources/) guide.
First, ensure you've provisioned an Amazon Location Service Map resource and configured your app using the instructions in either [Configure maps](/[platform]/build-a-backend/add-aws-services/geo/set-up-geo/) or [Use existing resources](/[platform]/build-a-backend/add-aws-services/geo/existing-resources/) guide.

Amplify-MapLibre is an open source adapter that enables the popular MapLibre SDK to work seamlessly with Amplify Geo.

Expand Down Expand Up @@ -679,7 +679,7 @@ Also, check the [official MapView API reference](https://docs.maptiler.com/mapli

## AmplifyMapView

The `AmplifyMapView` provides a default search field, place markers, visualization modes (map or list) and map controls. It can be used to easily embed a place picker into any app. To use the search functionality of `AmplifyMapView`, provision a search index resource using the instructions in either [Configure Location Search](/[platform]/build-a-backend/more-features/geo/configure-location-search/) or [Use existing Amazon Location Service resources](/[platform]/build-a-backend/more-features/geo/existing-resources/).
The `AmplifyMapView` provides a default search field, place markers, visualization modes (map or list) and map controls. It can be used to easily embed a place picker into any app. To use the search functionality of `AmplifyMapView`, provision a search index resource using the instructions in either [Configure Location Search](/[platform]/build-a-backend/add-aws-services/geo/configure-location-search/) or [Use existing Amazon Location Service resources](/[platform]/build-a-backend/add-aws-services/geo/configure-location-search/).

### Add a map to your app

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ An application with Amplify libraries integrated and a minimum target of any of
- **watchOS 9.0**, using **Xcode 14.3** or later.
- **visionOS 1.0**, using **Xcode 15 beta 2** or later. (Preview support - see below for more details.)

For a full example, please follow the [project setup walkthrough](/[platform]/start/project-setup/prerequisites/).
For a full example, please follow the [project setup walkthrough](/[platform]/start/quickstart/).

<Callout>

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -426,7 +426,7 @@ func confirmSignUp(for username: String, with confirmationCode: String) -> AnyCa

<Callout info>

**Note:** When specifying `email` or `phone` as a way for your users to sign-in, these are attributes that are used in place of the username. Visit the [concepts page to learn more about usernames](/[platform]/build-a-backend/auth/concepts/usernames).
**Note:** When specifying `email` or `phone` as a way for your users to sign-in, these are attributes that are used in place of the username. Visit the [concepts page to learn more about usernames](/[platform]/build-a-backend/auth/concepts/).

</Callout>

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ Future<void> confirmTotpUser(String totpCode) async {
```
### Confirm signin with custom challenge

If the next step is `confirmSignInWithCustomChallenge`, Amplify Auth is awaiting completion of a custom authentication challenge. The challenge is based on the AWS Lambda trigger you configured as part of a [custom sign in flow](/[platform]/build-a-backend/auth/sign-in-custom-flow/).
If the next step is `confirmSignInWithCustomChallenge`, Amplify Auth is awaiting completion of a custom authentication challenge. The challenge is based on the AWS Lambda trigger you configured as part of a [custom sign in flow](/[platform]/build-a-backend/auth/customize-auth-lifecycle/custom-auth-flows/#sign-in-a-user).

For example, your custom challenge Lambda may pass a prompt to the frontend which requires the user to enter a secret code.

Expand Down Expand Up @@ -864,7 +864,7 @@ Once the authenticator app is set up, the user can generate a TOTP code and prov

### Confirm signin with custom challenge

If the next step is `CONFIRM_SIGN_IN_WITH_CUSTOM_CHALLENGE`, Amplify Auth is awaiting completion of a custom authentication challenge. The challenge is based on the Lambda trigger you setup when you configured a [custom sign in flow](/[platform]/build-a-backend/auth/sign-in-custom-flow/). To complete this step, you should prompt the user for the custom challenge answer, and pass the answer to the `confirmSignIn` API.
If the next step is `CONFIRM_SIGN_IN_WITH_CUSTOM_CHALLENGE`, Amplify Auth is awaiting completion of a custom authentication challenge. The challenge is based on the Lambda trigger you setup when you configured a [custom sign in flow](/[platform]/build-a-backend/auth/customize-auth-lifecycle/custom-auth-flows/#sign-in-a-user). To complete this step, you should prompt the user for the custom challenge answer, and pass the answer to the `confirmSignIn` API.

<BlockSwitcher>

Expand Down Expand Up @@ -1598,7 +1598,7 @@ func confirmSignInWithTOTPSetup(totpCodeFromAuthenticatorApp: String) -> AnyCanc
### Confirm signin with custom challenge
If the next step is `confirmSignInWithCustomChallenge`, Amplify Auth is awaiting completion of a custom authentication challenge. The challenge is based on the Lambda trigger you setup when you configured a [custom sign in flow](/[platform]/build-a-backend/auth/sign-in-custom-flow/). To complete this step, you should prompt the user for the custom challenge answer, and pass the answer to the `confirmSignIn` API.
If the next step is `confirmSignInWithCustomChallenge`, Amplify Auth is awaiting completion of a custom authentication challenge. The challenge is based on the Lambda trigger you setup when you configured a [custom sign in flow](/[platform]/build-a-backend/auth/customize-auth-lifecycle/custom-auth-flows/#sign-in-a-user). To complete this step, you should prompt the user for the custom challenge answer, and pass the answer to the `confirmSignIn` API.
<BlockSwitcher>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ RxAmplify.Auth.signInWithWebUI(this)

An application with a minimum target of **iOS 13.0** and/or **macOS 10.15** with Amplify libraries integrated, using **Xcode 14.1** or later.

For a full example, please follow the [project setup walkthrough](/[platform]/start/project-setup/prerequisites/).
For a full example, please follow the [project setup walkthrough](/[platform]/start/quickstart/).

<Callout>

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -695,7 +695,7 @@ await Promise.all(
The recommended access patterns in these docs attempt to remove deleted files, but favor leaving orphans over leaving records that point to non-existent files. This optimizes for read latency by ensuring clients _rarely_ attempt to fetch a non-existent file from Storage. However, any app that deletes files can inherently cause records _on-device_ to point to non-existent files.
One example is when we [create an API record, associate the Storage file with that record, and then retrieve the file's signed URL](#create-a-record-with-an-associated-file). "Device A" calls the GraphQL API to create `API_Record_1`, and then associates that record with `First_Photo`. Before "Device A" is about to retrieve the signed URL, "Device B" might query `API_Record_1`, delete `First_Photo`, and update the record accordingly. However, "Device A" is still using the old `API_Record_1`, which is now out-of-date. Even though the shared global state is correctly in sync at every stage, the individual device ("Device A") has an out-of-date record that points to a non-existent file. Similar issues can conceivably occur for updates. Depending on your app, some of these mismatches can be minimized _even more_ with [real-time data / GraphQL subscriptions](/[platform]/build-a-backend/graphqlapi/subscribe-data/).
One example is when we [create an API record, associate the Storage file with that record, and then retrieve the file's signed URL](#create-a-record-with-an-associated-file). "Device A" calls the GraphQL API to create `API_Record_1`, and then associates that record with `First_Photo`. Before "Device A" is about to retrieve the signed URL, "Device B" might query `API_Record_1`, delete `First_Photo`, and update the record accordingly. However, "Device A" is still using the old `API_Record_1`, which is now out-of-date. Even though the shared global state is correctly in sync at every stage, the individual device ("Device A") has an out-of-date record that points to a non-existent file. Similar issues can conceivably occur for updates. Depending on your app, some of these mismatches can be minimized _even more_ with [real-time data / GraphQL subscriptions](/[platform]/build-a-backend/data/subscribe-data/).
It is important to understand when these mismatches can occur and to add meaningful error handling around these cases. This guide does not include exhaustive error handling, real-time subscriptions, re-querying of outdated records, or attempts to retry failed operations. However, these are all important considerations for a production-level application.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ An application with Amplify libraries integrated and a minimum target of any of
- **watchOS 9.0**, using **Xcode 14.3** or later.
- **visionOS 1.0**, using **Xcode 15 beta 2** or later. (Preview support - see below for more details.)

For a full example, please follow the [project setup walkthrough](/[platform]/start/project-setup/prerequisites/).
For a full example, please follow the [project setup walkthrough](/[platform]/start/quickstart/).

<Callout>
{/* is the visionOS support callout relevant here? */}
Expand Down Expand Up @@ -253,11 +253,11 @@ Amplify configured with Auth and Storage plugins
### Prerequisites

* An Android application targeting Android API level 24 (Android 7.0) or above
* For a full example of creating Android project, please follow the [project setup walkthrough](/[platform]/start/project-setup/create-application/)
* For a full example of creating Android project, please follow the [project setup walkthrough](/[platform]/start/quickstart/)

### Install the Amplify library

Expand **Gradle Scripts**, open **build.gradle (Module: app)**. You will already have configured Amplify by following the steps in the [Project Setup walkthrough](/[platform]/start/project-setup/create-application/).
Expand **Gradle Scripts**, open **build.gradle (Module: app)**. You will already have configured Amplify by following the steps in the [Project Setup walkthrough](/[platform]/start/quickstart/).

Add these libraries into the `dependencies` block:
```groovy
Expand Down Expand Up @@ -420,7 +420,7 @@ Note that because the storage category requires auth, you will need to either co
* Any Windows OS meeting Flutter minimums
* macOS version 10.15 or higher
* Any Ubuntu Linux distribution meeting Flutter minimums
* For a full example please follow the [project setup walkthrough](/[platform]/start/project-setup/create-application/)
* For a full example please follow the [project setup walkthrough](/[platform]/start/quickstart/)

### Install Amplify library

Expand Down
6 changes: 3 additions & 3 deletions src/pages/[platform]/start/quickstart/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1679,7 +1679,7 @@ You can terminate the sandbox environment now to clean up the project.

### Publishing changes to cloud

For publishing the changes to cloud, you need to create a remote git repository. For a detailed guide, you can follow the link [here](/gen2/start/quickstart/#create-remote-git-repository).
For publishing the changes to cloud, you need to create a remote git repository. For a detailed guide, you can follow the link [here](/[platform]/start/quickstart/#publishing-changes-to-cloud).

</InlineFilter>

Expand Down Expand Up @@ -2625,7 +2625,7 @@ This Quickstart guide will walk you through how to build a Todo application usin
<Callout>
Amplify now requires native modules not available through the Expo SDK. As a result, Expo Go is no longer supported but you should still be able to use Expo. [Learn more about dropping support for Expo Go in Amplify v6](/react-native/build-a-backend/troubleshooting/migrate-from-javascript-v5-to-v6/#dropping-support-for-expo-go).
Amplify now requires native modules not available through the Expo SDK. As a result, Expo Go is no longer supported but you should still be able to use Expo. [Learn more about dropping support for Expo Go in Amplify v6](/gen1/react-native/build-a-backend/troubleshooting/migrate-from-javascript-v5-to-v6/).
</Callout>
Expand Down Expand Up @@ -2934,7 +2934,7 @@ You can terminate the sandbox environment now to clean up the project.
### Publishing changes to cloud
For publishing the changes to cloud, you need to create a remote git repository. For a detailed guide, you can follow the link [here](/gen2/start/quickstart/#create-remote-git-repository).
For publishing the changes to cloud, you need to create a remote git repository. For a detailed guide, you can follow the link [here](/[platform]/start/quickstart/#publishing-changes-to-cloud).
</InlineFilter>
Expand Down

0 comments on commit dec20d3

Please sign in to comment.