ErrorLoadingStorage

[cerealexx]

Lately we've been spammed with these errors in iOS devices from Segment plugin:

ErrorLoadingStorage state.dart in PersistedState.init.<fn>
Error loading storage: FormatException: Unexpected character (at character 13)
{"queue":[]}anonymousId":"ff3b23a3-d9b9-42cf-be59-5574cf37da38","messageId"...

Any ideas?

[edsonjab]

hi @cerealexx we are working on the solution, thank you for your report.

[edsonjab]

hi @cerealexx could you help me to show me your configuration to try replicate the issue, please?

[cerealexx]

Configuration(
  WRITE_KEY,
  trackApplicationLifecycleEvents: true,
)

[PabloTortosaLopez]

Hey, I'm getting the same error, any updates on this?

[edsonjab]

Hi @PabloTortosaLopez , could you help us with the configuration of your project to know how can we replicate the issue?
Or an example similar to your project and configuration, please?

[PabloTortosaLopez]

Hey @edsonjab, this is the configuration that we are using on the project, pretty straightforward.

Configuration(
                _platformKey
                trackApplicationLifecycleEvents: true,
              )

We are using segment_analytics: ^1.0.1 and flutter 3.22.2

[brunosp15]

I'm facing the same problem, do you have any update on this?

We are using segment_analytics: 1.0.2 and flutter 3.22.1

[fhdeodato]

Hey guys,

I am facing the same trouble

not sure if there is an workaround for that, it is really hard to replicate... not get the error while debugging yet =(

[felipefuzaro-funda]

Hello,

We are also facing the error increase. Using segments_analytics 1.0.2 and Flutter version 3.22.2.

I was not able to reproduce it while testing. It happens mostly on iOS but we also have some error logs from Android.

*Logs are sampled in 1%

[felipefuzaro-funda]

I see the PR is merged, thank you for that 😄

Do you have a plan to release a new plugin version?

[PabloTortosaLopez]

Hey! I see the PR with the fix is merged 🚀

When will a new version with this fix be released?

Thank you!

[0aps]

@edsonjab any clue when we'll have a new version that includes this fix?