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
Input non-ASCII character in the variable, such as á
Query fails
Expected Result
The query goes through and works, like it does without the Sentry interceptor.
Actual Result
Exception in thread “AWT-EventQueue-0” com.apollographql.apollo3.exception.ApolloNetworkException: Unexpected char 0xe1 at 7 in SENTRY-APOLLO-3-VARIABLES value: {name=á}.
Based on my research, non-ASCII characters are not usually allowed in headers, while it may work for some clients, it may not for others. Users have suggested using Base64 to work around this issue, which may be what Sentry needs to do.
The text was updated successfully, but these errors were encountered:
Hi @Syer10,
I'm currently looking into this. However, it seems like I'm unable to reproduce the issue within our Test-Suite.
Could you provide a minimum sample that causes this issue? Alternatively, could you provide a bit more detail on the system/tech-stack/client this issue arises on?
We want to make sure that this is reproducible in our Test-Suite so we can make sure it keeps working as expected after the fix.
Integration
sentry-apollo-3
Java Version
17
Version
6.17.0
Steps to Reproduce
á
Expected Result
The query goes through and works, like it does without the Sentry interceptor.
Actual Result
Exception in thread “AWT-EventQueue-0” com.apollographql.apollo3.exception.ApolloNetworkException: Unexpected char 0xe1 at 7 in SENTRY-APOLLO-3-VARIABLES value: {name=á}.
Based on my research, non-ASCII characters are not usually allowed in headers, while it may work for some clients, it may not for others. Users have suggested using Base64 to work around this issue, which may be what Sentry needs to do.
The text was updated successfully, but these errors were encountered: