PurchasesEntitlementInfo type doesn't reflect all properties from actual data
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react-native, typescript
- Domain
- mobile-dev
Research direction
Start by locating the PurchasesEntitlementInfo type and searching the project for the six properties listed in the issue. Compare the declared type with the actual entitlement data, then verify that each property is accessible without a TypeScript error and run the relevant project checks.
Written by the indexing model from the issue text.
Description
- [+] I have updated Purchases SDK to the latest version
- [+] I have read the Contribution Guidelines
- [+] I have searched the Community
- [+] I have read docs.revenuecat.com
- [+] I have searched for existing Github issues
The following properties are not present in the PurchasesEntitlementInfo type, and you get a TypeScript error when trying to access them:
expirationDateMillis
unsubscribeDetectedAtMillis
latestPurchaseDateMillis
ownershipType
billingIssueDetectedAtMillis
originalPurchaseDateMillis
- Environment
- Platform:
- SDK version: 6.6.0
- OS version:
- Xcode/Android Studio version:
- React Native version:
- SDK installation (CocoaPods + version or manual):
- How widespread is the issue. Percentage of devices affected.
- Debug logs that reproduce the issue
- Steps to reproduce, with a description of expected vs. actual behavior
- Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)
Additional context
Add any other context about the problem here.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 117
- Avg merge
- 14h 40m
- Merged PRs (30d)
- 40
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RevenueCat/react-native-purchases
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
RevenueCat/react-native-purchases#1912 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
RevenueCat/react-native-purchases#1968 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
RevenueCat/react-native-purchases#1938 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
RevenueCat/react-native-purchases#1898 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
RevenueCat/react-native-purchases#1891 · 1 comment · 5 reactions ·
All issues in RevenueCat/react-native-purchases
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·