iOS credentials: p12 file password issues

Unity Services
1

Hi!

Just added a new project, but there was a ton of trouble because the p12 file password kept getting rejected even though it is the very same file and password I have successfully used for previous Cloud Build projects.

Initially I just tried re-exporting the certificate into new p12 files 4-5 times to make sure I don’t somehow have an issue with the password input on Cloud Build page, but none of the file/password inputs were accepted.

This morning I retried thinking that maybe it was a server issue, but still had no success with the existing certificates. I made one more cert p12 export and used a temporary, super simple password this time and everything worked immediately.

QUESTION: So, is there a list of some characters you are silently rejecting for password input that could be the cause of my repeated iOS credentials setup failures over the past two days?

I would think alphanumerics, spaces, special characters are all valid for password use and should absolutely be allowed for better password strengths.

2

You can try remove the pass. Also there was a bug in UCB before: if you entered a wrong pass, or provided wrong certs, then the next attempts won’t work too. You had to refresh the page to try again.

3

I don’t think we should be rejecting any special characters. The one that comes to mind that might not be handled properly is spaces. Yes, ideally this would be supported but at the moment that’s the one that might not work.

1 Like
4

Yeah, “space” character in password string was the issue. Please make an announcement when you get those working as well. Thanks for the answers!

1 Like