<?xml version="1.0" encoding="UTF-8"?>
<tickets type="array">
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">false</closed>
    <created-at type="datetime">2010-01-18T17:04:08-06:00</created-at>
    <creator-id type="integer">7462</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">13</number>
    <permalink>app-will-present-success-alert-sheet-even-if-url-in-plist-is-404</permalink>
    <priority type="integer">189339</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>open</state>
    <tag nil="true"></tag>
    <title>App will present success alert sheet even if URL in plist is 404</title>
    <updated-at type="datetime">2010-02-08T08:04:09-06:00</updated-at>
    <user-id type="integer">63029</user-id>
    <user-name>ctshryock</user-name>
    <creator-name>Mike Zornek</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/13</url>
    <original-body>If the developer mistypes the URL for his feedback form in the Info.plist or if the server happens to be wonky the user currently is shown a success message saying &quot;Your feedback has been sent.&quot;. While technically true .. it's been sent to a black hole never to see the light of day.

If the url is unavailable we should alert the user and suggest they send in the feedback via email or simply wait and try again later. Key here is to make sure we don't close the window and erase their message.

I don't see an easy way to do this using the current connectionDidFinishLoading: method so it might require more reworking.</original-body>
    <latest-body>If the developer mistypes the URL for his feedback form in the Info.plist or if the server happens to be wonky the user currently is shown a success message saying &quot;Your feedback has been sent.&quot;. While technically true .. it's been sent to a black hole never to see the light of day.

If the url is unavailable we should alert the user and suggest they send in the feedback via email or simply wait and try again later. Key here is to make sure we don't close the window and erase their message.

I don't see an easy way to do this using the current connectionDidFinishLoading: method so it might require more reworking.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;If the developer mistypes the URL for his feedback form in the
Info.plist or if the server happens to be wonky the user currently
is shown a success message saying &quot;Your feedback has been sent.&quot;.
While technically true .. it's been sent to a black hole never to
see the light of day.&lt;/p&gt;
&lt;p&gt;If the url is unavailable we should alert the user and suggest
they send in the feedback via email or simply wait and try again
later. Key here is to make sure we don't close the window and erase
their message.&lt;/p&gt;
&lt;p&gt;I don't see an easy way to do this using the current
connectionDidFinishLoading: method so it might require more
reworking.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2010-01-18T17:19:30-06:00</created-at>
    <creator-id type="integer">7462</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">14</number>
    <permalink>sample-php-script-doesnt-use-name-field-we-capture</permalink>
    <priority type="integer">0</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag nil="true"></tag>
    <title>Sample PHP script doesn't use name field we capture</title>
    <updated-at type="datetime">2010-01-20T09:44:13-06:00</updated-at>
    <user-id type="integer">7462</user-id>
    <user-name>Mike Zornek</user-name>
    <creator-name>Mike Zornek</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/14</url>
    <original-body>I noticed in the later versions we now capture the user's name. Sadly however the default sample PHP script doesn't utilize it.

I'm not interested in parsing the name for anything that might effect the email header so I use it at the top of the main message body like such:

@@@
if (eregi('^[a-zA-Z0-9._-]+@[a-zA-Z0-9-]+\.[a-zA-Z.]{2,5}$', $_REQUEST['email'])) {
    $email = $_REQUEST['email'];
    $name = $_REQUEST['name'];
} else {
    $email = 'mike@clickablebliss.com';
    $name = 'Unknown Submitter';
}
$feedback = $_REQUEST['feedback'];
$bundleID = $_REQUEST['bundleID'];
$systemProfile = $_REQUEST['systemProfile'];

$headers = 'From: ' . $email . &quot;\r\n&quot; .
      'Reply-To: ' . $email . &quot;\r\n&quot; .
      'X-Mailer: PHP/' . phpversion();

$msg .= &quot;$name writes:\n\n&quot;;
$msg .= &quot;$feedback\n&quot;;
@@@</original-body>
    <latest-body>I noticed in the later versions we now capture the user's name. Sadly however the default sample PHP script doesn't utilize it.

I'm not interested in parsing the name for anything that might effect the email header so I use it at the top of the main message body like such:

@@@
if (eregi('^[a-zA-Z0-9._-]+@[a-zA-Z0-9-]+\.[a-zA-Z.]{2,5}$', $_REQUEST['email'])) {
    $email = $_REQUEST['email'];
    $name = $_REQUEST['name'];
} else {
    $email = 'mike@clickablebliss.com';
    $name = 'Unknown Submitter';
}
$feedback = $_REQUEST['feedback'];
$bundleID = $_REQUEST['bundleID'];
$systemProfile = $_REQUEST['systemProfile'];

$headers = 'From: ' . $email . &quot;\r\n&quot; .
      'Reply-To: ' . $email . &quot;\r\n&quot; .
      'X-Mailer: PHP/' . phpversion();

$msg .= &quot;$name writes:\n\n&quot;;
$msg .= &quot;$feedback\n&quot;;
@@@</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;I noticed in the later versions we now capture the user's name.
Sadly however the default sample PHP script doesn't utilize it.&lt;/p&gt;
&lt;p&gt;I'm not interested in parsing the name for anything that might
effect the email header so I use it at the top of the main message
body like such:&lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;if (eregi('^[a-zA-Z0-9._-]+@[a-zA-Z0-9-]+\.[a-zA-Z.]{2,5}$', $_REQUEST['email'])) {
    $email = $_REQUEST['email'];
    $name = $_REQUEST['name'];
} else {
    $email = 'mike@clickablebliss.com';
    $name = 'Unknown Submitter';
}
$feedback = $_REQUEST['feedback'];
$bundleID = $_REQUEST['bundleID'];
$systemProfile = $_REQUEST['systemProfile'];

$headers = 'From: ' . $email . &quot;\r\n&quot; .
      'Reply-To: ' . $email . &quot;\r\n&quot; .
      'X-Mailer: PHP/' . phpversion();

$msg .= &quot;$name writes:\n\n&quot;;
$msg .= &quot;$feedback\n&quot;;&lt;/code&gt;
&lt;/pre&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">false</closed>
    <created-at type="datetime">2010-01-18T16:37:43-06:00</created-at>
    <creator-id type="integer">7462</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">12</number>
    <permalink>need-to-add-namespace-to-category-methods-appendstring-and-friends</permalink>
    <priority type="integer">0</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>open</state>
    <tag nil="true"></tag>
    <title>Need to add namespace to category methods appendString: and friends.</title>
    <updated-at type="datetime">2010-01-19T13:57:50-06:00</updated-at>
    <user-id type="integer">7462</user-id>
    <user-name>Mike Zornek</user-name>
    <creator-name>Mike Zornek</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/12</url>
    <original-body>In my own project I had a hell of a time debugging a broken POST body and found out the source to be the following category namespace collision.

In NSURLRequest+postForm.m we add some category methods on to NSMutableData

@@@ objectivec
@interface NSMutableData (append)
- (void)appendString:(NSString*)string;
- (void)appendFormat:(NSString *)format, ...;
@end 
@@@

Well it seems in 10.6 Apple has some similarly named methods that are colliding with ours.

objc[205]: REPLACED: -[NSMutableData appendString:]  by category MobileMeNSMutableDataAdditions  (IMP was 0x8ac32 (/Users/zorn/Builds/Debug/ProfitTrain.app/Contents/MacOS/ProfitTrain), now 0x92ce23bd (/System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/DotMacSyncManager))

I don't load the DotMacSyncManager framework and you won't see this collision with a generic new Cocoa app (like the demo app which works fine in 10.6). I assume it's coming along for the ride with WebKit or something I do link against.

Anyways we probably want to add some namespace to the method names.</original-body>
    <latest-body>In my own project I had a hell of a time debugging a broken POST body and found out the source to be the following category namespace collision.

In NSURLRequest+postForm.m we add some category methods on to NSMutableData

@@@ objectivec
@interface NSMutableData (append)
- (void)appendString:(NSString*)string;
- (void)appendFormat:(NSString *)format, ...;
@end 
@@@

Well it seems in 10.6 Apple has some similarly named methods that are colliding with ours.

objc[205]: REPLACED: -[NSMutableData appendString:]  by category MobileMeNSMutableDataAdditions  (IMP was 0x8ac32 (/Users/zorn/Builds/Debug/ProfitTrain.app/Contents/MacOS/ProfitTrain), now 0x92ce23bd (/System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/DotMacSyncManager))

I don't load the DotMacSyncManager framework and you won't see this collision with a generic new Cocoa app (like the demo app which works fine in 10.6). I assume it's coming along for the ride with WebKit or something I do link against.

Anyways we probably want to add some namespace to the method names.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;In my own project I had a hell of a time debugging a broken POST
body and found out the source to be the following category
namespace collision.&lt;/p&gt;
&lt;p&gt;In NSURLRequest+postForm.m we add some category methods on to
NSMutableData&lt;/p&gt;
&lt;pre&gt;
&lt;code class=&quot;objectivec&quot;&gt;@interface NSMutableData (append)
- (void)appendString:(NSString*)string;
- (void)appendFormat:(NSString *)format, ...;
@end&lt;/code&gt;
&lt;/pre&gt;
&lt;p&gt;Well it seems in 10.6 Apple has some similarly named methods
that are colliding with ours.&lt;/p&gt;
&lt;p&gt;objc[205]: REPLACED: -[NSMutableData appendString:] by category
MobileMeNSMutableDataAdditions (IMP was 0x8ac32
(/Users/zorn/Builds/Debug/ProfitTrain.app/Contents/MacOS/ProfitTrain),
now 0x92ce23bd
(/System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/DotMacSyncManager))&lt;/p&gt;
&lt;p&gt;I don't load the DotMacSyncManager framework and you won't see
this collision with a generic new Cocoa app (like the demo app
which works fine in 10.6). I assume it's coming along for the ride
with WebKit or something I do link against.&lt;/p&gt;
&lt;p&gt;Anyways we probably want to add some namespace to the method
names.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-12-01T18:27:28-06:00</created-at>
    <creator-id type="integer">2456</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">11</number>
    <permalink>scnetworkcheckreachabilitybyname-is-deprecated-in-106</permalink>
    <priority type="integer">180383</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag>warning</tag>
    <title>SCNetworkCheckReachabilityByName is deprecated in 10.6</title>
    <updated-at type="datetime">2009-12-02T12:25:06-06:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>Justin Williams</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/11</url>
    <original-body>*Summary:* SCNetworkCheckReachabilityByName has been deprecated in 10.6.  The following patch will fix it.  Comments/tweaks welcomed.  

http://gist.github.com/246780</original-body>
    <latest-body>*Summary:* SCNetworkCheckReachabilityByName has been deprecated in 10.6.  The following patch will fix it.  Comments/tweaks welcomed.  

http://gist.github.com/246780</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;&lt;em&gt;Summary:&lt;/em&gt; SCNetworkCheckReachabilityByName has been
deprecated in 10.6. The following patch will fix it.
Comments/tweaks welcomed.&lt;br&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=
&quot;http://gist.github.com/246780&quot;&gt;http://gist.github.com/246780&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-09-05T03:25:05-05:00</created-at>
    <creator-id type="integer">25228</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">10</number>
    <permalink>rails-cant-parse-posted-dat</permalink>
    <priority type="integer">138169</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag>bug multipart post rails</tag>
    <title>Rails can't parse posted dat</title>
    <updated-at type="datetime">2009-09-08T16:54:28-05:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>mantas</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/10</url>
    <original-body>I want to use Ruby On Rails as a backend. 

However, every time when data is posted I get following error:

Status: 500 Internal Server Error
bad content body</original-body>
    <latest-body>I want to use Ruby On Rails as a backend. 

However, every time when data is posted I get following error:

Status: 500 Internal Server Error
bad content body</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;I want to use Ruby On Rails as a backend.&lt;/p&gt;
&lt;p&gt;However, every time when data is posted I get following
error:&lt;/p&gt;
&lt;p&gt;Status: 500 Internal Server Error&lt;br&gt;
bad content body&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">false</closed>
    <created-at type="datetime">2009-08-25T00:29:16-05:00</created-at>
    <creator-id type="integer">67497</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">9</number>
    <permalink>french-xib-compiles-with-a-warning-on-105</permalink>
    <priority type="integer">134591</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>open</state>
    <tag nil="true"></tag>
    <title>French .xib compiles with a warning on 10.5</title>
    <updated-at type="datetime">2009-08-27T19:52:32-05:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>ddribin</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/9</url>
    <original-body>Same problem as the English .xib had a while ago.  Something about the segmented control.</original-body>
    <latest-body>Same problem as the English .xib had a while ago.  Something about the segmented control.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;Same problem as the English .xib had a while ago. Something
about the segmented control.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-02-19T16:26:34-06:00</created-at>
    <creator-id type="integer">7462</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">5</number>
    <permalink>using-showfeedbackwithbugdetails-results-in-all-message-text-being-bold</permalink>
    <priority type="integer">73441</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag nil="true"></tag>
    <title>Using showFeedbackWithBugDetails: results in all message text being bold.</title>
    <updated-at type="datetime">2009-08-06T14:00:36-05:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>Mike Zornek</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/5</url>
    <original-body>As I noted in the readme for 1.1.1

[NEW BUG] When using this new method the textView is given the bug report text via setString: this result in all the test being bold by default.

The main reason I haven't fixed it to date, is I'm not very good with attributed text.</original-body>
    <latest-body>As I noted in the readme for 1.1.1

[NEW BUG] When using this new method the textView is given the bug report text via setString: this result in all the test being bold by default.

The main reason I haven't fixed it to date, is I'm not very good with attributed text.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;As I noted in the readme for 1.1.1&lt;/p&gt;
&lt;p&gt;[NEW BUG] When using this new method the textView is given the
bug report text via setString: this result in all the test being
bold by default.&lt;/p&gt;
&lt;p&gt;The main reason I haven't fixed it to date, is I'm not very good
with attributed text.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer">45213</assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-07-17T07:49:19-05:00</created-at>
    <creator-id type="integer">63029</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">8</number>
    <permalink>jrfeedbackprovider-demo-app-wont-complie</permalink>
    <priority type="integer">114371</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag>localization</tag>
    <title>JRFeedbackProvider demo app wont complie</title>
    <updated-at type="datetime">2009-08-06T14:00:00-05:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>ctshryock</creator-name>
    <assigned-user-name>rentzsch</assigned-user-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/8</url>
    <original-body>I just pulled 88221115a3b511eb1011fc44e6e00ca777bf4e68 from last night and the demo app wont compile, it's looking for JRFeedbackProvider.xib in the lib folder but it's been moved to English.lproj (or French.lproj) in the move to add localization.  

I changed the path to the resource in the xcode project to fix this for now, was there a change to JRFeedbackProvider.xcodeproj that didn't make the commit?</original-body>
    <latest-body>I just pulled 88221115a3b511eb1011fc44e6e00ca777bf4e68 from last night and the demo app wont compile, it's looking for JRFeedbackProvider.xib in the lib folder but it's been moved to English.lproj (or French.lproj) in the move to add localization.  

I changed the path to the resource in the xcode project to fix this for now, was there a change to JRFeedbackProvider.xcodeproj that didn't make the commit?</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;I just pulled 88221115a3b511eb1011fc44e6e00ca777bf4e68 from last
night and the demo app wont compile, it's looking for
JRFeedbackProvider.xib in the lib folder but it's been moved to
English.lproj (or French.lproj) in the move to add
localization.&lt;br&gt;&lt;/p&gt;
&lt;p&gt;I changed the path to the resource in the xcode project to fix
this for now, was there a change to JRFeedbackProvider.xcodeproj
that didn't make the commit?&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-06-14T13:54:31-05:00</created-at>
    <creator-id type="integer">59896</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">7</number>
    <permalink>nscfarray-objectatindex-index-1-or-possibly-larger-beyond-bounds-0</permalink>
    <priority type="integer">120894</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag nil="true"></tag>
    <title>[NSCFArray objectAtIndex:]: index (-1( or possibly larger)) beyond bounds (0)</title>
    <updated-at type="datetime">2009-07-16T00:12:05-05:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>Rainer</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/7</url>
    <original-body>I am getting the same error as in bug # 6, it shows in your sample app like this:
*** -[NSCFArray objectAtIndex:]: index (-1( or possibly larger)) beyond bounds (0)
I'm on 10.5.7, Xcode 3.1, 10.5|Release|i386. When this error occurs, you can click the button again, and everything is fine. But a third click produces the same error, the fourth click gets the desired window.
I'm a Cocoa newbie, couldn't make the stack trace happen, but I am willing to try again, if you - or someone? - were to tell me how.
By caveman-debugging I found that the error is triggered by this line in +showFeedbackWithBugDetails in JRFeedbackController.m:
[gFeedbackController showWindow:self];
This line is roughly on line 57 of your code.</original-body>
    <latest-body>I am getting the same error as in bug # 6, it shows in your sample app like this:
*** -[NSCFArray objectAtIndex:]: index (-1( or possibly larger)) beyond bounds (0)
I'm on 10.5.7, Xcode 3.1, 10.5|Release|i386. When this error occurs, you can click the button again, and everything is fine. But a third click produces the same error, the fourth click gets the desired window.
I'm a Cocoa newbie, couldn't make the stack trace happen, but I am willing to try again, if you - or someone? - were to tell me how.
By caveman-debugging I found that the error is triggered by this line in +showFeedbackWithBugDetails in JRFeedbackController.m:
[gFeedbackController showWindow:self];
This line is roughly on line 57 of your code.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;I am getting the same error as in bug # 6, it shows in your
sample app like this: *** -[NSCFArray objectAtIndex:]: index (-1(
or possibly larger)) beyond bounds (0) I'm on 10.5.7, Xcode 3.1,
10.5|Release|i386. When this error occurs, you can click the button
again, and everything is fine. But a third click produces the same
error, the fourth click gets the desired window. I'm a Cocoa
newbie, couldn't make the stack trace happen, but I am willing to
try again, if you - or someone? - were to tell me how. By
caveman-debugging I found that the error is triggered by this line
in +showFeedbackWithBugDetails in JRFeedbackController.m:
[gFeedbackController showWindow:self]; This line is roughly on line
57 of your code.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer">45213</assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-03-01T16:55:09-06:00</created-at>
    <creator-id type="integer">46600</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">6</number>
    <permalink>bug-please-help</permalink>
    <priority type="integer">66757</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>wontfix</state>
    <tag nil="true"></tag>
    <title>Bug, please help</title>
    <updated-at type="datetime">2009-06-12T18:17:22-05:00</updated-at>
    <user-id type="integer">59896</user-id>
    <user-name>Rainer</user-name>
    <creator-name>sergmac (at gmail)</creator-name>
    <assigned-user-name>rentzsch</assigned-user-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/6</url>
    <original-body>After i implement your solution in my project and press Provide Feedback button, i get next error in console:
[33313:10b] *** -[NSCFArray objectAtIndex:]: index (-1( or possibly larger)) beyond bounds (0)
BUT after i press second time on the button window loads and all works perfectly, please help me solve this problem.
Tried the same just on your solution after downloading it without making any changes, same thing.
Thanks a lot! Waiting for your answer.</original-body>
    <latest-body>After i implement your solution in my project and press Provide Feedback button, i get next error in console:
[33313:10b] *** -[NSCFArray objectAtIndex:]: index (-1( or possibly larger)) beyond bounds (0)
BUT after i press second time on the button window loads and all works perfectly, please help me solve this problem.
Tried the same just on your solution after downloading it without making any changes, same thing.
Thanks a lot! Waiting for your answer.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;After i implement your solution in my project and press Provide
Feedback button, i get next error in console: [33313:10b] ***
-[NSCFArray objectAtIndex:]: index (-1( or possibly larger)) beyond
bounds (0) BUT after i press second time on the button window loads
and all works perfectly, please help me solve this problem. Tried
the same just on your solution after downloading it without making
any changes, same thing. Thanks a lot! Waiting for your answer.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-02-03T20:23:00-06:00</created-at>
    <creator-id type="integer">7462</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">1</number>
    <permalink>bug-checkbox-for-email-is-not-always-honored</permalink>
    <priority type="integer">68064</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>wontfix</state>
    <tag nil="true"></tag>
    <title>Bug: Checkbox for email is not always honored</title>
    <updated-at type="datetime">2009-02-18T16:17:13-06:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>Mike Zornek</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/1</url>
    <original-body>When I bring forward the feedback window, deselect the checkbox to send my email and then click on the support tab, the checkbox is re-selected.

I expect the checkbox to remain unselected.</original-body>
    <latest-body>When I bring forward the feedback window, deselect the checkbox to send my email and then click on the support tab, the checkbox is re-selected.

I expect the checkbox to remain unselected.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;When I bring forward the feedback window, deselect the checkbox
to send my email and then click on the support tab, the checkbox is
re-selected.&lt;/p&gt;
&lt;p&gt;I expect the checkbox to remain unselected.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-02-03T20:24:11-06:00</created-at>
    <creator-id type="integer">7462</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">2</number>
    <permalink>feature-should-post-app-version-and-build-number-in-report</permalink>
    <priority type="integer">68065</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag nil="true"></tag>
    <title>Feature: Should post App Version and Build Number in report</title>
    <updated-at type="datetime">2009-02-18T16:16:20-06:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>Mike Zornek</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/2</url>
    <original-body>It would be very helpful to know what version of my app they are running when they submit feedback. If I notice they are running 1.2.2 I can say go download 1.2.4 to fix this issue.</original-body>
    <latest-body>It would be very helpful to know what version of my app they are running when they submit feedback. If I notice they are running 1.2.2 I can say go download 1.2.4 to fix this issue.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;It would be very helpful to know what version of my app they are
running when they submit feedback. If I notice they are running
1.2.2 I can say go download 1.2.4 to fix this issue.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-02-04T09:30:06-06:00</created-at>
    <creator-id type="integer">7462</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">4</number>
    <permalink>feature-should-be-able-to-pre-fill-feedback-form-from-code</permalink>
    <priority type="integer">68225</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag nil="true"></tag>
    <title>Feature: Should be able to pre-fill feedback form from code.</title>
    <updated-at type="datetime">2009-02-18T16:16:09-06:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>Mike Zornek</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/4</url>
    <original-body>It would be nice if there was a way to init a feedback window with a pre-filled message.

For example, in my persistence code I do all the sql inside a transaction, before i commit it I check to see if we has any errors during the transaction (bad syntax, whatever). I then rollback and explain to the user why we can't save. Next to the OK (this sucks) button I want to have a button &quot;Report as Bug&quot; which would open the feedback window with a pre-filled message, the errors I got from SQLite.</original-body>
    <latest-body>It would be nice if there was a way to init a feedback window with a pre-filled message.

For example, in my persistence code I do all the sql inside a transaction, before i commit it I check to see if we has any errors during the transaction (bad syntax, whatever). I then rollback and explain to the user why we can't save. Next to the OK (this sucks) button I want to have a button &quot;Report as Bug&quot; which would open the feedback window with a pre-filled message, the errors I got from SQLite.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;It would be nice if there was a way to init a feedback window
with a pre-filled message.&lt;/p&gt;
&lt;p&gt;For example, in my persistence code I do all the sql inside a
transaction, before i commit it I check to see if we has any errors
during the transaction (bad syntax, whatever). I then rollback and
explain to the user why we can't save. Next to the OK (this sucks)
button I want to have a button &quot;Report as Bug&quot; which would open the
feedback window with a pre-filled message, the errors I got from
SQLite.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
  <ticket>
    <assigned-user-id type="integer" nil="true"></assigned-user-id>
    <attachments-count type="integer">0</attachments-count>
    <closed type="boolean">true</closed>
    <created-at type="datetime">2009-02-03T20:25:38-06:00</created-at>
    <creator-id type="integer">7462</creator-id>
    <milestone-due-on type="datetime" nil="true"></milestone-due-on>
    <milestone-id type="integer" nil="true"></milestone-id>
    <number type="integer">3</number>
    <permalink>feature-users-should-consent-to-hardware-profile-info</permalink>
    <priority type="integer">68066</priority>
    <project-id type="integer">24800</project-id>
    <raw-data type="binary" nil="true" encoding="base64"></raw-data>
    <state>resolved</state>
    <tag nil="true"></tag>
    <title>Feature: Users should consent to hardware profile info</title>
    <updated-at type="datetime">2009-02-18T16:15:48-06:00</updated-at>
    <user-id type="integer">45213</user-id>
    <user-name>rentzsch</user-name>
    <creator-name>Mike Zornek</creator-name>
    <url>http://rentzsch.lighthouseapp.com/projects/24800/tickets/3</url>
    <original-body>I'd love to see a checkbox where the user acknowledges sending in their hardware profile. 

In my own setup these posts auto generate FogBugz tickets and users are sent a link where they can follow the new ticket. Imaging sending one line of feedback asking for a simple feature, and then viewing the ticket to discover I've collected pages of hardware details and who knows what else. That info is scary to users.</original-body>
    <latest-body>I'd love to see a checkbox where the user acknowledges sending in their hardware profile. 

In my own setup these posts auto generate FogBugz tickets and users are sent a link where they can follow the new ticket. Imaging sending one line of feedback asking for a simple feature, and then viewing the ticket to discover I've collected pages of hardware details and who knows what else. That info is scary to users.</latest-body>
    <original-body-html>&lt;div&gt;&lt;p&gt;I'd love to see a checkbox where the user acknowledges sending
in their hardware profile.&lt;/p&gt;
&lt;p&gt;In my own setup these posts auto generate FogBugz tickets and
users are sent a link where they can follow the new ticket. Imaging
sending one line of feedback asking for a simple feature, and then
viewing the ticket to discover I've collected pages of hardware
details and who knows what else. That info is scary to users.&lt;/p&gt;&lt;/div&gt;</original-body-html>
  </ticket>
</tickets>
