Announcement

Collapse
No announcement yet.

Error in Log

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Error in Log

    sirmeili I've been catching this error in my log very recently. To be honest, I haven't done a lot of troubleshooting. I read earlier today that Life360 is going to start rolling out a feature called "Bubbles" https://www.life360.com/support/bubbles/ and thought maybe they are tweaking the API? I thought maybe I should see what you think before breaking my lazy streak and start working is what I'm getting at here. Think there's a correlation?

    Code:
    Exception UpdateInterval: Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue () [0x002b3] in :0 at Newtonsoft.Json.JsonTextReader.Read () [0x0004c] in :0 at Newtonsoft.Json.JsonReader.ReadAndMoveToContent () [0x00000] in :0 at Newtonsoft.Json.JsonReader.ReadForType (Newtonsoft.Json.Serialization.JsonContract contract, System.Boolean hasConverter) [0x0004a] in :0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType, System.Boolean checkAdditionalContent) [0x000db] in :0 at Newtonsoft.Json.JsonSerializer.DeserializeInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00054] in :0 at Newtonsoft.Json.JsonSerializer.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in :0 at Newtonsoft.Json.JsonConvert.DeserializeObject (System.String value, System.Type type, Newtonsoft.Json.JsonSerializerSettings settings) [0x0002d] in :0 at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in :0 at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value) [0x00000] in :0 at HSPI_Life360.Plugin.UpdateLife360Devices (System.Object obj) [0x00024] in :0

    #2
    Ok, disabled and re-enabled plugin. About 1.5 hrs and no error. That was anticlimactic.

    Comment

    Working...
    X