runner.xcworkspace versioning & HealthKit Signing Issues when using Local Run

Project Settings

When I am using local run mode from the FlutterFlow desktop app, I continuously have to re-add the HealthKit capability in order to test my HealthKit related features.

I also get the error shown in this other blog post every time I do local run mode or reload the app from flutter flow. https://community.flutterflow.io/ask-the-community/post/bug-using-local-run-OOE7wbwNKNQfT8X

I see from the recommendation is to "Use version on Disk", which I do and it closes/re-opens xcode. However, any time I reload from FlutterFlow local run, I have to go thru this process as well as adding HealthKit signing capability again.

I wonder if these two issues are somehow related to a step I missed when setting up xcode.

1) Should I be able to make a setting change (FlutterFlow/xCode/pods file/etc..) that keeps HealthKit signing capability enabled?

2) Should I be able to make a setting change that (FlutterFlow/xCode/pods file/etc..) that avoids the runner.xcworkspace versioning issue I am seeing?

What have you tried so far?

I have tried selecting "Keep Xcode Version and "Use Version on Disk". Selecting "Use Version on Disk" and then going to xcode (once it re-opens) and selecting product>run allows me to run the app on my iPhone with the HealthKit features enabled. When I select "Keep Xcode Version", the HealthKit features seem to never be able to work and I get a HealthKit permissions error when I run.

Did you check FlutterFlow's Documentation for this topic?
Yes
4
5 replies