Downloaded certificates not showing up in Certificate Trust Authority

Question

Created 3w

Replies 3

Boosts 0

Participants 2

Under iOS 18.0.1, I can't do any development that uses HTTPS, because I can't authorize my generated certificates on my phone. This was not a problem in the past.

Normally you AirDrop a root certificate authority to your phone, install the "profile" for it, and then trust it in Settings / General / About / Certificate Trust Authority. Then you can connect to another server on your network that's using the accompanying certificates.

But after sucessfully installing two profiles on my phone, neither shows up in Certificate Trust Authority. Anybody else seeing this?

This problem, in combo with this one (which prevents running on my Mac as an iPad app) has completely halted my project.

I've found reports of this problem that blamed an empty "common name" field in the certs, but that field is populated in both of these.

Answered by DTS Engineer in 809155022

It’s better if you reply as a reply, rather than in the comments. See Quinn’s Top Ten DevForums Tips for this and other titbits.

This is on a new iPhone 16, but I did transfer settings & data from a phone running iOS 15.

Oh, interesting. That suggests that you are hitting the same bug, which wasn’t what I expected.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

2w

There’s definitely something weird going on in this space. See this thread.

The concrete steps from that thread suggest that this is caused by folks upgrading from iOS 16 to iOS 18. Is that what you did? It seems unlikely.

I've found reports of this problem that blamed an empty "common name" field in the certs

Yeah, that’s a different variant of this problem. See here.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

DTS Engineer OP

Apple

2w

Recommended

It’s better if you reply as a reply, rather than in the comments. See Quinn’s Top Ten DevForums Tips for this and other titbits.

This is on a new iPhone 16, but I did transfer settings & data from a phone running iOS 15.

Oh, interesting. That suggests that you are hitting the same bug, which wasn’t what I expected.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 3

Stokestack OP

2w

It’s better if you reply as a reply, rather than in the comments

I appreciate that guideline; I've seen you make that remark to other people, so I thought this meant reply directly to your comment instead of making a new comment. So I went from doing it "right" to doing it "wrong."

0