Unable to make purchaseof book

So this popped up in my inbox and thought, sweet.

First I followed http://raywenderlich.us1.list-manage.com/track/click?u=1bc8e630b1599df629818e59b&id=cc947a435d&e=d205a5f1b3 which doesn’t exist … opps

The I followed http://raywenderlich.us1.list-manage.com/track/click?u=1bc8e630b1599df629818e59b&id=c5a3a425f5&e=d205a5f1b3 to the store and clicked on the pretty “Buy PDF” button, which doesn’t seem to do anything

So I went back to the store page and clicked on the book there and tried the pretty “Buy PDF” button, which again, did nothing.

So, I’ve probably bought a dozen copies by now, but it’s not allowing to download it (or actually enter any account details)

This “appears” to be an issue with the privacy filter extension installed in my browser - it’s at least now got me at a infinite wait indiciator

I now haz book :smiley:

1 Like

Glad that’s solved. Enjoy!

I get an infinite spinner on Mac Chrome, Mac Safari, and iOS Safari. Unable to purchase. I have no blockers or mega privacy things installed.

When hitting buy PDF the response JSON is a 500 server error HTML page.

"<!DOCTYPE html>
<html>
<head>
<title>We're sorry, but something went wrong (500)</title>
<meta name=\"viewport\" content=\"width=device-width,initial-scale=1\">
<style>..."

Well it let me attempt to buy the book finally but then I got an error - no book, no receipt shown in my receipts. But hey I have a pending charge for $44.99!

obviously there’s something wrong, no need to try anymore. wait until someone response here or visit the contact page: https://www.raywenderlich.com/contact

I had same issue while purchasing the book. My credit card was charged but checkout page shown me “We’re sorry, but something went wrong (500)” message. But in a few minutes, I have received an email with confirmation about book. So, now it’s available on my loot page.

1 Like

sorry for the inconvenience - it was an issue with our payment provider, the purchase will go through and everything was fine, but few people saw an error 500 message, which definitely was annoying for them.