GraphQL createSponsorship error #2977378

[anehzat]

Select Topic Area

GraphQL createSponsorship error

Body

Hi GH Team

Is there someone in the team that can help with this sponsorship issue.

https://support.github.com/ticket/personal/0/2977378

[rioyuda02]

Hi,
I think follow up with new open tickets.
Link : https://support.github.com/tickets/personal/0

[akoenig]

I also received the same error message today when trying to place one time payments:

mutation CreateSponsorship($amount: Int!, $sponsorLogin: String!, $sponsorableId: ID!) {
  createSponsorship(input:{
    amount: $amount,
    sponsorLogin: $sponsorLogin,
    sponsorableId: $sponsorableId,
    isRecurring: false,
    privacyLevel: PRIVATE
  }) {
    sponsorship {
      id
    }
  }
}

Wondering if this is a temporary problem or if I'm doing something wrong 🤷‍♂️ @anehzat did it work for you at some point?

[anehzat]

it's never worked for us @akoenig

[aspeckofdustin]

Chiming in from the Sponsors team as the new PM -- I am going to create a ticket with our eng team but in our repo. Thanks for flagging!

[akoenig]

It's my pleasure to try to help if I can.

❤️

Without the one-time payments, there is no other known workaround that the users can make (and you/they have reached out to the GitHub Support team already) correct?

Yes, our approach is for our service to issue one-time payments through the GitHub Sponsors API. Regarding workarounds, one possibility would be to issue a sponsorship using an existing tier. However, this workaround is not feasible for our approach, as it would require an OSS contributor who receives a payment to first add a tier and then inform us about it. Ideally, those who receive a sponsorship should not be aware of it beforehand. Therefore, we would love to see one-time payment support in the API 🚀

Yap, I reached out to the GitHub Support, but the ticket was unfortunately closed with a reference to this discussion here.

[aspeckofdustin]

I see, very helpful context and I appreciate you outlining the details. Let me check in with our first responder team and see if there's something that can be done in the UI; I don't foresee this happening quickly given bandwidth but it's worth an ask to see if we can unblock the users.

[akoenig]

Thanks, @aspeckofdustin for your response.

Let me check in with our first responder team and see if there's something that can be done in the UI

Hm, I'm not entirely certain I understand how an adjustment of the UI could help. In my opinion, the existing createSponsorship mutation should be adjusted so that it can handle one-time payments. However, the specific error mentioned in the original post remains unclear. While I suspect it might be due to a lack of support for one-time payments, there could be another reason. Would it be possible to provide more context on the error itself?

I understand that resolving this issue might not have the highest priority, but in the light of building a more sustainable environment for Open Source / Indie Hackers, I think you should unblock developers who wants to contribute to this cause. The barrier "should" be as low as possible when it comes to sending💰to these group of people. Especially on THE platform where all this development happens.

[aspeckofdustin]

Yes, you're right - our team got back to me and mentioned that the only thing that would fix this problem is by adjusting the API itself, which would require more intensive engineering on the back-end. We were also able to replicate the bug so it is in fact a valid issue that you're experiencing and have officially logged it in our internal repo as a bug to fix.

We're also logging it in as a known issue in the Docs, and I understand your sentiment and agree whole-heartedly. I don't want to leave you in silence so just wanted to reply here, even though there's no concrete update yet. I will keep you posted when a fix can be prioritized but again want to just set expectations that it may not occur in the near term.

[nehzata]

@aspeckofdustin Thanks for following this up. If not near term what kind of medium term do you think would be most likely? :)