5

2

I was delighted to find that my hosted account had been upgraded to v8, and even more pleased that a new version of the FogBugz plug-in was available for Visual Studio 2010.

My problem is that if I view a Filter other than "Inbox" I get an error in red-text at the top of the pane saying API returned invalid <case>

Is this a teething problem or an issue with my configuration/account?

Fog Creek Case FC1955552

flag
What plugins do you have enabled on your FogBugz site? – adambox Sep 22 2010 at 16:33
(repost since I accidentally added an answer instead of comment. how do you remove posts?) I have the same issue with the add-in using Visual Studio 2008. The old version of the plugin worked perfectly but after upgrade it will now complain about "API returned invalid ": screencast.com/t/Mzk2OTRm I'm using an on-demand account. Please fix! – Joakim Möller Sep 23 2010 at 14:16
Joakim, I just sent you an email to debug (Case FC1954248) – adambox Sep 23 2010 at 17:15
We have the similar problem, FB On demand v8, Visual Studio 2008. – Dmitry Lobanov Sep 27 2010 at 5:19
Same problem here. – carles Sep 27 2010 at 11:22
show 5 more comments

1 Answer

1

The fix should go out in the next service pack.

Update: The fix definitely went into 8.1.1 and I can no longer reproduce the API returned invalid <case> behavior when I change my number format to a locale that uses a comma as the decimal separator.

link|flag
When can we expect it to come? – Dmitry Lobanov Oct 13 2010 at 11:11
@Dmitry I'm not exactly sure but it should be in the next month or two. We're trying to move towards more frequent/regular releases so hopefully six months from now "next service pack" will be a much more precise description. – Aaron Maenpaa Oct 13 2010 at 19:19
Ok, thanks for the answer! – Dmitry Lobanov Oct 15 2010 at 4:28
Visual studio 2008 still returns "API returned invalid <case>" error. Fobgugz version 8.1.1 (DB 770, Build 2370). – Dmitry Lobanov Nov 11 2010 at 8:31
@Dmitry As I said in my edit: The went into to FogBugz 8.1.1 and I can no longer reproduce the problem using the 8.1.1 build. Would you mind re-installing the add-in and seeing if the problem persists? – Aaron Maenpaa Nov 22 2010 at 22:43

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.