Over-the-air updates (EAS Update) in React Native - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the EAS Update module in a React Native app.

React Native

import [1] from 'expo-updates';

Drag options to blanks, or click blank then click option'

AUpdates

BExpoUpdates

CEASUpdate

DUpdateManager

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect module names like 'EASUpdate' or 'ExpoUpdates'.

Trying to import from a wrong package.

You import the EAS Update module using Updates from expo-updates.

2fill in blank

medium

Complete the code to check if a new update is available using EAS Update.

React Native

const update = await Updates.[1]();

Drag options to blanks, or click blank then click option'

AfetchUpdate

BcheckForUpdate

CcheckForUpdateAsync

DgetUpdate

Attempts:

3 left

💡 Hint

Common Mistakes

Using a method without 'Async' suffix.

Using a method name that does not exist.

The correct method to check for updates asynchronously is checkForUpdateAsync().

3fill in blank

hard

Fix the error in the code to reload the app after an update is downloaded.

React Native

if (update.isAvailable) {
  await Updates.fetchUpdateAsync();
  await Updates.[1]();
}

Drag options to blanks, or click blank then click option'

AreloadAsync

Breload

Crestart

DreloadApp

Attempts:

3 left

💡 Hint

Common Mistakes

Using synchronous reload methods that do not exist.

Calling reload without awaiting the update download.

The method to reload the app asynchronously is reloadAsync(). Using reload() or others will cause errors.

4fill in blank

hard

Fill both blanks to create a function that checks for updates and reloads the app if an update is available.

React Native

async function checkAndUpdate() {
  const update = await Updates.[1]();
  if (update.[2]) {
    await Updates.fetchUpdateAsync();
    await Updates.reloadAsync();
  }
}

Drag options to blanks, or click blank then click option'

AcheckForUpdateAsync

BisAvailable

ChasUpdate

DfetchUpdateAsync

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect method names for checking updates.

Using wrong property names to check update availability.

You use checkForUpdateAsync() to check for updates and isAvailable to see if an update exists.

5fill in blank

hard

Fill all three blanks to implement a complete update check, fetch, and reload sequence.

React Native

async function performUpdate() {
  const update = await Updates.[1]();
  if (update.[2]) {
    await Updates.[3]();
    await Updates.reloadAsync();
  }
}

Drag options to blanks, or click blank then click option'

AcheckForUpdateAsync

BisAvailable

CreloadAsync

DfetchUpdateAsync

Attempts:

3 left

💡 Hint

Common Mistakes

Skipping the fetch update step before reloading.

Using wrong method names for fetching or reloading.

First, check for updates with checkForUpdateAsync(). Then, if isAvailable is true, fetch the update with fetchUpdateAsync() before reloading.

Practice

1.

What is the main benefit of using Over-the-air (OTA) updates with EAS Update in a React Native app?

easy

A. Fix bugs and add features without waiting for app store approval

B. Increase app size by adding more assets

C. Require users to reinstall the app for every update

D. Disable app functionality temporarily during updates

Solution

1. Step 1: Understand OTA update purpose

   OTA updates let developers fix bugs and add features quickly without app store delays.

2. Step 2: Compare options

   Only Fix bugs and add features without waiting for app store approval describes this benefit correctly; others describe drawbacks or unrelated effects.

3. Final Answer:

   Fix bugs and add features without waiting for app store approval -> Option A

4. Quick Check:

   OTA updates = fast fixes and features [OK]

Hint: OTA updates = fast fixes without app store wait [OK]

Common Mistakes:

• Thinking OTA updates increase app size
• Believing users must reinstall app for OTA
• Assuming app disables during update

2.

Which of the following is the correct way to import the Expo Updates API in a React Native app?

?

easy

A. import { Updates } from 'expo';

B. import Updates from 'react-native-updates';

C. const Updates = require('expo-updates');

D. import * as Updates from 'expo-updates';

Solution

1. Step 1: Recall Expo Updates import syntax

   The official Expo Updates API is imported using "import * as Updates from 'expo-updates';".

2. Step 2: Check other options

   Options A, B, and C use incorrect package names or import styles not recommended for Expo Updates.

3. Final Answer:

   import * as Updates from 'expo-updates'; -> Option D

4. Quick Check:

   Correct import = import * as Updates from 'expo-updates'; [OK]

Hint: Expo Updates import uses * as Updates from 'expo-updates' [OK]

Common Mistakes:

• Using wrong package name like 'react-native-updates'
• Using require instead of import
• Importing Updates from 'expo' instead of 'expo-updates'

3.

Given this React Native code snippet using Expo Updates API, what will be logged if an update is available?

import * as Updates from 'expo-updates';

async function checkUpdate() {
  const update = await Updates.checkForUpdateAsync();
  if (update.isAvailable) {
    console.log('Update found!');
  } else {
    console.log('No update available.');
  }
}

checkUpdate();

medium

A. SyntaxError

B. No update available.

C. Update found!

D. Nothing is logged

Solution

1. Step 1: Analyze checkForUpdateAsync result

   The function returns an object with isAvailable true if an update exists.

2. Step 2: Follow the if condition

   If update.isAvailable is true, it logs 'Update found!'. Otherwise, logs 'No update available.'

3. Final Answer:

   Update found! -> Option C

4. Quick Check:

   Update available logs 'Update found!' [OK]

Hint: If update.isAvailable true, logs 'Update found!' [OK]

Common Mistakes:

• Confusing checkForUpdateAsync return value
• Expecting syntax error from async function
• Thinking nothing logs without await

4.

Identify the error in this code snippet that tries to fetch and reload an update using Expo Updates API:

import * as Updates from 'expo-updates';

async function updateApp() {
  const update = Updates.checkForUpdateAsync();
  if (update.isAvailable) {
    await Updates.fetchUpdateAsync();
    Updates.reloadAsync();
  }
}

medium

A. reloadAsync() must be called before fetchUpdateAsync()

B. Missing await before Updates.checkForUpdateAsync()

C. fetchUpdateAsync() should not be awaited

D. No error, code is correct

Solution

1. Step 1: Check async function usage

   Updates.checkForUpdateAsync() returns a Promise and must be awaited to get the result.

2. Step 2: Identify missing await impact

   Without await, update is a Promise, so update.isAvailable is undefined causing error.

3. Final Answer:

   Missing await before Updates.checkForUpdateAsync() -> Option B

4. Quick Check:

   Always await async calls to get results [OK]

Hint: Always await async calls like checkForUpdateAsync() [OK]

Common Mistakes:

• Forgetting await on async functions
• Calling reloadAsync() before fetching update
• Assuming fetchUpdateAsync() is synchronous

5.

You want your React Native app to check for OTA updates on app start, download them silently, and apply on next app reload. Which approach correctly implements this behavior?

?

hard

A. Use Updates.checkForUpdateAsync(), then if available, call Updates.fetchUpdateAsync() without reload, apply on next start

B. Call Updates.reloadAsync() immediately on app start to force update

C. Only call Updates.fetchUpdateAsync() without checking availability

D. Use Updates.checkForUpdateAsync() and reloadAsync() immediately without fetching

Solution

1. Step 1: Understand OTA update flow

   Check for update availability first, then fetch update silently if available.

2. Step 2: Apply update on next reload

   Fetching update downloads it; reloadAsync applies update immediately, but we want to apply on next app start.

3. Final Answer:

   Use Updates.checkForUpdateAsync(), then if available, call Updates.fetchUpdateAsync() without reload, apply on next start -> Option A

4. Quick Check:

   Check, fetch silently, reload later = Use Updates.checkForUpdateAsync(), then if available, call Updates.fetchUpdateAsync() without reload, apply on next start [OK]

Hint: Check availability, fetch silently, reload later for smooth update [OK]

Common Mistakes:

• Reloading app immediately causing bad UX
• Fetching update without checking availability
• Reloading without fetching update