You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DevRev SDK allows you to configure the theme dynamically based on the system appearance, or use the theme configured on the DevRev portal. By default, the theme will be dynamic and follow the system appearance.
229
229
230
-
```swift
230
+
```typescript
231
231
DevRev.setPrefersSystemTheme(value: boolean)
232
232
```
233
233
234
-
## Analytics
234
+
## Analytics
235
235
236
236
The DevRev SDK allows you to send custom analytic events by using a properties map. You can track these events using the following function:
@@ -273,14 +273,14 @@ The session recording feature includes the following methods to control the reco
273
273
|`DevRev.stopRecording()`| Stops the session recording and uploads it to the portal. |
274
274
|`DevRev.pauseRecording()`| Pauses the ongoing session recording. |
275
275
|`DevRev.resumeRecording()`| Resumes a paused session recording. |
276
-
|`DevRev.processAllOnDemandSessions()`| Stops the ongoing session recording and uploads all offline sessions on demand, including the current one.|
276
+
|`DevRev.processAllOnDemandSessions()`| Stops the ongoing user recording and sends all on-demand sessions along with the current recording. |
277
277
278
278
### Session properties
279
279
280
280
You can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a map of string values.
The DevRev SDK offers automatic screen tracking to help you understand how users navigate through your app. Although view controllers are automatically tracked, you can manually track screens using the following method:
329
329
330
330
```typescript
331
-
DevRev.trackScreen(name: string)
331
+
DevRev.trackScreenName(name: string)
332
+
```
333
+
334
+
### Screen transition management (Android only)
335
+
336
+
The DevRev SDK allows tracking of screen transitions to understand the user navigation within your app.
337
+
You can manually update the state using the following methods:
338
+
339
+
```javascript
340
+
// Mark the transition as started.
341
+
DevRev.setInScreenTransitioning(true)
342
+
343
+
// Mark the transition as ended.
344
+
DevRev.setInScreenTransitioning(false)
332
345
```
333
346
334
347
## Push notifications
@@ -350,7 +363,7 @@ Push notifications require that the SDK has been configured and the user has bee
350
363
The DevRev SDK offers a method to register your device for receiving push notifications. You can register for push notifications using the following method:
On Android devices, the `deviceToken` should be the Firebase Cloud Messaging (FCM) token value, while on iOS devices, it should be the Apple Push Notification Service (APNs) token.
@@ -362,12 +375,11 @@ If your app no longer needs to receive push notifications, you can unregister th
362
375
Use the following method to unregister the device:
363
376
364
377
```typescript
365
-
DevRevSDK.unregisterDevice(deviceID: string)
378
+
DevRev.unregisterDevice(deviceID: string)
366
379
```
367
380
368
381
The method requires the device identifier, which should be the same as the one used when registering the device.
369
382
370
-
371
383
### Processing push notifications
372
384
373
385
#### Android
@@ -377,7 +389,7 @@ On Android, notifications are implemented as data messages to offer flexibility.
377
389
To process the notification, use the following method:
On iOS devices, you must pass the received push notification payload to the DevRev SDK for processing. The SDK will then handle the notification and execute the necessary actions.
0 commit comments