I am sure this has been brought up before, but there have been multiple times where I have needed to add a hardware feature to an application that will be ran on iOS devices (NFC for example) and it makes the development process in FlutterFlow pretty painful.
Apple requires you to add the capability for NFC in Xcode for your it to work; however, since FlutterFlow overwrites the Xcode capabilities everytime you deploy to a test device (in the ff platform) it leads to a really janky workflow where I am having to bounce in and out of VSCode just to run the application locally. This also kills 1-click deploy and requires you to use Github instead.
Both of these are not platformbreaking issues and obviously can be worked around, but considering so many application will rely on hardware feature that requires adding a capability on the iOS side at some point, this seems like a bit of an oversight?
It would be nice if we could select the capabilities that we would like FlutterFlow to avoid overwriting (or just the ones that we want it to add each time) so that we can continue to stay efficient and using the FlutterFlow platform testing options as well as 1-click deploy.
Thoughts on this?