How to call UIApplicationMain in main.swift in Swift 3

Question

mattn OP

Created May ’16

Replies 5

Boosts 0

Views 13k

Participants 3

I don't understand how to write a main.swift file in Swift 3 (current toolchain). We used to write it like this:

 UIApplicationMain(
    Process.argc, Process.unsafeArgv, nil, NSStringFromClass(AppDelegate)
)

But now that won't compile, because there is a type mismatch between

Process.argv

, which is typed like this:

UnsafeMutablePointer<UnsafeMutablePointer<Int8>?>

and the second parameter to UIApplicationMain, which is typed like this:

UnsafeMutablePointer<UnsafeMutablePointer<Int8>>!

As you can see, they are subtly different. I am able to work around the problem by writing this:

 withUnsafeMutablePointer(&Process.unsafeArgv.pointee!) {
    UIApplicationMain(
        Process.argc, $0, nil, NSStringFromClass(AppDelegate)
    )
}

But whether that is safe or correct, I have no idea.

Boost

Answer 1

DTS Engineer OP

Apple

May ’16

This seems like fallout from the recent change in how unsafe pointers interact with optional. I think

Process.argv

is correct, in that

Process.argv

itself can’t be nil, but any of the elements it points to can be nil. I recommend that you file a bug against

UIApplicationMain

. Please post your bug number, just for the record.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 2

mattn OP

May ’16

Thanks, radar 26062787 submitted. I'm also going to post this on bugs.swift, as it affects them. They had `@UIApplicationMain` wrong on the last toolchain release, and if the signature of UIApplicationMain changes again, `@UIApplicationMain` will be wrong again.

0

Answer 3

mattn OP

May ’16

Jordan Rose has suggested working around it like this:

 UIApplicationMain(
    Process.argc, UnsafeMutablePointer<UnsafeMutablePointer<CChar>>(Process.unsafeArgv), nil, NSStringFromClass(AppDelegate)
)

0

Answer 4

ellucian-jkh OP

Aug ’16

This broke for me in Xcode 8 beta 6. What is the new suggestion?

0

Answer 5

mattn OP

Aug ’16

Like this:

 UIApplicationMain(
    CommandLine.argc,
    UnsafeMutableRawPointer(CommandLine.unsafeArgv)
        .bindMemory(
            to: UnsafeMutablePointer<Int8>.self,
            capacity: Int(CommandLine.argc)),
    nil,
    NSStringFromClass(AppDelegate.self)
)

0

	UIApplicationMain(
	Process.argc, Process.unsafeArgv, nil, NSStringFromClass(AppDelegate)
	)

	withUnsafeMutablePointer(&Process.unsafeArgv.pointee!) {
	UIApplicationMain(
	Process.argc, $0, nil, NSStringFromClass(AppDelegate)
	)
	}

	UIApplicationMain(
	Process.argc, UnsafeMutablePointer<UnsafeMutablePointer<CChar>>(Process.unsafeArgv), nil, NSStringFromClass(AppDelegate)
	)

	UIApplicationMain(
	CommandLine.argc,
	UnsafeMutableRawPointer(CommandLine.unsafeArgv)
	.bindMemory(
	to: UnsafeMutablePointer<Int8>.self,
	capacity: Int(CommandLine.argc)),
	nil,
	NSStringFromClass(AppDelegate.self)
	)