I recently started having an issue with my TestFlight builds. In the past, if I built/distributed an app for TestFlight, the AppConnect group automatically received the builds and were able to install the on their devices. When I look in AppConnect, I can see the AC (AppConnect) group shown as a tester and that group shows the users I am expecting in them. The users are receiving an email from TestFlight saying the build is ready. However, when we go into TestFlight, it doesn't show the update being available for that new build. What I have done as a work-around is added my AppConnect users to separate group and add them as testers each time I release a build to TestFlight. Has anyone seen this or can they point out why this may be happening?

I inadvertently used the build number for the version number. How can I remove these versions/builds so that i can get back to my normal versioning scheme? I am now stuck using a version number of 110 instead of a build number of 110.

I have an app that I have been building with xCode without issue. The app is developed in Flutter. I am attempting to build this on an M1 Macbook Pro (and this is not the first time I build this app on my M1). Recently, however, I have run into a problem with my build. The specific error I am getting is "firebase_auth" not found. I have been using firebase_auth for several iterations of my app so it isn't anything new that I have introduced. I have seen many reports of this issue on StackOverflow and I have followed them (cleaning my project folder, flutter clean, removing pod files and recreating, etc.). Nothing has worked...I just can't get a clean build. I can, however, run a build from the command line using this command: flutter build ipa --flavor prod --export-options-plist ./assets/config/exportOptions.plist --dart-define=ENV=prod. The problem only occurs when I run my build inside of xCode. Very frustrating. Any suggestions you might have would be greatly appreciated.