Having same issue with macOS 11. Tried to remove profile, no joy. Signed out and in to App Store, no joy. Reinstalled macOS 11 "release", no joy cleared every cache folder and file I could find (OMG cleaned a lot of macOS cache corruption), no joy (now random cleaning) rebuilt Launch Services, no joy Tried to update Locate database, no joy Tried to update WhatIs database, no joy tried sudo softwareupdate --clear-catalog, "Catalog management is no longer supported.", no joy sacrificed a chicken, paprikash!😋, Mac still no joy Going to turn off SIP next and re-run cleaning so my old utils can clean out what Apple thinks is bug free Apple stuff. Clearly it ain't bug free. Chicken Kiev next.

I have two main Apple IDs because Apple forced me to create several. My receipt for the developer dues are not in any of them. Why on earth Apple thought it was cool to only let you see the last 90 days on the web interface and force you to go to a mobile device to dig farther back is a mystery.

OMG that was hard. The "From" is your_order_US[@]orders[.]apple[.]com and will contain the text "Apple Developer Program - Membership for one year". (sorry, you have to remove the brackets because Apple won't let me post their own e-mail address here 😡) The purchase does not show up in the purchase history for 2022, 2021, or 2020 on the mobile device (the only way you can view purchase history). A major web retailer not being able to provide you with online receipt history... Ahem, Amazon?

iPad 12.9" 3rd gen. iPad OS 16.2. Connecting iMac 24" M1 to iPad triggers no "trust this computer" dialog. Connection cable is a Thunderbolt 4 cable. As it turns out, I see that there is no "Developer Mode" in Settings -> Privacy & Security -> Developer Mode (at the bottom on right). This is presumably because of a corporate MDM setting (unconfirmed) removing the ability to get into Developer Mode. Your mileage may vary. Developer Mode: https://developer.apple.com/documentation/xcode/enabling-developer-mode-on-a-device

The best way in Xcode to do this is: (using your example) Open Preferences Click "Locations" then the "Custom Paths" tab Click the "+" sign at the bottom left enter "gst" as the "Name" (no quotes) enter "GST Headers" as the "Display Name" (no quotes) enter the path name* to your gst folder as the "Path" In the Finder, right-click / option click / two-finger click the "GST" folder, then hold the option and you will see "Copy" change to "Copy GST as Pathname". Do that and use paste it in for step 6 Ok no you have the first part. You created an Xcode system variable. The next part is to reference the Xcode variable in your project build settings by: Open the project Click on the folder button under the window close button Click on the blue project button/icon under the folder button In the column that appears to the right, click on another blue project button/icon In the row of tabs/buttons slightly higher and to the right, click on the "Build Settings" button/tab in the "Filter" text entry slightly lower than the tabs to the far right, enter "Search" without quotes below you should see "Search Paths" with a chevron, click the chevron if it is pointed at the word "Search" and it opens up the options below "Search Paths" you should see "System Header Search Paths". again click the chevron if it is pointed at the word "Search" and it opens up the options Hover over the word "Debug" below "System Header Search Paths" and a grey "+" button thing will show to the right, click the "+" button "Any Architecture/Any SDK" will appear and your cursor will be in a text entry. Type "$gst" without quotes Hover over the word "Release" below "Debug" and a grey "+" button thing will show to the right, click the "+" button "Any Architecture/Any SDK" will appear and your cursor will be in a text entry. Type "$gst" without quotes Now you should be able to put... #include <gst/gst.h> or maybe #include <gst.h> ... in your code and have it compile. Unfortunately Xcode has some problems with the basics of what an IDE should do so you may have to fiddle with the pathname vs what you put between the <>. Be aware that you also may need to close all projects and quit between edits of the "System Header Search Paths" and the "Custom Paths" to get Xcode to recognize changes. You may also have to delete the "Custom Paths" and re-enter it to get Xcode to recognize changes. Isn't that easier than it was in 1991 with drag and drop of a folder into "system headers" and "project headers" in CodeWarrior and MPW? </sarcasm mode>

Small update. In making this work, you may find it valuable to open the project bundle (directory, not a file) in BBEdit, then open the project.pbxproj inside and look for where Xcode is putting the reference to your "Custom Location". My custom location is named $C0re so it is easy to find. I found it very handy to be able to delete any line with the Custom Location generated into it by Xcode to force Xcode to update and to clean up the GUI mistakes in generating the lines in the project.pbxproj file. There is some kind of caching going on and you may not see the change you apply via Xcode to the "System Header Search Paths" in the actual file showing simultaneously in BBEdit until you command-s the project files in Xcode. You would think that quitting Xcode would commit the changes to the project file but it did not seem to do so sometimes. (Xcode's caching system is problematic at best) It took a couple of hours but now I am able to use #include <C0re/C0reTypes.h> in my project. Again so glad we advanced past that primitive old drag and drop thing 🙄

Same issue today with a tester that is from a testing company that has been working with us for years. This just started in June for us. For us the key is that it was “revoked” yet we did not revoke it and there is no appearance in the AppStoreConnect of revocation.

Perhaps what is worse is when they reply back and ask you for additional files ... such as exactly the files you sent in the bug report. I suspect that the support staff are under funded, over worked, and generally ignored when they report issues to the development team. When you can easily google a problem that existed 7 years ago and you report it 4 years in and it takes Apple 3 years to address it, there is something rotten with the process in Apple.

Like many Xcode defects, this has been around for a while. If you are reading this now, consider yourself lucky you have not hit this before. See Stack Overflow for more bread crumbs, unfortunately no root cause hence no reliable workaround yet. https://stackoverflow.com/questions/52421999/xcode-10-command-codesign-failed-with-a-nonzero-exit-code