You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, huge thanks for creating this fantastic app—I’ve been loving it after using it for a few weeks. I wanted to show my support, so I clicked on the “Become a Patron” button. But when I clicked confirm the in-app purchase, it jumped to “You’re all set!” without actually running the Apple payment flow.
Just to double-check, I looked for the charge in my iCloud purchase history, but there’s no record of it. So, unless I accidentally discovered a “free support” glitch (🤞), it seems like there might be an issue with the purchase process.
You may want to take a look at your patron income stats to make sure this isn’t affecting your other fans who want to support your work too. Thanks again for such an awesome app!
macOS version
15.0.1 (24A348)
MeetingBar version
4.10.0
Installation source
AppStore
Calendars provider
macOS Calendar app
Bug description
Hi @leits 👋
First off, huge thanks for creating this fantastic app—I’ve been loving it after using it for a few weeks. I wanted to show my support, so I clicked on the “Become a Patron” button. But when I clicked confirm the in-app purchase, it jumped to “You’re all set!” without actually running the Apple payment flow.
Just to double-check, I looked for the charge in my iCloud purchase history, but there’s no record of it. So, unless I accidentally discovered a “free support” glitch (🤞), it seems like there might be an issue with the purchase process.
You may want to take a look at your patron income stats to make sure this isn’t affecting your other fans who want to support your work too. Thanks again for such an awesome app!
Reproduction steps
No response
Expected behavior
No response
Screenshots/screen recordings
No response
Additional context
For anyone running into this issue: Go buymeacoffee.com/meetingbar instead for now.
The text was updated successfully, but these errors were encountered: