Cloud Storage in iOS Swift - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Cloud Storage in mobile app development?

Cloud Storage is a service that lets apps save and retrieve files or data on internet servers instead of the device. It helps keep data safe and accessible from anywhere.

beginner

Name a popular Cloud Storage service used in iOS apps.

Firebase Storage is a popular Cloud Storage service for iOS apps. It allows easy upload and download of files like images and videos.

beginner

Why use Cloud Storage instead of local device storage?

Cloud Storage keeps data safe even if the device is lost or damaged. It also allows sharing data across devices and users easily.

intermediate

What is a common step before uploading a file to Cloud Storage in Swift?

You usually convert the file (like an image) into Data format and then use the Cloud Storage API to upload that data.

intermediate

How can you secure files in Cloud Storage?

You secure files by setting rules and permissions on who can read or write files. For example, Firebase Storage uses security rules to control access.

What does Cloud Storage allow your app to do?

A Delete all local files automatically

B Only save files on the device

C Run the app offline only

D Save files on internet servers

Cloud Storage lets apps save files on internet servers, making them accessible from anywhere.

Which format is commonly used to upload images to Cloud Storage in Swift?

A Data

B String

C UIImage

D Int

Images are converted to Data format before uploading to Cloud Storage.

What is a benefit of using Cloud Storage over local storage?

A Data is lost if device is damaged

B Data can be shared across devices

C Files cannot be accessed online

D It uses more device memory

Cloud Storage allows sharing data across devices and users.

Which service is commonly used for Cloud Storage in iOS apps?

A Firebase Storage

B Core Data

C UserDefaults

D SQLite

Firebase Storage is a popular Cloud Storage service for iOS apps.

How do you control who can access files in Cloud Storage?

A By deleting files regularly

B By storing files locally only

C By setting security rules and permissions

D By using only public URLs

Security rules and permissions control access to files in Cloud Storage.

Explain how Cloud Storage benefits mobile apps compared to local storage.

Think about what happens if a phone is lost or you want to use the app on another device.

Describe the basic steps to upload an image file to Cloud Storage in an iOS app using Swift.

Focus on how the image is prepared and sent to the cloud.

Practice

1.

What is the main purpose of Cloud Storage in an iOS app?

easy

A. To create user interface elements

B. To store app settings locally on the device

C. To save files online for easy access and sharing

D. To manage app navigation flow

Solution

1. Step 1: Understand Cloud Storage role

   Cloud Storage is designed to save files online so users can access and share them easily.

2. Step 2: Compare options

   Options B, C, and D describe other app functions unrelated to Cloud Storage.

3. Final Answer:

   To save files online for easy access and sharing -> Option C

4. Quick Check:

   Cloud Storage = Online file saving [OK]

Hint: Cloud Storage means saving files online, not local data [OK]

Common Mistakes:

• Confusing Cloud Storage with local storage
• Thinking it manages UI or navigation
• Assuming it stores app settings only

2.

Which of the following is the correct way to create a reference to a file named image.png in Firebase Cloud Storage using Swift?

let storage = Storage.storage()
let storageRef = ...

easy

A. storageRef = storage.child("image.png")

B. storageRef = storage.reference().child("image.png")

C. storageRef = Storage.reference("image.png")

D. storageRef = storage.reference("image.png")

Solution

1. Step 1: Recall Firebase Storage syntax

   To get a reference, use storage.reference() then child("filename") to point to the file.

2. Step 2: Check each option

   storageRef = storage.reference().child("image.png") correctly chains reference() and child(). Options B, C, and D use incorrect method calls or syntax.

3. Final Answer:

   storageRef = storage.reference().child("image.png") -> Option B

4. Quick Check:

   Use reference().child() to get file reference [OK]

Hint: Use reference().child("filename") to get file reference [OK]

Common Mistakes:

• Calling child() directly on storage
• Using Storage.reference() instead of storage.reference()
• Passing filename directly to reference()

3.

What will be printed if the following Swift code successfully uploads a file to Firebase Storage?

let storageRef = Storage.storage().reference().child("file.txt")
let localFile = URL(fileURLWithPath: "/path/to/file.txt")
storageRef.putFile(from: localFile, metadata: nil) { metadata, error in
  if let error = error {
    print("Upload failed: \(error.localizedDescription)")
  } else {
    print("Upload succeeded")
  }
}

medium

A. Upload succeeded

B. Upload failed: File not found

C. Upload failed: Network error

D. No output

Solution

1. Step 1: Analyze the completion handler

   The closure checks if error is nil; if so, it prints "Upload succeeded".

2. Step 2: Given successful upload

   Since upload is successful, error is nil, so the else block runs printing "Upload succeeded".

3. Final Answer:

   Upload succeeded -> Option A

4. Quick Check:

   Success means error is nil, print "Upload succeeded" [OK]

Hint: If error is nil, upload succeeded message prints [OK]

Common Mistakes:

• Assuming error is always non-nil
• Confusing success and failure blocks
• Ignoring the asynchronous completion handler

4.

Identify the error in this Swift code snippet for uploading a file to Firebase Storage:

let storageRef = Storage.storage().reference().child("doc.pdf")
let fileURL = URL(string: "/documents/doc.pdf")!
storageRef.putFile(from: fileURL, metadata: nil) { metadata, error in
  if error != nil {
    print("Upload error")
  } else {
    print("Upload complete")
  }
}

medium

A. Using URL(string:) instead of URL(fileURLWithPath:)

B. Missing metadata parameter in putFile

C. Incorrect child path syntax

D. No completion handler provided

Solution

1. Step 1: Check URL creation method

   URL(string:) is for web URLs; local file paths need URL(fileURLWithPath:).

2. Step 2: Identify impact

   Using URL(string:) with a local path returns nil or incorrect URL, causing upload failure.

3. Final Answer:

   Using URL(string:) instead of URL(fileURLWithPath:) -> Option A

4. Quick Check:

   Local file URLs need URL(fileURLWithPath:) [OK]

Hint: Use URL(fileURLWithPath:) for local file paths [OK]

Common Mistakes:

• Using URL(string:) for local files
• Forgetting to unwrap optional URLs safely
• Ignoring completion handler errors

5.

You want to upload multiple images to Firebase Cloud Storage and keep track of their download URLs for later use. Which approach correctly handles this in Swift?

let images = [URL(fileURLWithPath: "/img1.png"), URL(fileURLWithPath: "/img2.png")]
var downloadURLs: [URL] = []
for imageURL in images {
  let ref = Storage.storage().reference().child(imageURL.lastPathComponent)
  ref.putFile(from: imageURL, metadata: nil) { metadata, error in
    if error == nil {
      ref.downloadURL { url, error in
        if let url = url {
          downloadURLs.append(url)
        }
      }
    }
  }
}
print(downloadURLs)

hard

A. The code will cause a syntax error due to missing await

B. This code correctly prints all download URLs immediately

C. The code uploads files but does not get download URLs

D. This code may print an empty array because uploads are asynchronous

Solution

1. Step 1: Understand asynchronous behavior

   Uploads and downloadURL calls run asynchronously, so print(downloadURLs) runs before completion.

2. Step 2: Effect on printed output

   Because of async calls, downloadURLs is likely empty when printed immediately after the loop.

3. Final Answer:

   This code may print an empty array because uploads are asynchronous -> Option D

4. Quick Check:

   Async uploads delay URL collection, print runs too early [OK]

Hint: Async calls need completion before using results [OK]

Common Mistakes:

• Expecting synchronous behavior from async uploads
• Printing results before upload completion
• Not using dispatch groups or async-await to wait