How to debug SparkePlus internet connection error?

[SteveC]

Folks;

I've just joined the SparkePlus group. I downloaded the most recent
(r115) and built a Release version under Leopard (no problems -
XCode3)
(Well except that the test app didn't build but the framework did!)

I took the framework and added it to my Linked Frameworks and then
added a copyFiles phase and added the Framwork to that.

I then read the class 'SUUpdater' into MainMenu.nib and then
associated a menu item (Check for Update) to the checkForUpdates
method in 'SUUpdater'.

I have an appcast file that I can successfully load in Safari by the
url and Safari will display the .xml file in a normal rss window with
the link to the enclosure properly linked.

My info.plist contains the following: url deliberately fudged)
...
<key>SUFeedURL</key>
<string>http://www.example.com/CurrentVersion/MyAppcast.xml</string>
<key>SUCheckAtStartup</key>
<string>NO</string>
<key>SUAllowsAutomaticUpdates</key>
<string>NO</string>
<key>CFBundleShortVersionString</key>
<string>1.0 beta 7</string>
<key>CFBundleVersion</key>
<string>1.0.0.0b7</string>
...

When I remove all my application traces, on first launch the Sparkle
prompt for @startup & profile shows up.
This is a little surprising since I have set the info.plist but not
a core issue right now!

When i then select the menu item identified above, I get the
following:
Update Error: An error occurred in retrieving update information;
are you connected to the internet? Please try again later.

I AM of course connected, email, browsing, source downloading, etc...
all functioning perfectly!

There are no relevant console log entries in XCode or Console.

*** How do I debug what is wrong? ***

Thanks for the really cool framework! I will definitely attribute in
the product and on web stat page!
Steve

[SteveC]

Folks;

Well, I've been poking around and finally found my bad, a stinking out
of balance quote in the appcast.xml!! Arrgh!

Anyway I learned a fair bit about SparklePlus in the meantime and I
have to say it is a LOT more powerful than I first understood!

It might be handy, if in at least some of the more crucial @catch
blocks, you logged the exception ala:
@catch (NSException *e)
{
NSLog(@"%@", e);
if ([delegate respondsToSelector:@selector(appcastDidFailToLoad:)])
[delegate
performSelectorOnMainThread:@selector(appcastDidFailToLoad:)
withObject:self waitUntilDone:NO];
}
That way at least there is some trail of what went wrong. Packing the
exception into userInfo and sending that upstream to the UI would be
even better but I know, I know - not enough hours or hands...

Anyway,sorry for the original pester but it did set me to rolling up
my sleeves and digging into the SU code base.
THANKS for an awesome tool!

Steve