Skip to content

Commit 6184338

Browse files
authored
Merge pull request #6231 from segmentio/niall/mobile_proxy
Add Proxy info for mobile libraries
2 parents c9d5ac9 + 904290b commit 6184338

File tree

3 files changed

+10
-0
lines changed

3 files changed

+10
-0
lines changed

src/connections/sources/catalog/libraries/mobile/apple/index.md

+3
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,9 @@ Analytics for Swift is built with extensibility in mind. Use the tools list belo
159159
- [Destination Filters](/docs/connections/sources/catalog/libraries/mobile/swift/swift-destination-filters)
160160
- [Code samples](/docs/connections/sources/catalog/libraries/mobile/swift/swift-samples)
161161
162+
## Proxying events
163+
If you proxy your events through the `apiHost` config option, you must forward the batched events to `https://api.segment.io/v1/b`. The `https://api.segment.io/v1/batch` endpoint is reserved for events arriving from server-side sending, and proxying to that endpoint for your mobile events may result in unexpected behavior.
164+
162165
> warning ""
163166
> If you are using the Analytics iOS (Classic) SDK, you can find [the documentation here](/docs/connections/sources/catalog/libraries/mobile/ios). Many of the features available in the Analytics-Swift SDK are not available in the Analytics iOS (Classic) SDK.
164167

src/connections/sources/catalog/libraries/mobile/kotlin-android/kotlin-android-faq.md

+3
Original file line numberDiff line numberDiff line change
@@ -82,3 +82,6 @@ When you successfully package a plugin in device-mode, you will no longer see th
8282

8383
## What is the instanceId set in context?
8484
The instanceId was introduced in [V 1.10.1](https://github.com/segmentio/analytics-kotlin/releases/tag/1.10.1){:target="_blank"} and correlates events to a particular instance of the client in a scenario when you might have multiple instances on a single app.
85+
86+
## If I use a proxy, what Segment endpoint should I send to?
87+
If you proxy your events through the `apiHost` config option, you must forward the batched events to `https://api.segment.io/v1/b`. The `https://api.segment.io/v1/batch` endpoint is reserved for events arriving from server side sending, and proxying to that endpoint for your mobile events may result in unexpected behavior.

src/connections/sources/catalog/libraries/mobile/react-native/index.md

+4
Original file line numberDiff line numberDiff line change
@@ -751,5 +751,9 @@ segmentClient.userInfo.set((currentUserInfo) => {
751751
});
752752
```
753753
754+
### If I use a proxy, what Segment endpoint should I send to?
755+
If you proxy your events through the `proxy` config option, you must forward the batched events to `https://api.segment.io/v1/b`. The `https://api.segment.io/v1/batch` endpoint is reserved for events arriving from server side sending, and proxying to that endpoint for your mobile events may result in unexpected behavior.
756+
757+
754758
## Changelog
755759
[View the Analytics React Native changelog on GitHub](https://github.com/segmentio/analytics-react-native/releases){:target="_blank"}.

0 commit comments

Comments
 (0)