I thought that the issue would be the "Archives are not showing up on Organizer window" one. After calling on Product > Archive, it will say it has finished successfully, and I can find a folder with the app name, date, and time of said "successful" run. However, the issue at hand seems to be even bigger: when I try to open the path in Xcode/Archives, it tells me that the archive may be "corrupt or unreadable." Overmore, I have done what old guides and stack overflow posts have said regarding this issue (such as https://developer.apple.com/library/archive/technotes/tn2215/_index.html#//apple_ref/doc/uid/DTS40011221-CH1-XCODE_SUCCESSFULLY_ARCHIVED_MY_APPLICATION__BUT_THE_ARCHIVES_ORGANIZER_DOES_NOT_LIST_MY_ARCHIVE) This all happened after I updated Xcode (I had to because it wasn't letting me test on my connected device). Any help resolving this issue is appreciated.

My app has it's debug and release schemes. A client had a specific request which meant adding a couple of Swift packages that we only use with said client, and we proceed to install the app directly on their devices; however, on our repository we've been managing this request in its own branch, planning to eventually merge it to the development and master branches, and I am unsure of what to do regarding the client's package dependencies. Therefore, is there a way to manage which package dependencies to include when publishing to the App Store? Or is this an all or nothing situation?