Code sign causes issue with macOS 11 beta 8?

[leotumwattana]

I updated to macOS 11 beta 8 and it seems after code signing Xcode I will no longer be able to sign into my developer account with the following error:

Anyone else facing this issue? Apple locking things down on the latest beta?

[ldakhoa]

I have the same problem, currently running Xcode 12.0 GM, macOS 11 beta 8

[qiudaomao]

Same here, we may need keep two Xcode..

[ldakhoa]

In my case, I have created a new certificate then resign again, and it works.

[leotumwattana]

I did the new certificate thing. Works for a little while and then that warning reappears.

Then tried two Xcode 12 beta 6 where I renamed one to be called XcodeVim. If both are open, then sometimes compiler will error out.

Right now using Xcode 12.2 beta to compile and Xcode 12 beta 6 for Vim and it seems to be working well enough. I changed the theme on Xcode 12.2 so it's easier to tell which Xcode I'm looking at. 🤣

[jooyyy]

I certainly sure about that Xcode Version 12.0.1 (12A7300) will cause the mentioned problem, and i'll try 12.2 beta.

[shinriyo]

Can you put Xcode 12 label on Labels?

[gmedori]

+1 to this issue. would love to see this fixed so I can test on device.

[iT-Boyer]

+1 to this issue.

[travisjayday]

Same here +1. Apple's being wack.

[water-su]

Is there any way to publish XVim2 so that we don't have to re-sign xcode and also able to use XVim2 on xcode?
Looks like the re-sign xcode workaround is not ok on bigsur now. 😢

[sealedace]

My solution is keeping an original copy of Xcode. Can't live without vim...😂

[jhirsh]

+1 issue (Big Sur 11.1, Xcode 12.3/12.4 Release Candidate)

@sealedace can you specify your solution in greater detail? I can live without vim in XCode, but am unhappy doing so 😰

[sealedace]

@jhirsh
The fact is, you will not be able to sign in your developer account after code signing Xcode.
So you have to keep an original copy of Xcode to make your developer account works. Then do your coding with the resigned one... 😄