Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
This is also affecting Rarity. I can't get the add-on to build properly as a result of this issue. Can we get an update from anyone? It's not specific to Mercurial, as it happens to only SVN repos in my example.
Seems back up now. Cool that we got no response on this issue. Curse has really gone to shit these past six months. I've got users yelling at me over the packaging bug, and now they're telling me the Client is forcing Alpha builds on them when they set it to Release, again blaming me. The whole platform is inherently unreliable now. It had a good run, but I guess all things come to an end.
Surprised this hasn't gotten any attention yet. This issue also affects me. It completely broke packaging yet again for Rarity. You guys really need to test with multi-line keys any time you touch the localization portion of the packager.
You do need to enter a URL. The directory is what I'm talking about, it's the URL, and it requires some memory or looking up to find. Anyway, it turns out that TortoiseSVN saves your last tag's URL, making this trivial. Since this was SVN-only and it's not as hard as I thought it was, disregard. It's not a big deal.
Oh, I guess you're supposed to click "Following" and then turn on "Issues". That is yet another feature that is hidden behind strange and awkward UI design.
I don't seem to get notifications when new issues are created, or when new comments are posted on issues. Is this intentional? As a result, tickets really get lost.
Must have. :) Out of curiosity, what does the approval process involve? I'm familiar with Apple's, but they use a lot of automated tools and symbol checkers, and then they actually install and run the app. Are you doing any of that? What things would trigger something to not be approved? (This might warrant a larger blog post, maybe.)
This issue affected my add-on Rarity as well. Currently I'm unable to post updates to that add-on due to this. I submitted a ticket and Torhal responded, saying he has made the developers aware of the issue, and it is affecting multiple add-ons.
0
This is also affecting Rarity. I can't get the add-on to build properly as a result of this issue. Can we get an update from anyone? It's not specific to Mercurial, as it happens to only SVN repos in my example.
Submitting a ticket now.
0
Good to know. How to contact support is not readily apparent.
They used to monitor this forum.
0
Seems back up now. Cool that we got no response on this issue. Curse has really gone to shit these past six months. I've got users yelling at me over the packaging bug, and now they're telling me the Client is forcing Alpha builds on them when they set it to Release, again blaming me. The whole platform is inherently unreliable now. It had a good run, but I guess all things come to an end.
0
Me too. Subversion repos are totally down (can't commit either).
0
Surprised this hasn't gotten any attention yet. This issue also affects me. It completely broke packaging yet again for Rarity. You guys really need to test with multi-line keys any time you touch the localization portion of the packager.
0
Also confirming the localization within the packager now works for multiline phrases.
0
You do need to enter a URL. The directory is what I'm talking about, it's the URL, and it requires some memory or looking up to find. Anyway, it turns out that TortoiseSVN saves your last tag's URL, making this trivial. Since this was SVN-only and it's not as hard as I thought it was, disregard. It's not a big deal.
0
Actually it looks like Torhal right above you did announce that they were fixed. Testing now.
0
Thank you for responding! I just wanted to point out that this issue is a critical blocker—anyone affected by it cannot use the Curse platform at all.
0
Oh, I guess you're supposed to click "Following" and then turn on "Issues". That is yet another feature that is hidden behind strange and awkward UI design.
0
I mean new tickets. When a new ticket is submitted, I don't get a notification. This means I have to manually check for them.
I just checked and there were two new tickets and no notification for them. This means realistically I won't see new tickets very frequently.
0
I don't seem to get notifications when new issues are created, or when new comments are posted on issues. Is this intentional? As a result, tickets really get lost.
0
Must have. :) Out of curiosity, what does the approval process involve? I'm familiar with Apple's, but they use a lot of automated tools and symbol checkers, and then they actually install and run the app. Are you doing any of that? What things would trigger something to not be approved? (This might warrant a larger blog post, maybe.)
0
Thank you! It wasn't clear what that option did, so I hadn't tried it yet.
0
This issue affected my add-on Rarity as well. Currently I'm unable to post updates to that add-on due to this. I submitted a ticket and Torhal responded, saying he has made the developers aware of the issue, and it is affecting multiple add-ons.