helpshift / helpshift/CocoaPods

closeHelpshiftSupportSession not working?

Open
#6 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Hey there,

Either I'm not understanding what a "Helpshift session" is, or `HelpshiftSupport.closeHelpshiftSupportSession()` doesn't work.

Am I correct that this line of code should basically "cancel" any outstanding conversations? In other words, it should have similar behaviour as if I was to press the "Reject" or "Resolve" button on my Helpshift Issues Dashboard, right? Close the existing conversations (if any), so the user can start a new one.

That doesn't seem to work for me. I'm doing the following:

```
HelpshiftSupport.closeHelpshiftSupportSession() // close any existing conversations TODO: doesn't seem to do what you think it does?
HelpshiftSupport.showConversation(vc, withOptions: getOptionsForDeletingAccount(providedFeedback)) // create the final conversation/feedback screen with prefilled text
```

I'm trying to open a new conversation screen with pre-filled text that the user entered in the previous screen. I want to collect any feedback on how I can improve my app, before they delete their user account for whatever reason. I want to know that reason.

However if a user already has an open conversation, it just opens the messages screen. It doesn't cancel anything and neither does it pre-populate the textfield.

It only works if I reject/resolve any existing issues from the dashboard and then try to call the above two lines of code. Only then I see a brand new conversation screen with my text pre-filled.

Any ideas what I'm doing wrong? How is `HelpshiftSupport.closeHelpshiftSupportSession()` supposed to work?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the sequence using HelpshiftSupport.closeHelpshiftSupportSession() followed by HelpshiftSupport.showConversation(vc, withOptions: getOptionsForDeletingAccount(providedFeedback)). Compare the result when an existing conversation is open with the result after rejecting or resolving it in the Helpshift Issues Dashboard. Done means the session behavior and prefilled-text behavior are understood and the issue has a documented resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.