Bird
Raised Fist0
React Nativemobile~20 mins

Over-the-air updates (EAS Update) in React Native - Mini App: Build & Ship

Choose your learning style10 modes available
Build: EAS Update Demo
This screen shows how to check for and apply over-the-air updates using Expo Application Services (EAS) Update in a React Native app.
Target UI
┌───────────────────────────────┐
│        EAS Update Demo         │
├───────────────────────────────┤
│ Status: Checking for updates...│
│                               │
│ [Check for Update]             │
│                               │
│ [Apply Update]                │
│                               │
│ Last update: None             │
└───────────────────────────────┘
Display current update status text (e.g., 'Checking for updates...', 'Up to date', 'Update available').
Add a button labeled 'Check for Update' that checks if an update is available.
Add a button labeled 'Apply Update' that downloads and reloads the app if an update is found.
Show the last update time or 'None' if no update applied yet.
Handle errors gracefully and show error messages in the status text.
Starter Code
React Native
import React, { useState } from 'react';
import { View, Text, Button, StyleSheet } from 'react-native';
import * as Updates from 'expo-updates';

export default function EASUpdateDemo() {
  const [status, setStatus] = useState('Idle');
  const [lastUpdate, setLastUpdate] = useState('None');

  // TODO: Implement checkForUpdate function

  // TODO: Implement applyUpdate function

  return (
    <View style={styles.container}>
      <Text style={styles.title}>EAS Update Demo</Text>
      <Text style={styles.status}>Status: {status}</Text>
      <View style={styles.buttonContainer}>
        <Button title="Check for Update" onPress={() => {}} />
      </View>
      <View style={styles.buttonContainer}>
        <Button title="Apply Update" onPress={() => {}} disabled />
      </View>
      <Text style={styles.lastUpdate}>Last update: {lastUpdate}</Text>
    </View>
  );
}

const styles = StyleSheet.create({
  container: { flex: 1, justifyContent: 'center', alignItems: 'center', padding: 20 },
  title: { fontSize: 24, fontWeight: 'bold', marginBottom: 20 },
  status: { fontSize: 16, marginBottom: 20 },
  buttonContainer: { marginVertical: 10, width: '60%' },
  lastUpdate: { marginTop: 30, fontSize: 14, fontStyle: 'italic' }
});
Task 1
Task 2
Task 3
Task 4
Task 5
Solution
React Native
import React, { useState } from 'react';
import { View, Text, Button, StyleSheet } from 'react-native';
import * as Updates from 'expo-updates';

export default function EASUpdateDemo() {
  const [status, setStatus] = useState('Idle');
  const [lastUpdate, setLastUpdate] = useState('None');
  const [updateAvailable, setUpdateAvailable] = useState(false);

  async function checkForUpdate() {
    setStatus('Checking for updates...');
    try {
      const update = await Updates.checkForUpdateAsync();
      if (update.isAvailable) {
        setStatus('Update available');
        setUpdateAvailable(true);
      } else {
        setStatus('Up to date');
        setUpdateAvailable(false);
      }
    } catch (e) {
      setStatus('Error checking updates');
      setUpdateAvailable(false);
    }
  }

  async function applyUpdate() {
    setStatus('Downloading update...');
    try {
      await Updates.fetchUpdateAsync();
      setStatus('Applying update...');
      await Updates.reloadAsync();
      // After reload, this code runs fresh, so lastUpdate resets
    } catch (e) {
      setStatus('Error applying update');
    }
  }

  return (
    <View style={styles.container}>
      <Text style={styles.title}>EAS Update Demo</Text>
      <Text style={styles.status}>Status: {status}</Text>
      <View style={styles.buttonContainer}>
        <Button title="Check for Update" onPress={checkForUpdate} />
      </View>
      <View style={styles.buttonContainer}>
        <Button title="Apply Update" onPress={applyUpdate} disabled={!updateAvailable} />
      </View>
      <Text style={styles.lastUpdate}>Last update: {lastUpdate}</Text>
    </View>
  );
}

const styles = StyleSheet.create({
  container: { flex: 1, justifyContent: 'center', alignItems: 'center', padding: 20 },
  title: { fontSize: 24, fontWeight: 'bold', marginBottom: 20 },
  status: { fontSize: 16, marginBottom: 20 },
  buttonContainer: { marginVertical: 10, width: '60%' },
  lastUpdate: { marginTop: 30, fontSize: 14, fontStyle: 'italic' }
});

This React Native screen uses Expo Updates API to check and apply over-the-air updates.

When the user taps 'Check for Update', the app calls Updates.checkForUpdateAsync() to see if a new update is available. The status text updates to show the result.

If an update is available, the 'Apply Update' button becomes enabled. When tapped, it downloads the update with Updates.fetchUpdateAsync() and then reloads the app with Updates.reloadAsync() to apply the update immediately.

Errors during checking or applying updates are caught and shown in the status text.

The last update time is shown but remains 'None' here because this example does not persist update timestamps across reloads. In a real app, you could save the update time in persistent storage.

Final Result
Completed Screen
┌───────────────────────────────┐
│        EAS Update Demo         │
├───────────────────────────────┤
│ Status: Up to date             │
│                               │
│ [Check for Update]             │
│                               │
│ [Apply Update] (disabled)      │
│                               │
│ Last update: None             │
└───────────────────────────────┘
Tapping 'Check for Update' changes status to 'Checking for updates...' then 'Up to date' or 'Update available'.
If update is available, 'Apply Update' button becomes enabled.
Tapping 'Apply Update' downloads and reloads the app to apply the update.
If errors occur, status shows error messages.
Stretch Goal
Add a timestamp showing when the last successful update was applied, saved persistently.
💡 Hint
Use React Native AsyncStorage or Expo SecureStore to save the update time before calling reloadAsync, then read it on app start.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard