Async/await in Unity - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this async method in Unity?

Consider this Unity C# script snippet using async/await. What will be printed in the Unity console?

Unity

using System.Threading.Tasks;
using UnityEngine;

public class AsyncTest : MonoBehaviour
{
    async void Start()
    {
        Debug.Log("Start");
        await Task.Delay(1000);
        Debug.Log("After delay");
    }
}

A Start immediately, then after 1 second print 'After delay'

B Only prints 'Start' and never prints 'After delay'

C Throws a runtime exception because Task.Delay is not supported

D Prints 'After delay' first, then 'Start'

💡 Hint

Think about how async/await works with Task.Delay in Unity's main thread.

The Start method prints 'Start' immediately, then awaits Task.Delay(1000) which pauses asynchronously for 1 second without blocking the main thread. After the delay, it prints 'After delay'.

🧠 Conceptual

intermediate

Which statement about async/await in Unity is true?

Choose the correct statement about using async/await in Unity.

A async void methods are recommended for all Unity event functions to handle async code

B await Task.Delay blocks the main thread in Unity

C async Task methods can be awaited and allow better error handling than async void

D Unity's main thread cannot run async methods at all

💡 Hint

Consider the difference between async void and async Task in C#.

async Task methods return a Task and can be awaited, allowing exceptions to be caught. async void methods cannot be awaited and are only recommended for event handlers. Unity's main thread can run async methods without blocking.

🔧 Debug

advanced

Why does this async method cause a deadlock in Unity?

Examine this code snippet. Why does it cause the Unity editor to freeze?

Unity

using System.Threading.Tasks;
using UnityEngine;

public class DeadlockExample : MonoBehaviour
{
    void Start()
    {
        var result = GetData().Result;
        Debug.Log(result);
    }

    async Task<string> GetData()
    {
        await Task.Delay(1000);
        return "Data loaded";
    }
}

A Debug.Log cannot be called inside Start method

B Task.Delay is not awaited properly causing infinite wait

C GetData method is missing async keyword

D Calling .Result on an async Task blocks the main thread causing a deadlock

💡 Hint

Think about what happens when you block the main thread waiting for an async method that also needs the main thread.

Calling .Result blocks the main thread waiting for GetData to complete. But GetData awaits Task.Delay and tries to resume on the main thread, which is blocked. This causes a deadlock freezing Unity.

📝 Syntax

advanced

Which option correctly defines an async method returning a value in Unity?

Choose the correct syntax for an async method that returns an integer after a delay.

A async int GetNumber() { await Task.Delay(500); return 42; }

B async Task<int> GetNumber() { await Task.Delay(500); return 42; }

C Task<int> async GetNumber() { await Task.Delay(500); return 42; }

D async void GetNumber() { await Task.Delay(500); return 42; }

💡 Hint

Remember the correct order of async and return type for methods returning a value.

The correct syntax is 'async Task MethodName()'. Option B correctly places async before Task. Option B is invalid because async cannot be used with plain int return type. Option B has wrong order. Option B returns void but tries to return a value.

🚀 Application

expert

How many times will 'Loading...' print in this Unity async loop?

Analyze this Unity C# code. How many times will 'Loading...' be printed in the console?

Unity

using System.Threading.Tasks;
using UnityEngine;

public class LoopAsync : MonoBehaviour
{
    async void Start()
    {
        for (int i = 0; i < 3; i++)
        {
            Debug.Log("Loading...");
            await Task.Delay(500);
        }
        Debug.Log("Done");
    }
}

A 3 times, once per loop iteration

B 1 time, because await delays the whole loop

C 0 times, because Debug.Log is skipped in async methods

D Infinite times, because the loop never ends

💡 Hint

Consider how the for loop and await work together in async methods.

The loop runs 3 times. Each iteration prints 'Loading...', then awaits 500ms before continuing. So 'Loading...' prints exactly 3 times, then 'Done' prints once.