Skip to content
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.

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

Localization Decoding Issue #111

Open
ryancstack opened this issue Feb 18, 2025 · 4 comments
Open

Localization Decoding Issue #111

ryancstack opened this issue Feb 18, 2025 · 4 comments

Comments

@ryancstack
Copy link

SDK: 3.3.4

Getting failures when decoding fallbacks for paywalls with single localizations. Looking at the fallback downloaded from my account, the localizations are structured in an array for the key localization.

AdaptyHTTPEndpointErrorKey | GET /sdk/in-apps/***/paywall-builder/***/4_1/en/fallback.json
AdaptyHTTPStatusCodeErrorKey | 200
AdaptySourceErrorKey | [3.3.4]: Adapty/HTTPSession.swift#97
NSDebugDescription | Response decoding failed
nserror-code | 2006
nserror-domain | AdaptyErrorDomain
NSUnderlyingError | Swift.DecodingError.typeMismatch(Swift.Array<Any>, Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "data", intValue: nil), ContainerCodingKeys(stringValue: "paywall_builder_config", intValue: nil), CodingKeys(stringValue: "localizations", intValue: nil)], debugDescription: "Expected to decode Array<Any> but found a dictionary instead.", underlyingError: nil))
@x401om
Copy link
Contributor

x401om commented Feb 18, 2025

Hi @ryancstack, please contact [email protected] and send us the fallback file. It seems like one of the paywalls is corrupted.

@ryancstack
Copy link
Author

@x401om the paywall downloaded from the dashboard is properly formatted with the array fwiw

@x401om
Copy link
Contributor

x401om commented Feb 18, 2025

@ryancstack I understand this, but we need to know your company id and affected paywalls ids to resolve the issue. Since the SDK is not directly involved and this data contain sensitive information, I ask you to contact support.

@ryancstack
Copy link
Author

thanks @x401om I'll include that in the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants