Skip to main content

SDK Configuration

Important
Helpshift’s Legacy SDKs (SDK Version <=7.x.x) reached their end of life on 31 Dec 2022, and end of support on 31 March 2023. Please upgrade to the Latest SDKif you haven't already.

SDK Configuration

Helpshift provides several config options which can be used to customize behaviour of the SDK.

Install Options​

notificationIcon​

By default the application icon is used as the notification icon. You can customize the notification icon using the config in the Install call.

FlagnotificationIcon
ValuesResource id of the icon
DefaultApplication icon

Example :

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetNotificationIcon(Resource.Drawable.Icon)
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.0.0 and above.

largeNotificationIcon​

By default the application icon is used as the notification icon. If you want to specify the large notification icon also to show up in the notification tray, you can specify that using the config in the install call.

FlaglargeNotificationIcon
ValuesResource id of the icon
Defaultnone

Example :

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                   .SetLargeNotificationIcon(Resource.Drawable.LargeNotificationIcon)
                                   .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.0.0 and above.

enableInAppNotification​

If you do not want the in-app notification support provided by the Helpshift SDK, you can set the flag to "no". The default value of this flag is "yes" i.e., in app notification will be enabled.

FlagenableInAppNotification
Values"yes"/ "no"
Default"no"

Example:

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetEnableInAppNotifications(true)
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.0.0 and above.

notificationSound​

By default the default device notification sound is used for helpshift notifications. You can customize the notification sound using the config in the install call.

FlagnotificationSound
ValuesResource id of the sound file.
DefaultSystem notification sound.

Example:

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetNotificationSound(Resource.Raw.notification_sound)
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

  • Available from SDK version 3.0.0 and above

  • Starting from SDK v3.1.0, the sound provided here would only be set for the default notification channel that the SDK creates on its own on Android OS 8.0 & above. This sound can only be set once on the default channel and it won’t change if a different sound resource is passed.

  • If the sound needs to be changed later on, it is recommended to create your own notification channels. Refer this.

Notification channels​

Starting from Android Oreo, Helpshift notifications will create a default channel named In-app Support. If you want to customize the name and description for the default channel, you can do so by using the following resources in your <application project>/Resources/values/strings.xml file:

<string name="hs__default_notification_channel_name">Example Support Name</string>
<string name="hs__default_notification_channel_desc">Example Support Description</string>

If you want to customize the notification channels, you can create your own custom channels and provide their channel IDs using the following config key:

  • supportNotificationChannelId

For Example:

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetSupportNotificationChannelId("supportChannel")
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.0.0 and above.

enableDefaultFallbackLanguage​

FlagenableDefaultFallbackLanguage
values"yes"/ "no"
default"no"

You can enable or disable the SDK default fallback language when showing FAQs using this flag. When set to "no", the Helpshift SDK will not fallback to the default language that is English, when showing FAQs.

Note

This configuration does not apply to the QuickSearch Bot suggested FAQs.

Example:

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetEnableDefaultFallbackLanguage(true)
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.0.0 and above.

Using Custom Fonts​

Step 1: Add the font file to your Assets folder.

Step 2: Pass the font location relative to the Assets folder as follows during installation. If the font file DancingScript-Regular.ttf lies in the fonts folder inside the assets folder, then your path is fonts/DancingScript-Regular.ttf.

Example:

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetFontPath("fonts/DancingScript-Regular.ttf")
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.0.0 and above.

Step 3: Test the font in simulator. Errors in font names are ignored by the SDK —

screenOrientation​

FlagscreenOrientation
valuesenum values for orientation from ScreenOrientation class
defaultScreenOrientation.Unspecified

The screen orientation of Helpshift SDK screens can be fixed by setting the screenOrientation to enum available in the ScreenOrientation class. For example, you may want to fix the orientation to ScreenOrientation.Portrait for mobile users and ScreenOrientation.Landscape for tablet users.

Example:

    using Android.Content.PM;
    .
    .
    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetScreenOrientation((int) ScreenOrientation.Landscape)
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.0.0 and above.

Note

Due to a bug in Android OS 8.0, setting the requested orientation when opening the Helpshift activity causes a crash. This happens only when the targetSDKVersion is greater than 26 and certain android theming flags (mentioned in the bug) are used for the Activity. On Xamarin SDK v3.1.0 & above, calling this API would be a no-op if the android exception is thrown. On Xamarin SDK v3.0.0 & below, as a workaround, apps need to turn off the flags for Helpshift's ParentActivity which will prevent the exception.

enableLogging​

FlagenableLogging
values"yes"/ "no"
default"no"

Upon setting enableLogging to true, Helpshift SDK logs will be generated in the Android logcat. These will be useful for debugging the SDK during integration. Turning on this logging could help the developer resolve common integration issues.

Example:

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetEnableLogging(true)
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.0.0 and above.

disableErrorReporting​

FlagdisableErrorReporting
values"yes"/ "no"
default"no"

Disables reporting of Helpshift SDK’s internal error logs. The Helpshift SDK will collect internal error logs and report them to our systems to ensure that we become aware of runtime crashes and we have enough information to fix them.

Example:

    HelpshiftInstallConfig installConfig = new HelpshiftInstallConfig.Builder()
                                             .SetDisableErrorReporting(true)
                                             .Build();
    HelpshiftApi.HelpshiftCore.Install("<YOUR_API_KEY>",
                                       "<YOUR_COMPANY>.helpshift.com",
                                       "<YOUR_APP_ID>",
                                       installConfig);
Note

Applicable to version 3.3.0 and above.

API Options​

enableContactUs​

FlagenableContactUs
ValuesHelpshiftApi.HelpshiftSupport.CONTACT_US_ALWAYS HelpshiftApi.HelpshiftSupport.CONTACT_US_NEVER HelpshiftApi.HelpshiftSupport.CONTACT_US_AFTER_VIEWING_FAQS HelpshiftApi.HelpshiftSupport.CONTACT_US_AFTER_MARKING_ANSWER_UNHELPFUL
DefaultHelpshiftApi.HelpshiftSupport.CONTACT_US_ALWAYS

The enableContactUs flag will determine whether the Contact Us button is shown. The default value is ALWAYS, with the normal showFAQs call. So if you want to override that you can pass the arguments in a dictionary. This flag has no effect for the ShowConversation API call.

Example:

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetEnableContactUs(HsEnableContactUs.AfterViewingFAQs)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowFAQs(activity, config);
Note

Applicable to version 3.0.0 and above.

gotoConversationAfterContactUs​

Note

This API is now deprecated with Xamarin SDK v3.0.0. Read more about the new conversational experience here

FlaggotoConversationAfterContactUs
Values"yes"/ "no"
Default"no"

The gotoConversationAfterContactUs flag will determine whether the user lands up in the conversation screen after starting a new conversation via "Contact Us". This only makes sense if the enableContactUs flag takes on the default value.

Example:

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetGotoConversationAfterContactUs(true)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowConversation(activity, config);
Note

Applicable to version 3.0.0 and above.

Note

For ShowFAQs, ShowFAQSection and ShowSingleFAQ APIs, setting gotoConversationAfterContactUs makes sense only if enableContactUs is not HelpshiftApi.HelpshiftSupport.CONTACT_US_NEVER.

requireEmail​

Note

This API is now deprecated with Xamarin SDK v3.0.0. Read more about the new conversational experience here

FlagrequireEmail
Values"yes"/ "no"
Default"no"

If requireEmail flag is set to "yes", an e-mail address is required while starting a new conversation. Default value is "no" i.e. e-mail is optional.

Example:

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetRequireEmail(true)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowConversation(activity, config);
Note

Applicable to version 3.0.0 and above.

Note

Once requireEmail flag is set, the SDK will use that value for all new conversations until it is changed again.

hideNameAndEmail​

Note

This API is now deprecated with Xamarin SDK v3.0.0. Read more about the new conversational experience here

FlaghideNameAndEmail
Values"yes"/ "no"
Default"no"

The hideNameAndEmail flag will hide the name and email fields when the user starts a new conversation.

When the flag is set to "yes" the name and email fields will be hidden. If set to "no" the default behaviour will resume.

For example:

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetHideNameAndEmail(true)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowConversation(activity, config);
Note

Applicable to version 3.0.0 and above.

If the requireEmail flag is set to "yes" and email is not available to the SDK, then hideNameAndEmail flag will be ignored.

Interaction with Helpshift settings on agent dashboard​

If "New Issue Forwarding" is ON then this flag will be ignored when name and email are not available to the SDK. You can use the SetNameAndEmail API, to supply the SDK with name and email in this case.

If "Allow anonymous issues" is ON, under app settings in the agent dashboard, then this flag will be ignored.

Note

Once hideNameAndEmail flag is set, the SDK will use that value for all new conversations until it is changed again.

conversationPrefillText​

FlagconversationPrefillText
ValuesNon-empty String

The conversationPrefillText API option will prefill a new conversation description, with the supplied string. This is useful where you might want your users to send you diagnostic information in the conversation description, for example if the app hits an exception, etc.

Example:

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetConversationPrefillText("Pre fill text")
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowConversation(activity, config);
Note

Applicable to version 3.0.0 and above.

Note

The conversationPrefillText option takes effect only for the ShowConversation API.

enableFullPrivacy​

FlagenableFullPrivacy
Values"yes"/ "no"
Default"no"

In scenarios where the user attaches objectionable content in the screenshots, it becomes a huge COPPA concern. The enableFullPrivacy flag will help solve this problem.

If this flag is set to "yes", it enables full privacy controls for the SDK. The user can be disabled from attaching screenshots and sending personally identifiable information in meta-data. This helps developers ensure full COPPA compliance.

To send personally identifiable information through custom meta-data, the information must be added inside a dictionary with a "private-data" key. If this flag is set to "yes", the following data will be removed when the user starts a new conversation.

  1. Map with "private-data" key inside custom meta-data.
  2. Country code.
  3. Carrier name.

Example:

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetEnableFullPrivacy(true)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowFAQs(activity, config);
Note

Applicable to version 3.0.0 and above.

Note
  1. Once the enableFullPrivacy flag is set, the SDK will use that value for all further sessions until it is changed again.
  2. If the enableFullPrivacy flag is set, for SDK versions 2.3.1 or earlier, the email requirement is always set to optional. i.e. even if requiredEmail is true; enableFullPrivacy will override it and set email requirement as optional.
  3. If the enableFullPrivacy flag is set, for SDK versions 2.4.0 or later, the user's 'email and name will not be collected and the fields will be hidden. enableFullPrivacy flag will override all other flags pertaining to name and email field.
  4. For Xamarin SDK v3.0.0 and above, this flag is ignored in the flows created to show Dynamic forms. The following flows do not honor this flag:
    • ConversationFlow
    • FAQsFlow
    • SingleFAQFlow
    • FAQSectionFlow

showSearchOnNewConversation​

Note

This API is now deprecated with Xamarin SDK v3.0.0. Read more about the new conversational experience here

FlagshowSearchOnNewConversation
Values"yes"/ "no"
Default"no"

If showSearchOnNewConversation flag is set to "yes", the user will be taken to a view which shows the search results relevant to the conversation text that he has entered upon clicking the 'Send' button. This is to avoid tickets which are already answered in the FAQs. The user will still be able to start a new conversation with the same text. He can also go through one of the FAQs and find a solution to his query, and exit the session without submitting a ticket.

Default value is "no", ie., this feature will not be enabled unless you explicitly pass "yes" for this flag.

Example :

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetShowSearchOnNewConversation(true)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowConversation(activity, config);
Note

Applicable to version 3.0.0 and above.

showConversationResolutionQuestion​

For v3.0+​

This SDK configuration is deprecated with v3.0+ and default value will be treated as False.

If you want to use this feature, you can turn the feature on and off ("Resolution Question") from the Settings > App settings > In-App Configuration page.

{" "}

For Older SDK versions 2.6 and below, please read the following:​

FlagshowConversationResolutionQuestion
Values"yes" / "no"
Default"yes"

By default the Helpshift SDK will show the conversation resolution question to the user, to confirm if the conversation was resolved. If you want to disable the conversation resolution question, set showConversationResolutionQuestion to false, On resolving the conversation from the admin dashboard will now take the user directly to the "Start a new conversation" state..

Default value is yes, ie., this feature will not be disabled unless you explicitly pass no for this flag.

Example :

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetShowConversationResolutionQuestion(true)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowConversation(activity, config);
Note

Applicable to version 3.0.0 and above.

customContactUsFlows​

FlagcustomContactUsFlows
ValuesList of Flows. See the example below to create flows.
DefaultThere is no default value for this configuration.

This configuration allows you to override the Contact Us buttons inside the Helpshift SDK and show Guided Issue Filing when a user taps on the Contact Us buttons.

Example :

Let’s say you want the users to see a particular FAQ section, a single FAQ and 2 different Contact Us flows with different prefill texts when they tap the Contact Us buttons within the Helpshift SDK. In this case, you would configure the showHelp button (a button which triggers Helpshift SDK) in the following way :

    FAQSectionFlow faqSectionFlow = new FAQSectionFlow("1509", "FAQ section");
    SingleFAQFlow singleFAQFlow = new SingleFAQFlow("2998", "FAQ");
    HelpshiftAPIConfig conversationConfig1 = new HelpshiftAPIConfig.Builder()
                                              .SetConversationPrefillText("Contact Us about our app")
                                              .Build();
    ConversationFlow conversationFlow1 = new ConversationFlow("Converse 1", conversationConfig1);
    HelpshiftAPIConfig conversationConfig2 = new HelpshiftAPIConfig.Builder()
                                     .SetConversationPrefillText("Contact Us about in-app purchases")
                                     .Build();
    ConversationFlow conversationFlow2 = new ConversationFlow("Converse 2", conversationConfig2);
    IList<Flow> flows = new List<Flow>() { faqSectionFlow, singleFAQFlow, conversationFlow1,
                                           conversationFlow2 };

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetCustomContactUsFlows(flows)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowFAQs(activity, config);
Note

Applicable to version 3.0.0 and above.

Anytime the Helpshift SDK is presented via showHelp with this configuration, the Contact Us buttons in the SDK will redirect to Guided Issue Filing with the flows provided in the customContactUsOptions list.

Once a particular flow is selected, the subsequent Contact Us buttons will redirect to nested customContactUsFlow if configured else to default contact us screen.

Custom flows can be nested by passing another custom flows configuration while creating a flow.

Example :

Let’s say you want to configure singleFAQFlow in the above example to show showConversationFlow1 and showConversationFlow2 through the Contact Us buttons inside it. In this case, you would configure the showHelp button (a button which triggers Helpshift SDK) in the following way :

    HelpshiftAPIConfig conversationConfig1 = new HelpshiftAPIConfig.Builder()
                                              .SetConversationPrefillText("Contact Us about our app")
                                              .Build();
    ConversationFlow showConversationFlow1 = new ConversationFlow("Converse 1", conversationConfig1);
    HelpshiftAPIConfig conversationConfig2 = new HelpshiftAPIConfig.Builder()
                                     .SetConversationPrefillText("Contact Us about in-app purchases")
                                     .Build();
    ConversationFlow showConversationFlow2 = new ConversationFlow("Converse 2", conversationConfig2);
    IList<Flow> nestedFlows = new List<Flow>() { showConversationFlow1, showConversationFlow2 };
    HelpshiftAPIConfig singleFAQConfig = new HelpshiftAPIConfig.Builder()
                                             .SetCustomContactUsFlows(nestedFlows)
                                             .Build();
    SingleFAQFlow singleFAQFlow = new SingleFAQFlow("2998", "FAQ", singleFAQConfig);
    FAQSectionFlow faqSectionFlow = new FAQSectionFlow("1", "FAQ Section");
    IList<Flow> flows = new List<Flow>() { singleFAQFlow, faqSectionFlow };

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetCustomContactUsFlows(flows)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowFAQs(activity, config);
Note

Applicable to version 3.0.0 and above.

With this configuration, the Contact Us buttons in singleFAQFlow View will redirect to Guided Issue Filing with showConversationFlow1 and showConversationFlow2.

showConversationInfoScreen​

FlagshowConversationInfoScreen
Values"yes"/"no"
Default"no"

The showConversationInfoScreen flag will determine if the user can see the Conversation info on the conversation feed. If set to true, the Conversation ID (Issue ID) will be shown in conversation feed.

Example :

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetShowConversationInfoScreen(true)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowConversation(activity, config);
Note

Applicable to version 3.0.0 and above.

Note

The Conversation ID (Issue ID) will only be visible when a conversation is actually created for support teams and Automations / Agents can act on it. (This is after QuickSearch Bot (if configured) and Identity Bot (if configured) complete their tasks.)

enableTypingIndicator​

FlagenableTypingIndicator
Values"yes"/"no"
Default"no"

A graphical indicator is shown to the end user if an Agent is currently replying to the same Conversation. The "enableTypingIndicator" flag will enable/disable the aforementioned indicator.

Note

This SDK configuration has been deprecated since this configuration has shifted to the In-App SDK configuration page. (Settings > App settings)

For Xamarin SDK v3.0 and above, the typing indicator configuration ("Show Agent typing Indicator") is now part of the In-app SDK configurations page.

If this configuration is turned ON from the configurations page OR if the SDK configuration is used, then the typing indicator will shown to the end users.

Example :

    HelpshiftAPIConfig config = new HelpshiftAPIConfig.Builder()
                                             .SetEnableTypingIndicator(true)
                                             .Build();
    HelpshiftApi.HelpshiftSupport.ShowFAQs(activity, config);
Note

Applicable to version 3.0.0 and above.

Note

The typing indicator will only be enabled for all the new issues filed using SDK v2.4.0+

Minimum issue description length​

You can set the minimum length requirement of text for the user while filing the new issue using the integer resource hs__issue_description_min_chars. Its default value is set to 1 for all languages and it can be configured per language. If the number of characters is less than the defined minimum length requirement then an error is displayed to the user.

Example :

For Korean language, if you want to have minimum length as 5 characters and 10 characters for all other languages, do the following:

Put the following integer resource in integers.xml of values-ko resource directory

<integer name="hs__issue_description_min_chars">5</integer>

and the following integer resource in integers.xml of values resource directory

<integer name="hs__issue_description_min_chars">10</integer>

Configuration Summary​

Configuration / APIshowFAQsshowFAQSectionshowSingleFAQshowConversation
enableContactUsSupportedSupportedSupportedNot Supported
enableFullPrivacySupportedSupportedSupportedSupported
showConversationResolutionQuestionSupportedSupportedSupportedSupported
customContactUsFlowsSupportedSupportedSupportedNot Supported
showConversationInfoScreenSupportedSupportedSupportedSupported
enableTypingIndicatorSupportedSupportedSupportedSupported

Flexible permissions adaptive to Android M and older versions​

Starting from Android 6.0 (API level 23), users grant permissions to apps while the app is running, not when they install the app. The storage permissions can be removed from AndroidManifest.xml in case you do not want to use them. You can remove the WRITE_EXTERNAL_STORAGE permission with the following line in your final AndroidManifest.xml file:

<uses-permission android:name=“android.permission.WRITE_EXTERNAL_STORAGE” tools:node=“remove”/>

The Helpshift SDK has 4 features that require storage permissions. The following is the behavior for these 4 features based on whether the permission is present in AndroidManifest.xml or not.

User side attach screenshot flow​

Starting from Helpshift SDK v2.5.0, user's screenshots can be attached independent of the storage permission being present in the manifest.

Agent side attachment downloads​

Storage Permission StatusAPI 15 to 22API 23 and above
Permission declared in manifestWorks as normal (attachments are downloaded and rendered in chat screen by sdk's own download manager)User granted the permission
  • Works as normal

User did not grant the permission
  • User is shown permission dialog. If user denies the permission then show a requirement description msg with intent to launch the app settings page (User can't download the attachment unless he grants the permission)
Permission not declared in manifestUri will be passed to system provided download service and it will start download with progress bar in notification drawer. Helpshift Sdk will just show the toast indicating that download has started. User is allowed to trigger the download multiple times. Sdk would not show any progress in the chat screen.Uri will be passed to system provided download service and it will start download with progress bar in notification drawer.Helpshift Sdk will just show the toast indicating that download has started. User is allowed to trigger the download multiple times. Sdk would not show any progress in the chat screen.

Image caching in single question screen​

Storage Permission StatusAPI 15 to 18API 19 and above
Permission declared in manifestWorks as normal (images are cached)Works as normal.
Permission not declared in manifestCaching will not work. Image will be reloaded every time the user visits the particular single question screenWorks as normal.

Profile persistence across uninstalls for multi login​

Storage Permission StatusAPI 15 and above
Permission declared in manifestUser profile will be persisted across uninstalls
Permission not declared in manifestUser profile will not be persisted across uninstalls