Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save Dialog Not Working - Even Not In save_file_dialog.py Example - on macOS #578

Closed
SurfChriz opened this issue Jul 24, 2020 · 4 comments
Closed

Comments

@SurfChriz
Copy link

SurfChriz commented Jul 24, 2020

Specification

  • pywebview version: 3.3.1 (but have seen the issue in older versions as well)
  • platform / version: macOS 10.15.6, Python 3.7.3

Description

When executing window.create_file_dialog(webview.SAVE_DIALOG....), the program stops execution and never delivers a result for that call.

I stumbled over the issue in a personal project and narrowed it down to not being able to execute the save_file_dialog.py example with the expected result.
Since it worked previously I suspected the macOS updates being the reason. So I started analysing by using the mac console.app, which brought up two errors when I executed the line of code in question:

  1. [NSOpenPanel filenames]: unrecognized (NSOpenPanel) selector sent to instance 0x7f865687c3a0. This sandboxed application's NSSavePanel class object only responds to NSSavePanel APIs! Please use the interface as described in NSSavePanel.h.
  2. (
    0 CoreFoundation 0x00007fff36a16b57 __exceptionPreprocess + 250
    1 libobjc.A.dylib 0x00007fff6f85d5bf objc_exception_throw + 48
    2 CoreFoundation 0x00007fff36a3f34c -[NSException raise] + 9
    3 _objc.cpython-37m-darwin.so 0x000000010b8a59de PyObjCErr_ToObjCWithGILState + 46
    4 _objc.cpython-37m-darwin.so 0x000000010b883333 method_stub + 5395
    5 _objc.cpython-37m-darwin.so 0x000000010b8a5364 ffi_closure_unix64_inner + 708
    6 _objc.cpython-37m-darwin.so 0x000000010b8a4886 ffi_closure_unix64 + 70
    7 CoreFoundation 0x00007fff3699ad52 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    8 CoreFoundation 0x00007fff3699acf1 __CFRunLoopDoSource0 + 103
    9 CoreFoundation 0x00007fff3699ab0b __CFRunLoopDoSources0 + 209
    10 CoreFoundation 0x00007fff3699983a __CFRunLoopRun + 927
    11 CoreFoundation 0x00007fff36998e3e CFRunLoopRunSpecific + 462
    12 HIToolbox 0x00007fff355c5abd RunCurrentEventLoopInMode + 292
    13 HIToolbox 0x00007fff355c57d5 ReceiveNextEventCommon + 584
    14 HIToolbox 0x00007fff355c5579 _BlockUntilNextEventMatchingListInModeWithFilter + 64
    15 AppKit 0x00007fff33c0b039 _DPSNextEvent + 883
    16 AppKit 0x00007fff33c09880 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
    17 AppKit 0x00007fff33bfb58e -[NSApplication run] + 658
    18 _objc.cpython-37m-darwin.so 0x000000010b8a4707 ffi_call_unix64 + 79
    19 ??? 0x000000010e2c8ac8 0x0 + 4532767432
    )

This looks like some security sandbox issues to me, but I am not pretty familiar with native mac development...

Practicalities

  • I am not willing to work on this issue myself.
  • I am not prepared to support this issue financially.
@r0x0r
Copy link
Owner

r0x0r commented Jul 24, 2020

@SurfChriz
Copy link
Author

SurfChriz commented Jul 24, 2020

You mean macOS 10.5.4? That would underline the idea of having a macOS issue with recent updates.
I remember, that it worked roughly a year ago, so probably on 10.14.x. Probably due to the enhanced System Integrity Protection... But I am only guessing...

@r0x0r
Copy link
Owner

r0x0r commented Jul 30, 2020

Fixed in master now.

@r0x0r
Copy link
Owner

r0x0r commented Aug 8, 2020

Released in 3.3.3

@r0x0r r0x0r closed this as completed Aug 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants