Error on OS X 10.5 "Invalid parameter not satisfying: windownibpath"

Asked by Adonis D.

I get the error "Invalid parameter not satisfying: windownibpath" when running my app in OS X 10.5 but in 10.6, everything works fine. I even tried the sample program included in the andymatuschak-Sparkle-f1a3538.zip and got the same error.

Here is the console log whenever I run the sample app.

2011-07-12 09:01:18.355 Sparkle Test App[306:10b] *** Assertion failure in -[SUUpdatePermissionPrompt initWithWindowNibPath:owner:], /SourceCache/AppKit/AppKit-949.27/AppKit.subproj/NSWindowController.m:107
2011-07-12 09:01:18.562 Sparkle Test App[306:10b] Invalid parameter not satisfying: windowNibPath

Question information

Language:
English Edit question
Status:
Solved
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Solved by:
Adonis D.
Solved:
Last query:
Last reply:
Revision history for this message
Adonis D. (gq-byte69) said :
#1

I get the error "Invalid parameter not satisfying: windownibpath" when running my app in OS X 10.5 but in 10.6, everything works fine. I even tried the sample program included in the andymatuschak-Sparkle-f1a3538.zip and got the same error.

Here is the console log whenever I run the sample app.

2011-07-12 09:01:18.355 Sparkle Test App[306:10b] *** Assertion failure in -[SUUpdatePermissionPrompt initWithWindowNibPath:owner:], /SourceCache/AppKit/AppKit-949.27/AppKit.subproj/NSWindowController.m:107
2011-07-12 09:01:18.562 Sparkle Test App[306:10b] Invalid parameter not satisfying: windowNibPath

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

When I've seen this before, it's been because of a broken extraction or download: does SUUpdatePermissionPrompt.nib exist in the localization directories? What are its contents?

Revision history for this message
Adonis D. (gq-byte69) said :
#3

Sorry to bother you Andy. You are right. It seems that sending the app through LAN messes the content of the app. I decided to compress my app first before sending it through LAN. That solved the problem. When I checked the code, I saw that it looks for the shortcut "Resources" found in myapp.app/Contents/Frameworks/Sparkle.framework/. That shortcut was missing after sending it through LAN and causes the error message.

Thank You very much Andy!