iOS Build Environment Help Center

Where is the SDK migration assistant?

append delete Brett

So I'm literally on the first step of the first steps of the documentation. Trying to copy over the files from the Mac side of the computer to the Windows side, and I cannot find the Shortcut for the SDK migration assistant. The documentation says it's in All Programs > iOS Project Builder for Unity, but I don't see this.

It's almost like there was an install step that I missed?

How do I first install the iOS Project Builder for Unity, so I can have access to the SDK migration assistant shortcut?

Reply RSS

Replies

append delete #1. Pierre-Marie Baty

Hello

You’ll find it in the builder’s install directory (typically in your Windows profile home directory)

Did I mistakenly remove the shortcut from the installer script ? I’ll have to check that.

:: @Pierre-Marie Baty added on 07 Apr ’22 · 07:51

*edit* Which version of Windows do you use ?

append delete #2. Brett

Ok, so the problem was I didn't actually download and install the package from your website. I was blindly following the documentation, and it didn't mention I had to download something from your website. I guess that should be a "before the first steps of the first steps" in the documentation.

Now I'm running into a problem with the Private key passphrase. Where do I get this? I've googled all over the place and can't seem to find where I get the Private key passphrase.

Thanks,
-Brett

append delete #3. Pierre-Marie Baty

Hello

If you migrated your signing identity from macOS, the private key passphrase is a passphrase that you choose, to protect your signing identity from being used by anybody else but you. Should I change what the dialog box says, would you suggest another wording ?

If you created your signing identity from scratch using the Keychain tool, it's the same thing : a passphrase that you choose to protect your key from being used without your consent.

All of this is covered in the documentation, in the section that deals with signing identities.

It's also possible to use "unprotected" signing identities, in which case the builder greys out the passphrase text field. I don't recommend it though, because that would make signing identity theft possible if someone could obtain your Keychain files. To "unprotect" your private key, you need to run a special OpenSSL command on it (and supply the passphrase of course).

append delete #4. Brett

Ok well I used XCode to generate my signing identity automatically, so I have no clue what the passphrase is.

Should I just delete everything and start from scratch? Or should I start again from the mac side and migrate again?

What is the preferred method of action here?

append delete #5. Pierre-Marie Baty

There’s a misunderstanding here. Passphrases are used only by the builder on Windows. Xcode’s private keys are stored in the Mac’s keychain, which itself is protected by the Mac user account’s (or the Mac administrator) password. When the builder migrates the signing identities created by Xcode, it first asks for the Mac keychain’s password to access them - at this point they’re unprotected -, *then* it asks you for a passphrase of your choosing to store them in protected form outside of the Mac’s keychain.

I advise you to take the time to read that documentation again and make sure you understand everything.

:: @Pierre-Marie Baty added on 21 Apr ’22 · 19:27

*edit* Regarding your question specifically, unless your iOS signing identity is used by other people or other projects, the simplest way is almost always to create a new one from scratch.

append delete #6. Brett

Thanks for the info!

Yea, I figure I'll just wipe everything and start from scratch. Can I do this all from your windows tools, or should I wipe my mac, start over, and then migrate the keys once I make the new ones on the mac?

I would like to do it all from your windows tools, if possible!

append delete #7. Pierre-Marie Baty

Yes, you can do all that from Windows.

*Please* read the documentation that I endured writing specifically with the goal of avoiding spending all my time answering common questions.

append delete #8. Brett

I did a search for passphrase in the documentation, and it doesn't mention that I need to keep the passphrase from the migration assistant to use in your keychain tool. If you could add that note to the documentation, it might avoid this situation in the future with other potential customers.

append delete #9. Pierre-Marie Baty

Well, the dialog box that asked you for that passphrase explains its purpose and why you need to remember it. And your question about whether creating a signing identity could be done in Windows was already covered in the documentation.

append delete #10. Brett

Hey, I'm just trying to help you out here. Having to battle with Apple's insane keychain process is difficult enough, so having clear, concise, and redundant documentation on your end is only going to help new users like myself out. You may say something in a dialog, but if you also have that in the documentation, it will make situations like much easier to handle.

append delete #11. Pierre-Marie Baty

Noted. I will add a paragraph in the documentation.

Reply

(Leave this as-is, it’s a trap!)

There is no need to “register”, just enter the same name + password of your choice every time.

Pro tip: Use markup to add links, quotes and more.

Moderators: Pierre-Marie Baty