Developer ID popup invalid entry

John_Eidsvoog · August 16, 2026, 7:37pm

I’ve used ChatGPT to diagnose the following problem. I’ve never issued a bug report before so I thought I’d run it by the forum first to see if anyone else has experienced this (couldn’t find instances of it here). If it’s agreed that it’s a bug, I’ll report it, although I don’t know how. **
**
——————————————————————-

Subject: Xojo 2026r1.2 rejects valid Developer ID identity; Xojo 2025r3.1 accepts it

I’m seeing a macOS code-signing identity-selection problem in Xojo 2026r1.2 (build 67271).

Environment

Mac mini, Apple silicon
macOS 15.7.8
Xcode 26.3
Xojo 2026r1.2, build 67271
Developer ID team: 92N236Y924

Problem

In the macOS build settings, the Developer ID menu displays:

Julie Eidsvoog (92N236Y924)

The certificate actually installed in the login keychain is:

Developer ID Application: John Charles Eidsvoog (92N236Y924)

When I select the displayed team in Xojo 2026r1.2, the Developer ID setting immediately changes back to None. Because it resets immediately, I cannot proceed to select a Build For option.

The same behavior occurs in a newly created blank Desktop project, so it is not specific to my existing project.

Expected behavior

Xojo should accept the team and use the valid Developer ID Application certificate installed in the keychain.

Certificate verification

Terminal reports two valid code-signing identities:

1) A927B8FD9995FD3A5C3DB26DD6CA12726A827E80
   "Developer ID Application: John Charles Eidsvoog (92N236Y924)"

2) E473834B4393D950C9ECADF7EC9B012B67D43713
   "Apple Development: John Charles Eidsvoog (SD7FC2ZV6J)"

2 valid identities found

The Developer ID Application certificate has its private key and expires February 1, 2027.

I also successfully signed a test executable manually:

codesign --force --options runtime --timestamp \
  --sign "Developer ID Application: John Charles Eidsvoog (92N236Y924)" \
  /tmp/noodle-sign-test

Verification showed:

Authority=Developer ID Application: John Charles Eidsvoog (92N236Y924)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
TeamIdentifier=92N236Y924

This demonstrates that the certificate, private key, trust chain, hardened runtime signing, and timestamp service work correctly outside Xojo.

Additional troubleshooting

Restarted Xojo and the Mac.
Reset Xojo preferences and caches, with no change.
Restored the original preferences after testing.
Confirmed the required Apple root and Developer ID intermediate certificates are installed.
Confirmed that a blank Xojo 2026r1.2 Desktop project exhibits the same behavior.
The inspector lists older missing or expired development/distribution certificate records, although those leaf certificates are not present in Keychain Access.

Important comparison

Opening the project in Xojo 2025r3.1 on the same Mac with the same keychain works correctly. That version allows me to enter/select my Developer ID and produces no complaint when running or building.

Therefore, the problem appears specific to the Developer ID/team-selection logic in Xojo 2026r1.2 rather than the project, certificate, private key, or macOS keychain.

John_Eidsvoog · August 16, 2026, 7:43pm

Also, on my MacBook Pro, my correct Developer ID shows, allows my to select it and signs correctly.

John_Eidsvoog · August 17, 2026, 12:38am

I’m also aware this bug may be impossible to reproduce elsewhere, but there must be something that will help.

Javier_Menendez · August 17, 2026, 8:01am

Hard to tell without additional information… because if “Julie Eidsvoog” developer certificates are not installed on that particular Mac is impossible it should be shown by the popup menu. After all, that popup menu displays the Team certificates found on the system. Maybe it would help if you can provide more information about all the developer certificates installed on that Mac (Keychain Access > Login section (at the sidebar) > Certificates. Then View > Show Expired Certificates… so even the expired ones are listed.

Here you can see the correlation between the teams (certificates) installed in Keychain Access app and the ones shown in the Developer ID popup menu from the Xojo IDE:

John_Eidsvoog · August 17, 2026, 2:25pm

Thanks for responding.

I should have added that Julie is my wife. She is not a developer and has no idea what a certificate is. She’s never been assigned any roll as a developer. Somehow, her name has been assigned to my developer ID and that invalidates it in Xojo’s eyes. The Terminal responses show the correct attribution. The only place her name shows up is in Xojo’s Developer ID popup.

I’ve reset/reinitialized these preference files:

~/Library/Preferences/com.xojo.xojo.plist
~/Library/Caches/com.xojo.xojo
~/Library/Caches/Xojo

Perhaps there’s some other hidden Xojo file retaining her name.

Javier_Menendez · August 17, 2026, 2:42pm

I’m clueless… because if there are not Apple developer certificates in your wife’s Mac, then it is no way her name could be added to that popup menu (and moreover attached to your Team ID value).

And, if your Apple Developer Certificates are installed in your wife’s Mac… then those are added to the popup menu… using the corresponding name, not the one from your wife. As you can see in the second screenshot from my reply, there are two more teams added to the popup menu in addition to my own… just because I have some of that developer certificates installed on that particular Mac.

FWIW… that menu is populated from the available installed Apple Developer Certificates on the Mac. That is, similar to how the own Keychain Access app works

In addition, nothing is stored in Xojo preferences, cache files, etc.; and, in fact, the Developer ID popup menu entries changes on the fly to reflect any change made to certificates (adding new ones, removing any of the existing ones, those expired or not valid anymore…)

Javier_Menendez · August 17, 2026, 3:10pm

Could you post please a screenshot from Developer ID > Inspect, after selecting your wife detected Team in the resulting window and got from Xojo running in your wife’s Mac?

John_Eidsvoog · August 17, 2026, 3:16pm

Xojo isn’t installed on my wife’s Mac. Here’s the Inspect screen from my computer. Her non-existent team is listed. Mine is not.

John_Eidsvoog · August 17, 2026, 3:22pm

Here’s the Inspect screen from my MacBook where signing works as expected.

Javier_Menendez · August 17, 2026, 3:29pm

Are you enabling “Show Expired Certificates” from Keychain Access > View menu? Maybe that will bring some hint…

Javier_Menendez · August 17, 2026, 3:36pm

Ok, so I understand that the Mac mini where the problem is shown is also yours (I mean, nothing to do with your wife, wife account on that Mac, etc.), isn’t? And also that on that particular Mac you have the same Developer certificates that on your MacBook Pro.

It would be worth to see if in the Mac mini is some certificate installed whose organizative name is set to “Julie Eidsvoog” and kind of Apple Developer certificate or, for the case, any other type (although we only collect those whose emitter is from Apple, kind = developer and with a trusted chain) .

John_Eidsvoog · August 17, 2026, 5:18pm

Here’s the list with the expired certificates. There’s nothing with Julie’s name and I’ve never issued one for her. Strangely, there are some certificates listed which I don’t recognize. Jacquelyn Herzig and Daniel Gold are friends, I don’t recognize Stephanie Campbell, blog.forestent, or h4ha. I don’t recall requesting any of those.

I should also note that Julie and I have shared my Apple ID, against Apple’s recommendations. But if that were the cause, the MacBook should also have the problem.

John_Eidsvoog · August 17, 2026, 5:21pm

Here’s what appears in the popup.

…and on my MacBook

John_Eidsvoog · August 17, 2026, 5:36pm

Note that I mentioned above that Xojo 2025r3.1 allows me to type my Developer ID into the field (today) and it is accepted. Something about Xojo’s current version thinks it belongs to my wife and my name is not displayed. It leads me to believe it’s not finding existing IDs correctly.

John_Eidsvoog · August 17, 2026, 5:52pm

Here’s the response from Terminal command: security find-identity -v -p codesigning

A927B8FD9995FD3A5C3DB26DD6CA12726A827E80 “Developer ID Application: John Charles Eidsvoog (92N236Y924)”
E473834B4393D950C9ECADF7EC9B012B67D43713 “Apple Development: John Charles Eidsvoog (SD7FC2ZV6J)”

2 valid identities found

Xojo can’t be using this command. What could it be using to find existing identities?