Cloud Storage lets your app save files online so users can access them anytime and anywhere. It keeps data safe and easy to share.
Cloud Storage in iOS Swift
import FirebaseStorage let storage = Storage.storage() let storageRef = storage.reference() // Upload a file let localFile = URL(fileURLWithPath: "path/to/local/file") let fileRef = storageRef.child("folder/filename.ext") fileRef.putFile(from: localFile, metadata: nil) { metadata, error in if let error = error { print("Upload failed: \(error.localizedDescription)") } else { print("Upload successful") } }
Use Storage.storage() to get the cloud storage instance.
Use putFile to upload files asynchronously with a completion handler.
let storage = Storage.storage()
let storageRef = storage.reference()
let imageRef = storageRef.child("images/photo.jpg")imageRef.putFile(from: localURL, metadata: nil) { metadata, error in if error == nil { print("File uploaded") } }
imageRef.downloadURL { url, error in
if let url = url {
print("Download URL: \(url)")
}
}This SwiftUI app uploads a small text file to cloud storage when you tap the button. It shows a message if the upload worked or failed.
import SwiftUI import FirebaseStorage struct ContentView: View { @State private var message = "" var body: some View { VStack(spacing: 20) { Text(message) .padding() Button("Upload Sample File") { uploadSampleFile() } } .padding() } func uploadSampleFile() { let storage = Storage.storage() let storageRef = storage.reference() let fileRef = storageRef.child("samples/hello.txt") // Create a temporary file with sample text let tempDir = FileManager.default.temporaryDirectory let localURL = tempDir.appendingPathComponent("hello.txt") try? "Hello Cloud Storage!".write(to: localURL, atomically: true, encoding: .utf8) fileRef.putFile(from: localURL, metadata: nil) { metadata, error in if let error = error { message = "Upload failed: \(error.localizedDescription)" } else { message = "Upload successful!" } } } }
Make sure to configure Firebase in your app before using cloud storage.
Uploading files is asynchronous; use completion handlers to update UI.
Files are stored in paths like folders; organize them logically.
Cloud Storage saves files online for easy access and sharing.
Use storage references to point to file locations.
Upload files with putFile and handle success or errors.
Practice
What is the main purpose of Cloud Storage in an iOS app?
Solution
Step 1: Understand Cloud Storage role
Cloud Storage is designed to save files online so users can access and share them easily.Step 2: Compare options
Options B, C, and D describe other app functions unrelated to Cloud Storage.Final Answer:
To save files online for easy access and sharing -> Option CQuick Check:
Cloud Storage = Online file saving [OK]
- Confusing Cloud Storage with local storage
- Thinking it manages UI or navigation
- Assuming it stores app settings only
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 = ...
Solution
Step 1: Recall Firebase Storage syntax
To get a reference, use storage.reference() then child("filename") to point to the file.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.Final Answer:
storageRef = storage.reference().child("image.png") -> Option BQuick Check:
Use reference().child() to get file reference [OK]
- Calling child() directly on storage
- Using Storage.reference() instead of storage.reference()
- Passing filename directly to reference()
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")
}
}Solution
Step 1: Analyze the completion handler
The closure checks if error is nil; if so, it prints "Upload succeeded".Step 2: Given successful upload
Since upload is successful, error is nil, so the else block runs printing "Upload succeeded".Final Answer:
Upload succeeded -> Option AQuick Check:
Success means error is nil, print "Upload succeeded" [OK]
- Assuming error is always non-nil
- Confusing success and failure blocks
- Ignoring the asynchronous completion handler
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")
}
}Solution
Step 1: Check URL creation method
URL(string:) is for web URLs; local file paths need URL(fileURLWithPath:).Step 2: Identify impact
Using URL(string:) with a local path returns nil or incorrect URL, causing upload failure.Final Answer:
Using URL(string:) instead of URL(fileURLWithPath:) -> Option AQuick Check:
Local file URLs need URL(fileURLWithPath:) [OK]
- Using URL(string:) for local files
- Forgetting to unwrap optional URLs safely
- Ignoring completion handler errors
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)Solution
Step 1: Understand asynchronous behavior
Uploads and downloadURL calls run asynchronously, so print(downloadURLs) runs before completion.Step 2: Effect on printed output
Because of async calls, downloadURLs is likely empty when printed immediately after the loop.Final Answer:
This code may print an empty array because uploads are asynchronous -> Option DQuick Check:
Async uploads delay URL collection, print runs too early [OK]
- Expecting synchronous behavior from async uploads
- Printing results before upload completion
- Not using dispatch groups or async-await to wait
Ready to prove it?
Pass the test and this pattern moves unknown
