-
Notifications
You must be signed in to change notification settings - Fork 1
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
packetfix-hander: don't hardcode Wireshark.app installation path into the apple script #19
Comments
Thank you very much for your report and information on how to fix it, highly appreciated! With my current limited understanding of these macos corners, the Apple script "sources" are inside https://github.com/siemens/cshargextcap/tree/main/packaging/macos/packetflix-handler: this "exploded" bundle can be loaded into Apple's Script Editor. Yes, that's very inconvenient, not something that fits into modern CI/CD, but Apple doesn't seem to recognize this as outdated. If there is actually a way to build from proper source in a Github action runner, I would be thankful for pointers. I'll look into this. |
Unfortunately I am like on the same boat: not that familiar with AppleScriptEditor and especially would it be possible to actually create If macOS runner is available than maybe something like |
Hi @maslovalex It is actually quite easy to modify the script, you open the app Anyways, I added the snippet you provided and zipped it: It worked on my system where the app is installed natively (no macports), give it a try and hopefully it "just works" |
Yes, it works for me also as I have modified it manually in my system same way you described 👍 |
nota bene: we should consider using nohup in order to be able to finish the script immediately after start. This would allow starting multiple Wireshark-Edgeshark sessions in parallel from the web UI. Beware of quoting...
|
Current packetfix-handler expects Wireshark to be installed under
/Applications/
which is not always the case, e.g.macports
installs it under the/Applications/MacPorts/
Couldn't find the sources of AppleScript to make a PR :) so, here are the changes to make it a bit better than it is:
to something like
This is not my solution, btw, just found a nice one from https://www.macscripter.net/t/determining-path-to-application-without-using-path-to-command/73645/5
The text was updated successfully, but these errors were encountered: