Run the same problem. My solution was to create separate build targets for QA and production, use pre-processor macros for specific target settings in the code and two separate plist files for things like facebook application id, package ids (you can specify which object to create a plist file using information about project settings).
The same thing with GA - 2 array files for each purpose and avoiding a name conflict (because if you change the plist name from GoogleService-Info, the application crashes) - just put your QA plist in a separate folder, it will work anyway just fine from there.
Do not interfere with targeted membership for you :)
source share