Sparkle

Receving [SUHost sharedFrameworksPath]: unrecognized selector sent to instance

Asked by jay_eagle

For some reason I continue to get the following exception in the console when my app starts up:

-[SUHost sharedFrameworksPath]: unrecognized selector sent to instance.

I have set up my app identically to my test app using sparkle, and I just started getting this message.

Does anyone have any ideas how to correct this?

Question information

Language:
English Edit question
Status:
Solved
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Solved by:
jay_eagle
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
jay_eagle (jason-eagle) said : 		#1

The copy step was not copying the alias links to the frameworks directory.

Revision history for this message
kdbdallas (dbrown-hashbangind) said : 		#2

I am getting this error seen also, but only for some users.
For me for example it works fine.

Why would this show only for a small percentage of my users?

Revision history for this message
Andy Matuschak (andymatuschak) said : 		#3

Huh. So what's interesting is that that should never happen—that selector is sent to an NSBundle, not an SUHost. Are you calling initWithBundle with a custom bundle by chance?

Revision history for this message
kdbdallas (dbrown-hashbangind) said : 		#4

Nope.. Just searched my entire project for initWithBundle and nothing.

Revision history for this message
jay_eagle (jason-eagle) said : 		#5

I am receiving this message again, previously I fixed it by adding the SUFeedURL url to my appcast.xml file, but recently I modified this to point to a redirect, and now it is occurring again.

Revision history for this message
jay_eagle (jason-eagle) said : 		#6

Figured out the problem, the aliases at the root of sparkle.framework were not being copied to the app bundle.

Revision history for this message
Dave Riggle (dave-busymac) said : 		#7

This line of code exists in the 1.5b6 release:

  NSString *frameworkPath = [[host sharedFrameworksPath] stringByAppendingPathComponent:@"Sparkle.framework"];

Seems a likely source of the problem.

Revision history for this message
jga23 (mail-jga) said : 		#8

So what is the fix to this bug? A few users of my app are experiencing this problem.

Revision history for this message
Andy Matuschak (andymatuschak) said : 		#9

This bug is fixed in more recent builds on Github.