macOs Swift Command Line App crashes on Task statement - swift

Question

I am trying a simple exercise to demonstrate using async/await in Swift and, best that I can isolate, the app crashes when executing the Task statement. I have tried catching the exception on-throw and on-catch and the call stack does not provide any additional insight into the issue. The error is on Thread 1:
Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)
My theory is that the COMMAND LINE template does not support Task in this simple form.
//
// main.swift
//
import Foundation
struct User {
var username: String
var movies = [Movie]()
}
struct Movie {
var title: String
var rating: Double?
}
class ManagerUsingAsync {
func getUsers() async throws -> [User] {
let allIsGood = true // Bool.random()
if allIsGood {
let users = ["mary", "casey", "theo", "dick"].map { User(username: $0) }
return users
} else {
throw URLError(.cannotConnectToHost)
}
}
func getUsersMovies(username: String) async throws -> [Movie] {
let allIsGood = true // Bool.random()
if allIsGood {
let movies = ["breaking away", "diner", "the great escape"].map { Movie(title: $0) }
return movies
} else {
throw URLError(.cannotCreateFile)
}
}
func getMovieRating(title: String) async -> Double? {
let allIsGood = true // Bool.random()
if allIsGood {
return Double.random(in: 1...10)
}
return nil
}
}
func testAsync() async -> [User] {
var _users = [User]()
let manager = ManagerUsingAsync()
do {
_users = try await manager.getUsers()
for var user in _users {
user.movies = try await manager.getUsersMovies(username: user.username)
for var movie in user.movies {
movie.rating = await manager.getMovieRating(title: movie.title)
}
}
} catch (let error) {
print(error.localizedDescription)
}
return _users
}
print("TEST ASYNC/AWAIT...")
Task {
let users = await testAsync()
for user in users {
print( "Username: \(user.username) Movies: \(user.movies)" )
}
}

Answer 1

Apparently this is somehow related to how my corporate MacBook is locked-down. I cannot figure this out in deeper detail, but the same code works fine (as did for #RobNapier as shared in the comments) on my personal MacBook.
Not sure if this Q should be withdrawn, but there is something to be learned about corporate MDM impact on developers (not the first time). FWIW -- My corp MacBook is managed by JAMF.