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
I have been using the version of nuget package Jira.SDK 1.2.25 and is working fine for us, all we are doing is passing a jql and getting the issues list. but not sure what happened, am started to get the following error when SearchIssue method is called
"Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
Source=Newtonsoft.Json
from stack trace it is coming from
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonTextReader.Read()
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
at Jira.SDK.JiraClient.DeserializeIssues(String json)
at Jira.SDK.JiraClient.GetIssues(String url, Dictionary2 parameters, Dictionary2 keys)
at Jira.SDK.JiraClient.SearchIssues(String jql, Int32 maxResults)
The text was updated successfully, but these errors were encountered:
Hi,
I have been using the version of nuget package Jira.SDK 1.2.25 and is working fine for us, all we are doing is passing a jql and getting the issues list. but not sure what happened, am started to get the following error when SearchIssue method is called
"Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
Source=Newtonsoft.Json
from stack trace it is coming from
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonTextReader.Read()
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
at Jira.SDK.JiraClient.DeserializeIssues(String json)
at Jira.SDK.JiraClient.GetIssues(String url, Dictionary
2 parameters, Dictionary
2 keys)at Jira.SDK.JiraClient.SearchIssues(String jql, Int32 maxResults)
The text was updated successfully, but these errors were encountered: