Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Building Cloud-enabled Mobile Applications with React Native & AWS Amplify

NotificationsYou must be signed in to change notification settings

dabit3/aws-amplify-workshop-react-native

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

In this workshop we'll learn how to build cloud-enabled mobile applications with React Native &AWS Amplify.

Amplify React Native Workshop

Topics we'll be covering:

Getting Started - Creating the React Native Application

To get started, we first need to create a new React Native project & change into the new directory using either theReact Native CLI (SeeBuilding Projects With Native Code in the documentation) orExpo CLI.

We can use the React Native CLI or Expo to create a new app:

If you're using the React Native CLI (you're not using Expo)

Change into the app directory & install the dependencies

$ npx react-native init RNAmplify$cd RNAmplify$ npm install --save aws-amplify aws-amplify-react-native uuid amazon-cognito-identity-js @react-native-community/netinfo# or$ yarn add aws-amplify aws-amplify-react-native uuid amazon-cognito-identity-js @react-native-community/netinfo

Next, for iOS you need to install the pods:

$cd ios$ pod install --repo-update$cd ..

If you are using Expo

$ npx expo init RNAmplify> Choose a template: blank$cd RNAmplify$ npm install --save aws-amplify aws-amplify-react-native uuid @react-native-community/netinfo# or$ yarn add aws-amplify aws-amplify-react-native uuid

Running the app

Next, run the app:

$ npx react-native run-ios# or if running android$ npx react-native run-android# or, if using expo$ expo start

Installing the CLI & Initializing a new AWS Amplify Project

Installing the CLI

Next, we'll install the AWS Amplify CLI:

$ npm install -g @aws-amplify/cli

Now we need to configure the CLI with our credentials:

$amplifyconfigure

If you'd like to see a video walkthrough of this configuration process, clickhere.

Here we'll walk through theamplify configure setup. Once you've signed in to the AWS console, continue:

  • Specify the AWS Region:your preferred region
  • Specify the username of the new IAM user:amplify-workshop-user

In the AWS Console, clickNext: Permissions,Next: Tags,Next: Review, &Create User to create the new IAM user. Then, return to the command line & press Enter.

  • Enter the access key of the newly created user:
    accessKeyId:(<YOUR_ACCESS_KEY_ID>)
    secretAccessKey:(<YOUR_SECRET_ACCESS_KEY>)
  • Profile Name:amplify-workshop-user

Initializing A New AWS Amplify Project

Make sure to initialize this Amplify project in the root of your new React Native application

$ amplify init
  • Enter a name for the project:RNAmplify
  • Enter a name for the environment:dev
  • Choose your default editor:Visual Studio Code (or your favorite editor)
  • Please choose the type of app that you're buildingjavascript
  • What javascript framework are you usingreact-native
  • Source Directory Path:/
  • Distribution Directory Path:/
  • Build Command:npm run-script build
  • Start Command:npm run-script start
  • Select the authentication method you want to use:AWS profile
  • Please choose the profile you want to use:amplify-workshop-user

Now, the AWS Amplify CLI has iniatilized a new project & you will see a couple of new files & folders:amplify &aws-exports.js. These files hold your project configuration.

Configuring the React Native application

The next thing we need to do is to configure our React Native application to be aware of our new AWS Amplify project. We can do this by referencing the auto-generatedaws-exports.js file that is now in our root folder.

If you are using the React Native CLI (not using Expo)

To configure the app, openindex.js and add the following code below the last import:

// index.jsimportAmplifyfrom'aws-amplify'importconfigfrom'./aws-exports'Amplify.configure(config)

Now, our app is ready to start using our AWS services.

If you are using the Expo (not using the React Native CLI)

To configure the app, openApp.js and add the following code below the last import:

// App.jsimportAmplifyfrom'aws-amplify'importconfigfrom'./aws-exports'Amplify.configure(config)

Now, our app is ready to start using our AWS services.

Adding Authentication

To add authentication, we can use the following command:

$ amplify add auth
  • Do you want to use default authentication and security configuration?Default configuration
  • How do you want users to be able to sign in when using your Cognito User Pool?Username (keep default)
  • Do you want to configure advanced settings?No

Now, we'll run the push command and the cloud resources will be created in our AWS account.

$ amplify push

To view the AWS services any time after their creation, run the following command:

$ amplify console

Using the withAuthenticator component

To add authentication, we'll go intoApp.js and first import thewithAuthenticator HOC (Higher Order Component) fromaws-amplify-react:

// App.jsimport{withAuthenticator}from'aws-amplify-react-native'

Next, we'll wrap our default export (the App component) with thewithAuthenticator HOC:

exportdefaultwithAuthenticator(App,{includeGreetings:true})

Now, we can run the app and see that an Authentication flow has been added in front of our App component. This flow gives users the ability to sign up & sign in.

To refresh, you can use one of the following commands:

# iOS SimulatorCMD + d# Opens debug menuCMD + r# Reloads the app# Android EmulatorCTRL + m# Opens debug menurr# Reloads the app

Accessing User Data

We can access the user's info now that they are signed in by callingAuth.currentAuthenticatedUser().

// App.jsimportReactfrom'react';import{SafeAreaView,StyleSheet,Text,}from'react-native';import{withAuthenticator}from'aws-amplify-react-native'import{Auth}from'aws-amplify'classAppextendsReact.Component{asynccomponentDidMount(){constuser=awaitAuth.currentAuthenticatedUser()console.log('user:',user)}render(){return(<SafeAreaViewstyle={styles.container}><Textstyle={styles.title}>Hello World</Text></SafeAreaView>)}}conststyles=StyleSheet.create({container:{flex:1,justifyContent:'center',alignItems:'center'},title:{fontSize:28}})exportdefaultwithAuthenticator(App,{includeGreetings:true})

Signing out with a custom Sign Out button

We can also sign the user out using theAuth class & callingAuth.signOut(). This function returns a promise that is fulfilled after the user session has been ended & AsyncStorage is updated.

BecausewithAuthenticator holds all of the state within the actual component, we must have a way to rerender the actualwithAuthenticator component by forcing React to rerender the parent component.

To do so, let's make a few updates:

// App.jsimportReactfrom'react';import{SafeAreaView,StyleSheet,Text,}from'react-native';import{withAuthenticator}from'aws-amplify-react-native'import{Auth}from'aws-amplify'classAppextendsReact.Component{asynccomponentDidMount(){constuser=awaitAuth.currentAuthenticatedUser()console.log('user:',user)}signOut=()=>{Auth.signOut().then(()=>this.props.onStateChange('signedOut')).catch(err=>console.log('err: ',err))}render(){return(<SafeAreaViewstyle={styles.container}><Textstyle={styles.title}>Hello World</Text><TextonPress={this.signOut}>Sign Out</Text></SafeAreaView>)}}conststyles=StyleSheet.create({container:{flex:1,justifyContent:'center',alignItems:'center'},title:{fontSize:28}})exportdefaultwithAuthenticator(App);

Custom authentication strategies

To view a final solution for a custom authentication strategy, check out theAWS Amplify React Native Auth Starterhere.

This section is an overview and is considered an advanced part of the workshop. If you are not comfortable writing a custom authentication flow, I would read through this section and use it as a reference in the future. If you'd like to jump to the next section, clickhere.

ThewithAuthenticator component is a really easy way to get up and running with authentication, but in a real-world application we probably want more control over how our form looks & functions.

Let's look at how we might create our own authentication flow.

To get started, we would probably want to create input fields that would hold user input data in the state. For instance when signing up a new user, we would probably need 3 user inputs to capture the user's username, email, & password.

To do this, we could create some initial state for these values & create an event handler that we could attach to the form inputs:

// initial statestate={username:'',password:'',email:''}// event handleronChangeText=(key,value)=>{this.setState({[key]:value})}// example of usage with TextInput<TextInputplaceholder='username'value={this.state.username}style={{width:300,height:50,margin:5,backgroundColor:"#ddd"}}onChangeText={v=>this.onChange('username',v)}/>

We'd also need to have a method that signed up & signed in users. We can us the Auth class to do thi. The Auth class has over 30 methods including things likesignUp,signIn,confirmSignUp,confirmSignIn, &forgotPassword. Thes functions return a promise so they need to be handled asynchronously.

// import the Auth componentimport{Auth}from'aws-amplify'// Class method to sign up a usersignUp=async()=>{const{ username, password, email}=this.statetry{awaitAuth.signUp({ username, password,attributes:{ email}})}catch(err){console.log('error signing up user...',err)}}

Adding a GraphQL API with AWS AppSync

To add a GraphQL API, we can use the following command:

$ amplify add api

Answer the following questions

  • Please select from one of the above mentioned servicesGraphQL
  • Provide API name:RestaurantAPI
  • Choose the default authorization type for the APIAPI key
  • Enter a description for the API keypublic
  • After how many days from now the API key should expire365
  • Do you want to configure advanced settings for the GraphQL APINo
  • Do you have an annotated GraphQL schema?N
  • Choose a schema template:Single object with fields (e.g. “Todo” with ID, name, description)
  • Do you want to edit the schema now? (Y/n)Y

When prompted, update the schema to the following:

typeRestaurant@model {id:ID!clientId:Stringname:String!description:String!city:String!}

Next, deploy the API:

amplify push? Are you sure you want to continue? Yes? Do you want to generate codefor your newly created GraphQL API: Yes? Choose the code generation language target: javascript? Enter the file name pattern of graphql queries, mutations and subscriptions: ./graphql/**/*.js? Do you want to generate/update all possible GraphQL operations - queries, mutations and subscriptions: Yes? Enter maximum statement depth [increase from defaultif your schema is deeply nested] (2)

Optional - To mock and test the API locally, you can run the mock command:

$ amplify mock api

This should start an AppSync Mock endpoint:

AppSync Mock endpoint is running at http://10.219.99.136:20002

Open the endpoint in the browser to use the GraphiQL Editor.

From here, we can now test the API.

Adding mutations from within the GraphiQL Editor.

In the GraphiQL editor, execute the following mutation to create a new restaurant in the API:

mutationcreateRestaurant {createRestaurant(input: {name:"Nobu"description:"Great Sushi"city:"New York"  }) {idnamedescriptioncity  }}

Now, let's query for the restaurant:

querylistRestaurants {listRestaurants {items {idnamedescriptioncity    }  }}

We can even add search / filter capabilities when querying:

querysearchRestaurants {listRestaurants(filter: {city: {contains:"New York"    }  }) {items {idnamedescriptioncity    }  }}

Or, get an individual restaurant by ID:

querygetRestaurant {getRestaurant(id:"RESTAURANT_ID") {namedescriptioncity  }}

Interacting with the GraphQL API from our client application - Querying for data

Now that the GraphQL API is created we can begin interacting with it!

The first thing we'll do is perform a query to fetch data from our API.

To do so, we need to define the query, execute the query, store the data in our state, then list the items in our UI.

importReactfrom'react';import{SafeAreaView,View,StyleSheet,Text,}from'react-native';// imports from Amplify libraryimport{withAuthenticator}from'aws-amplify-react-native'import{API,graphqlOperation}from'aws-amplify'// import the GraphQL queryimport{listRestaurants}from'./graphql/queries'classAppextendsReact.Component{// define some state to hold the data returned from the APIstate={restaurants:[]}// execute the query in componentDidMountasynccomponentDidMount(){try{constrestaurantData=awaitAPI.graphql(graphqlOperation(listRestaurants))console.log('restaurantData:',restaurantData)this.setState({restaurants:restaurantData.data.listRestaurants.items})}catch(err){console.log('error fetching restaurants...',err)}}render(){return(<SafeAreaViewstyle={styles.container}>{this.state.restaurants.map((restaurant,index)=>(<Viewkey={index}style={styles.item}><Textstyle={styles.name}>{restaurant.name}</Text><Textstyle={styles.description}>{restaurant.description}</Text><Textstyle={styles.city}>{restaurant.city}</Text></View>))}</SafeAreaView>)}}conststyles=StyleSheet.create({container:{flex:1,justifyContent:'center',},item:{padding:10},name:{fontSize:20},description:{fontWeight:'600',marginTop:4,color:'rgba(0, 0, 0, .5)'},city:{marginTop:4}})exportdefaultwithAuthenticator(App,{includeGreetings:true});

Performing mutations

Now, let's look at how we can create mutations. The mutation we will be working with iscreateRestaurant.

// App.jsimportReactfrom'react';import{SafeAreaView,View,StyleSheet,Text,TextInput,Button}from'react-native';// imports from Amplify libraryimport{withAuthenticator}from'aws-amplify-react-native'import{API,graphqlOperation}from'aws-amplify'// import the GraphQL queryimport{listRestaurants}from'./graphql/queries'// import the GraphQL mutationimport{createRestaurant}from'./graphql/mutations'// create client IDimport{v4asuuid}from'uuid'constCLIENTID=uuid()classAppextendsReact.Component{// add additional state to hold form state as well as restaurant data returned from the APIstate={name:'',description:'',city:'',restaurants:[]}// execute the query in componentDidMountasynccomponentDidMount(){try{constrestaurantData=awaitAPI.graphql(graphqlOperation(listRestaurants))console.log('restaurantData:',restaurantData)this.setState({restaurants:restaurantData.data.listRestaurants.items})}catch(err){console.log('error fetching restaurants...',err)}}// this method calls the API and creates the mutationcreateRestaurant=async()=>{const{ name, description, city}=this.state// store the restaurant data in a variableconstrestaurant={      name, description, city,clientId:CLIENTID}// perform an optimistic response to update the UI immediatelyconstrestaurants=[...this.state.restaurants,restaurant]this.setState({      restaurants,name:'',description:'',city:''})try{// make the API callawaitAPI.graphql(graphqlOperation(createRestaurant,{input:restaurant}))console.log('item created!')}catch(err){console.log('error creating restaurant...',err)}}// change form state then user types into inputonChange=(key,value)=>{this.setState({[key]:value})}render(){return(<SafeAreaViewstyle={styles.container}><TextInputstyle={{height:50,margin:5,backgroundColor:"#ddd"}}onChangeText={v=>this.onChange('name',v)}value={this.state.name}placeholder='name'/><TextInputstyle={{height:50,margin:5,backgroundColor:"#ddd"}}onChangeText={v=>this.onChange('description',v)}value={this.state.description}placeholder='description'/><TextInputstyle={{height:50,margin:5,backgroundColor:"#ddd"}}onChangeText={v=>this.onChange('city',v)}value={this.state.city}placeholder='city'/><ButtononPress={this.createRestaurant}title='Create Restaurant'/>{this.state.restaurants.map((restaurant,index)=>(<Viewkey={index}style={styles.item}><Textstyle={styles.name}>{restaurant.name}</Text><Textstyle={styles.description}>{restaurant.description}</Text><Textstyle={styles.city}>{restaurant.city}</Text></View>))}</SafeAreaView>)}}conststyles=StyleSheet.create({container:{flex:1,justifyContent:'center',},item:{padding:10},name:{fontSize:20},description:{fontWeight:'600',marginTop:4,color:'rgba(0, 0, 0, .5)'},city:{marginTop:4}})exportdefaultwithAuthenticator(App,{includeGreetings:true});

Challenge

Recreate this functionality in Hooks

For direction, check out the tutorialhere

For the solution to this challenge, view thehooks file.

Adding a Serverless Function

Adding a basic Lambda Function

To add a serverless function, we can run the following command:

$ amplify add function? Select which capability you want to add: Lambda function? Provide an AWS Lambdafunctionnam: basiclambda? Choose the runtime that you want to use: NodeJS? Choose thefunctiontemplate that you want to use: Hello World? Do you want to configure advanced settings? N? Do you want to edit thelocal lambdafunctionnow? Y

This should open the function package located atamplify/backend/function/basiclambda/src/index.js.

Edit the function to look like this, & then save the file.

exports.handler=async(event,contex)=>{console.log('event: ',event)constbody={message:"Hello world!"}constresponse={statusCode:200,    body}returnresponse}

Next, we can test this out by running:

$ amplify mockfunctionbasiclambda? Provide the path to the event JSON object: src/event.json

You'll notice the following output from your terminal:

Ensuring latestfunctionchanges are built...Starting execution...event:  { key1:'value1', key2:'value2', key3:'value3' }Result:{"statusCode": 200,"body": {"message":"Hello world!"  }}Finished execution.

Where is the event data coming from? It is coming from the values located in event.json in the function folder (amplify/backend/function/basiclambda/src/event.json). If you update the values here, you can simulate data coming arguments the event.

Feel free to test out the function by updatingevent.json with data of your own.

Adding a function running an express server and invoking it from an API call (http)

Next, we'll build a function that will be running anExpress server inside of it.

This new function will fetch data from a cryptocurrency API & return the values in the response.

To get started, we'll create a new function:

$ amplify add function? Select which capability you want to add: Lambda function? Provide an AWS Lambdafunctionname: cryptofunction? Choose the runtime that you want to use: NodeJS? Choose thefunctiontemplate that you want to use: Serverless ExpressJS? Do you want to configure advanced settings? No? Do you want to edit thelocal lambdafunctionnow? Y

This should open the function package located atamplify/backend/function/cryptofunction/src/index.js. You'll notice in this file, that the event is being proxied into an express server:

exports.handler=(event,context)=>{console.log(`EVENT:${JSON.stringify(event)}`);awsServerlessExpress.proxy(server,event,context);};

Instead of updating the handler function itself, we'll instead updateamplify/backend/function/cryptofunction/src/app.js which has the actual server code we would like to be working with.

Here, inamplify/backend/function/cryptofunction/src/app.js, we'll add the following code & save the file:

// amplify/backend/function/cryptofunction/src/app.js// you should see this code already there 👇:app.use(function(req,res,next){res.header("Access-Control-Allow-Origin","*")res.header("Access-Control-Allow-Headers","Origin, X-Requested-With, Content-Type, Accept")next()});// below the above code, add the following code 👇 (be sure not to delete any other code from this file)constaxios=require('axios')app.get('/coins',function(req,res){letapiUrl=`https://api.coinlore.com/api/tickers?start=0&limit=10`if(req&&req.query){// here we are checking to see if there are any query parameters, and if so appending them to the requestconst{ start=0, limit=10}=req.queryapiUrl=`https://api.coinlore.com/api/tickers/?start=${start}&limit=${limit}`}axios.get(apiUrl).then(response=>{res.json({coins:response.data.data})}).catch(err=>res.json({error:err}))})

In the above function we've used theaxios library to call another API. In order to useaxios, we need be sure that it will be installed by updating thepackage.json for the new function:

$cd amplify/backend/function/cryptofunction/src$ npm install axios$cd ../../../../../

Next, change back into the root directory.

Adding a REST API

Now that we've created the cryptocurrency Lambda function let's add an API endpoint so we can invoke it via http.

To add the REST API, we can use the following command:

$ amplify add api? Pleaseselectfrom one of the above mentioned services: REST? Provide a friendly nameforyour resource that will be used to label this categoryin the project: cryptoapi? Provide a path (e.g., /items): /coins? Choose lambda source: Use a Lambdafunctionalready addedin the current Amplify project? Choose the Lambdafunctionto invoke by this path: cryptofunction? Restrict API access: Y? Who should have access? Authenticated users only? What kind of accessdo you wantfor Authenticated users: read/create/update/delete? Do you want to add another path? (y/N) N

Now the resources have been created & configured & we can push them to our account:

$ amplify push? Are you sure you want to continue? Y

Interacting with the new API

Now that the API is created we can start sending requests to it & interacting with it.

Let's request some data from the API:

// App.jsimportReactfrom'react'import{View,Text,StyleSheet}from'react-native'import{API}from'aws-amplify'import{withAuthenticator}from'aws-amplify-react-native'classAppextendsReact.Component{state={coins:[]}asynccomponentDidMount(){try{// to get all coins, do not send in a query parameter// const data = await API.get('cryptoapi', '/coins')constdata=awaitAPI.get('cryptoapi','/coins?limit=5&start=100')console.log('data from Lambda REST API: ',data)this.setState({coins:data.coins})}catch(err){console.log('error fetching data..',err)}}render(){return(<View>{this.state.coins.map((c,i)=>(<Viewkey={i}style={styles.row}><Textstyle={styles.name}>{c.name}</Text><Text>{c.price_usd}</Text></View>))}</View>)}}conststyles=StyleSheet.create({row:{padding:10},name:{fontSize:20,marginBottom:4},})exportdefaultwithAuthenticator(App,{includeGreetings:true})

Adding Analytics

To add analytics, we can use the following command:

$ amplify add analytics

Next, we'll be prompted for the following:

  • Provide your pinpoint resource name:amplifyanalytics
  • Apps need authorization to send analytics events. Do you want to allow guest/unauthenticated users to send analytics events (recommended when getting started)?Y

To deploy, run thepush command:

$ amplify push

Recording events

Now that the service has been created we can now begin recording events.

To record analytics events, we need to import theAnalytics class from Amplify & then callAnalytics.record:

import{Analytics}from'aws-amplify'state={username:''}asynccomponentDidMount(){try{constuser=awaitAuth.currentAuthenticatedUser()this.setState({username:user.username})}catch(err){console.log('error getting user: ',err)}}recordEvent=()=>{Analytics.record({name:'My test event',attributes:{username:this.state.username}})}<ButtononPress={this.recordEvent}title='Record Event'/>

To view the analytics in the console, run theconsole command:

$ amplify console

In the console, click onAnalytics, then click onView in Pinpoint. In thePinpoint console, click onevents and then enable filters.

Working with Storage

To add storage, we can use the following command:

amplify add storage

Answer the following questions

  • Please select from one of the below mentioned servicesContent (Images, audio, video, etc.)
  • Please provide a friendly name for your resource that will be used to label this category in theproject:rnworkshopstorage
  • Please provide bucket name:YOUR_UNIQUE_BUCKET_NAME
  • Who should have access:Auth users only
  • What kind of access do you want for Authenticated users?
❯◉ create/update ◉read ◉ delete
amplify push

Now, storage is configured & ready to use.

What we've done above is created configured an Amazon S3 bucket that we can now start using for storing items.

For example, if we wanted to test it out we could store some text in a file like this:

import{Storage}from'aws-amplify'// create function to work with StorageaddToStorage=()=>{Storage.put('textfiles/mytext.txt',`Hello World`).then(result=>{console.log('result: ',result)}).catch(err=>console.log('error: ',err));}// add click handler<ButtononPress={this.addToStorage}title='Add to Storage'/>

This would create a folder calledtextfiles in our S3 bucket & store a file calledmytext.txt there with the code we specified in the second argument ofStorage.put.

If we want to read everything from this folder, we can useStorage.list:

readFromStorage=()=>{Storage.list('textfiles/').then(data=>console.log('data from S3: ',data)).catch(err=>console.log('error fetching from S3',err))}

If we only want to read the single file, we can useStorage.get:

readFromStorage=()=>{Storage.get('textfiles/mytext.txt').then(data=>{console.log('data from S3: ',data)fetch(data).then(r=>r.text()).then(text=>{console.log('text: ',text)}).catch(e=>console.log('error fetching text: ',e))}).catch(err=>console.log('error fetching from S3',err))}

If we wanted to pull down everything, we can useStorage.list:

readFromStorage=()=>{Storage.list('').then(data=>console.log('data from S3: ',data)).catch(err=>console.log('error fetching from S3',err))}

Multiple Serverless Environments

Now that we have our API up & running, what if we wanted to update our API but wanted to test it out without it affecting our existing version?

To do so, we can create a clone of our existing environment, test it out, & then deploy & test the new resources.

Once we are happy with the new feature, we can then merge it back into our main environment. Let's see how to do this!

Creating a new environment

To create a new environment, we can run theenv command:

$ amplify env add> Do you want to use an existing environment? No> Enter a namefor the environment: apiupdate> Do you want to use an AWS profile? Yes> Please choose the profile you want to use: appsync-workshop-profile

Now, the new environment has been initialize, & we can deploy the new environment using thepush command:

$ amplify push

Now that the new environment has been created we can get a list of all available environments using the CLI:

$ amplify env list

Let's update the GraphQL schema to add a new field. Inamplify/backend/api/RestaurantAPI/schema.graphql update the schema to the following:

typeRestaurant@model {id:ID!clientId:Stringname:String!type:Stringdescription:String!city:String!}typeModelRestaurantConnection {items: [Restaurant]nextToken:String}typeQuery {listAllRestaurants(limit:Int,nextToken:String):ModelRestaurantConnection}

In the schema we added a new field to theRestaurant definition to define the type of restaurant:

type:String

Now, we can run amplify push again to update the API:

$ amplify push

To test this out, we can go into theAppSync Console & log into the API.

You should now see a new API calledRestaurantAPI-apiupdate. Click on this API to view the API dashboard.

If you click onSchema you should notice that it has been created with the newtype field. Let's try it out.

To test it out we need to create a new user because we are using a brand new authentication service. To do this, open the app & sign up.

In the API dashboard, click onQueries.

Next, click on theLogin with User Pools link.

Copy theaws_user_pools_web_client_id value from youraws-exports file & paste it into theClientId field.

Next, login using yourusername &password.

Now, create a new mutation & then query for it:

mutationcreateRestaurant {createRestaurant(input: {name:"Nobu"description:"Great Sushi"city:"New York"type:"sushi"  }) {idnamedescriptioncitytype  }}querylistRestaurants {listAllRestaurants {items {namedescriptioncitytype    }  }}

Merging the new environment changes into the main environment.

Now that we've created a new environment & tested it out, let's check out the main environment.

$ amplify env checkoutlocal

Next, run thestatus command:

$ amplify status

You should now see anUpdate operation:

Current Environment: local| Category | Resource name   | Operation | Provider plugin   || -------- | --------------- | --------- | ----------------- || Api      | RestaurantAPI   | Update    | awscloudformation || Auth     | cognito75a8ccb4 | No Change | awscloudformation |

To deploy the changes, run the push command:

$ amplify push

Now, the changes have been deployed & we can delete theapiupdate environment:

$ amplify env remove apiupdateDo you also want to remove all the resources of the environment from the cloud? Y

Now, we should be able to run thelist command & see only our main environment:

$ amplify env list

Removing Services

If at any time, or at the end of this workshop, you would like to delete a service from your project & your account, you can do this by running theamplify remove command:

$ amplify remove auth$ amplify push

If you are unsure of what services you have enabled at any time, you can run theamplify status command:

$ amplify status

amplify status will give you the list of resources that are currently enabled in your app.

Deleting the project

To delete the entire project, run thedelete command:

$ amplify delete

About

Building Cloud-enabled Mobile Applications with React Native & AWS Amplify

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

[8]ページ先頭

©2009-2025 Movatter.jp