Matt
I tried what you suggested. I can now catch the exception, but it also
propagates up to my uncaught exception handling delegate, which I am
surprised.
Now how bad is it to ignore "NSInvalidArgumentException" , the system
just logs these and I am only getting these issues when I have
installed my own uncaught exception handling system.
I tried it in Safari, it saves the pages but the result is not accurate.
Thanks
Reza
On 20 Jan 2009, at 10:18, Matt Gough wrote:
On 20 Jan 2009, at 09:10, Reza Farhad wrote:
The Problem is that the exception is occurring within the Apple
call, so there is no way for me to break into it.
Also I have tried to catch it locally but it get propagated to
uncaught exceptions.
Reza
Break on objc_exception_throw. Investigate from there...
corbin
You won't be able to see the source code, but the break on
objc_exception_throw would at least give you the stack trace and
maybe a clue as to what is going wrong.
It seems odd that you can't catch the exception though. Have you tried
@try{[[[webView mainFrame] dataSource] webArchive]}
@catch(id exception){}
instead of catching (NSException* exception) ?
Is Safari able to save the Webarchive of the same page without any
problems?
Good Luck
Matt
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [email protected]
