-
Notifications
You must be signed in to change notification settings - Fork 6
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
Subscriber gems not bought #18
Comments
if (
(plan.dateTerminated && new Date(plan.dateTerminated).getTime() > new Date().getTime())
|| (plan.dateTerminated === null && plan.customerId === "group-plan")
) { Actually I understand the first part: If the plan has a termination date, check if it isn't expired. I couldn't find any information in the API on how to properly check, if a user is still a subscriber ... |
Hi @ramotar, what kind of subscription plan are you on? |
I have an uncanceled 12 month subscription as indicated by the |
Hi @ramotar, thanks for bringing this to my attention and thanks for your patience! I am collecting more data on various subscription types so I can rewrite the algorithm that checks for subscription benefits. I'll let you know as soon as I've released a fix for this issue. :) |
Hi @ramotar, thanks again for your patience. I just got COVID for the first time and I am finally recovered, so I am catching up on work and tasks. Can you please let me know whether you've ever received a gift subscription from another Habitica user? Thanks! |
Hi @ramotar, did you see my latest comment? Still need this info from you so I can proceed with the troubleshooting. :) |
Hey @bumbleshoot, |
What is the bug?
When trying to buy subscriber gems, my active subscription isn't detected properly.
Additional context
I already debugged the function
purchaseGems()
and the firstif
clause evaluates tofalse
.For reference, here is the content of my
plan
(withoutcustomerId
):How often does this happen?
On every try.
Script version
Automate Habitica v0.29.32 (beta) by @bumbleshoot
Script settings
The text was updated successfully, but these errors were encountered: