Merge pull request #6142 from segmentio/joeynmq-patch-2

Add FAQ about loading multiple writeKeys for iOS

Author: cmastr

src/connections/sources/catalog/libraries/mobile/ios/ios-faqs.md

@@ -28,6 +28,14 @@ Once you install the framework, import the header file and install as described
 If you choose not to use a dependency manager, you must manually keep files up-to-date with regularly scheduled, manual updates.
 
 
+## Can I initiate multiple `writeKey`s for a single iOS project?
+No, Segment doesn't support sending events to multiple `writeKey`s for a single iOS project post-initialization. You can conditionally set the `writeKey` based on an environment variable. For example:
+```objc
+let writeKey
+ENV == 'production' ? (writeKey = 'A') : (writeKey = 'B')
+```
+
+
 ## Should I include each destination's native SDK in my project?
 
 No. Don't include destination-native SDKs manually for a service Segment supports. Instead, bundle the destination's Segment-integration SDK.
@@ -258,4 +266,4 @@ If you are tracking App Clips using iOS or Swift libraries, there is a chance th
 
 ## Why am I seeing a value of -- set for the network carrier?
 
-With iOS [16.4](https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-16_4-release-notes#Core-Telephony){:target="_blank"}, Apple deprecated the method to return the network carrier. The iOS library can no longer return a valid value for the network carrier on devices using iOS 16.4 or later. As a result, you will likely see `--` set for the `context.network.carrier` field.
+With iOS [16.4](https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-16_4-release-notes#Core-Telephony){:target="_blank"}, Apple deprecated the method to return the network carrier. The iOS library can no longer return a valid value for the network carrier on devices using iOS 16.4 or later. As a result, you will likely see `--` set for the `context.network.carrier` field.