Skip to content

Commit 4fd889d

Browse files
authored
Merge pull request #147 from segmentio/repo-sync
repo sync
2 parents b051ca0 + 3243864 commit 4fd889d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ strat: android
1010
- The `writekey` might change when you make changes to the source from the Segment web app.
1111
- If the `writeKey` you entered is something other than a string or an empty string your app may crash
1212
- If the `writeKey` you entered is a valid form but not the correct writeKey for your specific source, you won't see an error response. Segment receives the data, but cannot route it to your source (debugger).
13-
3. [Enable logging](/docs/connections/sources/catalog/libraries/mobile/android/#debugging) to confirm if call is being sent to Segment
13+
3. [Enable logging](/docs/connections/sources/catalog/libraries/mobile/android/#adding-debug-logging) to confirm if call is being sent to Segment
1414

1515

1616
## No events in my destinations
@@ -29,7 +29,7 @@ If you still don't see data getting to your destination, continue debugging base
2929

3030
Inspect one of your data payloads. If you are using device-mode for a specific destination, the value of that integration should be set to `false` in the `integrations` object. That means that the data is being sent from the device directly to the destination's API endpoints, and not through Segment's servers. This is expected if you chose to use a device-mode destination's SDK with Segment's during installation.
3131

32-
Enable verbose [logging](/docs/connections/sources/catalog/libraries/mobile/android/#debugging) and trigger the call in question. You should see a call to Segment, and one going to the partner SDK. It will show you exactly which partner method was invoked and the arguments it was invoked with!
32+
Enable verbose [logging](/docs/connections/sources/catalog/libraries/mobile/android/#adding-debug-logging) and trigger the call in question. You should see calls to Segment and the partner SDK that show the partner method that was invoked and the arguments with which it was invoked.
3333

3434
## Debugging Cloud-mode Destinations
3535

0 commit comments

Comments
 (0)