I am adding Internal testers to a TestFlight build, and the invite email is being sent to two of us, but not a third tester that I have invited. Next to their name, it is showing "No Builds Available". They would be a new tester for us, but they are not receiving the invite email. The build is still waiting on review, but Internal Testers should have access to it without review, correct? See the image below. TestFlight is incredibly frustrating.

I successfully distributed my app from my XCode build using a build Archive and the XCode tools to upload the build to App Store Connect. However, the build is not showing up under my TestFlight builds, and I was wondering how long this typically takes? I have distributed my app in a different way in the past and want to start using XCode to do so. Is there typically a delay between when the build successfully sends from XCode to when it actually shows up (not processing) in TestFlight?

I am using Codemagic, through a low-code tool, to deploy my app to the App Store. It has worked great up until a few days ago when the deployment stopped working. Their support suggested deleting and re-adding my app's Identifiers (the app is already published and being used). However, after searching around, it appears these IDs cannot be re-used, specifically the Bundle ID that is associated with the Developer ID, even if that Developer ID is deleted. Is that true? I am having trouble fully understanding the differences between Certificates and Identifiers, but it is okay to delete an ID and re-add the exact same information (Bundle ID, Description, ect.)? Also, do Identifiers expire like Certificates do?

I received an email from Apple saying that my iOS Distribution Certificate will expire in 30 days. When I went to the Developer Portal I also saw that my personal Development certificate will also expire in 30 days. However, the docs are very confusing and most of the answers online on how to fix this are very old. So the questions I have are: I am using XCode to 'Automatically manage signing'. Does this mean that it automatically renews these certificates when they go to expire? Or does this have anything to do with managing the expiration of these? Does it regenerate one of the certs and not the other? It is very unclear what exactly the automatic managing actually does in this situation. If XCode does not automatically renew these certs, what is the proper procedure in doing so that will not impact development and updates sent to the App Store? Should I generate new certs for both iOS Distribution and Development before I revoke the old ones? Or revoke the old ones first and then regenerate new ones? Again, vague on the procedure. These certs are being used for PushNotification profile and keys, which also appear to expire in the Developer portal. Is there anything that needs to be done with these or does XCode also take care of this? Is there a way (either in XCode or the Developer Portal) to see which certs are actually being used and which ones are stagnant (may have been probably generated for testing purposes)? Again, it is really hard to determine which certs I need to worry about expiring and which ones aren't even being used. Thanks for your help.