8000 LaunchDarkly.ClientSDK 5.3.0 throws `Format_InvalidStringWithOffsetAndReason` · Issue #89 · launchdarkly/dotnet-core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

LaunchDarkly.ClientSDK 5.3.0 throws Format_InvalidStringWithOffsetAndReason #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ryanalford-suzy opened this issue Apr 3, 2025 · 6 comments
Open

LaunchDarkly.ClientSDK 5.3.0 throws Format_InvalidStringWithOffsetAndReason #89

ryanalford-suzy opened this issue Apr 3, 2025 · 6 comments
Labels
bug Something isn't working package: sdk/server

Comments

@ryanalford-suzy
Copy link

Is this a support request?
We are seeing an increasing number of exceptions being thrown in the ClientSDK for .Net/Maui. We are only seeing it in release builds, but I can't totally rule out that it would happen in debug builds. We just haven't seen it in debug builds.

It seems like the exception is happening in the LaunchDarkly.InternalSDK.

Describe the bug
See screenshots below

To reproduce
N/A

Expected behavior
Should not throw exceptions?

Logs
See screenshots below

SDK version
LaunchDarkly.ClientSDK 5.3.0

Language version, developer tools
.Net 8.0, Maui 8.0.100

OS/platform
Only seems to happen on iOS. I've got iOS reports on iOS 15.5 all the way through 18.3.

I went through our Android crash/error reporting and didn't find any reports.

Additional context
Since I can't give you access to the crash report, I can try to give screenshots of the stack trace and error message.

Image
@ryanalford-suzy ryanalford-suzy added bug Something isn't working package: sdk/server labels Apr 3, 2025
@tanderson-ld
Copy link
Contributor

Thank you for bringing this to our attention. Filed internally as 1177.

Could you provide stats on frequency and daily sessions impacted to help us triage?

Thank you.

@ryanalford-suzy
Copy link
Author

Over the last 24 hours, 104 users had it occur 148 times. Over the last 7 days, 708 users had it occur ~4200 times.

Image

Image

@tanderson-ld
Copy link
Contributor
tanderson-ld commented Apr 7, 2025 •
edited
Loading

Thank you for the quick response. Did anything in the project change recently? SDK Version update, target .NET version, etc...?

@ryanalford-suzy
Copy link
Author

We updated SDK from version 5.2.1 to 5.3.0 about 3 months ago(we are on our third release since then). At that time, we also started adding a custom attribute for the user Context.

Image

Pretty straight forward code change.

Our latest version is the first time we've had Sentry crash reporting implemented. We were using AppCenter before. I went through AppCenter's crash reports and didn't see this issue. I only started seeing it after moving to Sentry. Not sure if AppCenter was just missing it or not.

@tanderson-ld
Copy link
Contributor

Thank you for the extra info. Will dig in in the next day or two and let you know what we find.

@tanderson-ld
Copy link
Contributor

I haven't been able to reproduce this. Have you been able to up to this point?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working package: sdk/server
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ryanalford-suzy @tanderson-ld
0