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

Debug logs are polluted with "Key 'CodingKeys(stringValue: "ownershipType", intValue: nil)' not found" #1392

Closed
5 tasks done
EliotAndres opened this issue Mar 15, 2022 · 4 comments · Fixed by #1399
Closed
5 tasks done
Assignees

Comments

@EliotAndres
Copy link

Describe the bug
We just updated to 4.0.0. Since then the RevenueCat debug logs show this line very often:

[Purchases] - DEBUG: ℹ️ Key 'CodingKeys(stringValue: "ownershipType", intValue: nil)' not found, codingPath: [], description:
No value associated with key CodingKeys(stringValue: "ownershipType", intValue: nil) ("ownershipType"), converted to ownership_type.
  1. Environment
    1. Platform: iOS
    2. SDK version: 4.0.0
    3. OS version: 14.4.1
    4. Xcode version: 13.3 beta 3
    5. How widespread is the issue. Percentage of devices affected.
  2. Debug logs that reproduce the issue
  3. Steps to reproduce, with a description of expected vs. actual behavior
  4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)
    It could be linked to iOS 14 or to the fact that this phone was previously running a previous version of the RevenueCat SDK.
@vegaro
Copy link
Contributor

vegaro commented Mar 16, 2022

Thanks for opening @EliotAndres . It looks like ownershipType is not always present in the response we get from our backend. We can default to PURCHASED to silence the log. I will look into it.

@vegaro vegaro self-assigned this Mar 16, 2022
@vegaro vegaro added the triaged label Mar 16, 2022
@EliotAndres
Copy link
Author

Thank you for your quick answer. We're about to release the update to production, so let me know if we should wait until this is fixed or if we're good to go. If we're good to go I'll disable debug logs and close this issue

@vegaro
Copy link
Contributor

vegaro commented Mar 18, 2022

We just merged a PR that removes the log since it wasn't that helpful and it was polluting the debug logs. We'll release it with the next version.

Thanks for opening the issue @EliotAndres

@github-actions
Copy link

This issue has been automatically locked due to no recent activity after it was closed. Please open a new issue for related reports.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants