Hello,
I've isolated a very strange issue that I'm having with Sparkle's SUUpdater,
though the issue is more to do with 64-bit and how frameworks work, I think.

My apps all use a common framework SDToolkit, which has an App Delegate
superclass that does a lot of work for me, called SDCommonAppDelegate.
Inside the -init method of this superclass, SUUpdater is created via updater= [[
SUUpdater sharedUpdater] retain]; which is supposed to return *something*,
and always has in the past.

Recently, I've updated all my apps and the frameworks they use, to 64-bit,
as a site-wide update for my company. Just this morning I discovered that
updater is now nil, inside my SDCommonAppDelegate class's -init method,
which is making it impossible for all of my current users to receive new
updates.

At this point I should probably mention that this bug ONLY happens when the
application itself is compiled as 32/64-bit, but under 32-bit it works fine.
That's the weird part!

I can't for the life of me figure out why it is returning nil. I think it
has to do with the fact that my framework SDToolkit is using a "weak" link
to Sparkle.framework (as set in its Target Info's General tab), and thus my
guess is that somehow this is making +alloc return nil under 64-bit mode.

I have verified that the Sparkle framework bundle is in fact 64-bit
(excepting ppc64) and my SDToolkit is as well.

Does anyone know why this would possibly be happening at all? I've looked
through Sparkle's source, and the only place where it could return nil
instead of a valid object is +alloc, from my understanding.

Thanks in advance for any help on this!!

-- 
Steven Degutis
http://www.thoughtfultree.com/
http://www.degutis.org/
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to