starred/Proxyman

Fork 0

mirror of https://github.com/ProxymanApp/Proxyman.git synced 2026-04-25 16:15:55 +03:00

[GH-ISSUE #1925] proxyman cli import does not activate "allow system environment" Scripting permission #1917

New issue

Open

opened 2026-03-03 19:55:26 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 19:55:26 +03:00

Owner

Originally created by @samybenatt on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1925

Originally assigned to: @NghiaTranUIT on GitHub.

Description

proxyman cli import does not activate "allow system environment" permission

Steps to Reproduce

Create script and activate "allow system environment" permission
Export current scripting settings with proxyman cli export

/Applications/Proxyman.app/Contents/MacOS/proxyman-cli export -m enabledRules -o /tmp/proxy_script.json

Remove scripting rule and disable system environment permission to reset Proxyman state
Close Proxyman
Import scripting settings with proxyman cli import

/Applications/Proxyman.app/Contents/MacOS/proxyman-cli import -m override -i /tmp/proxy_script.json

Open Proxyman and observe script imported and scripting enabled but environment variable option not activated

Current Behavior

proxyman cli import does not activate "allow system environment" permission of Scripting on import of settings

Expected Behavior

proxyman cli export should keep the state of Scripting advanced permission and proxyman cli import should be able to import it

Environment

Proxyman macOS 4.16.0

Originally created by @samybenatt on GitHub (Feb 2, 2024). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1925 Originally assigned to: @NghiaTranUIT on GitHub. ## Description proxyman cli import does not activate "allow system environment" permission ## Steps to Reproduce 1. Create script and activate "allow system environment" permission <img width="1207" alt="image" src="https://github.com/ProxymanApp/Proxyman/assets/24391573/c6933659-1e8d-4097-80d0-e744662ace75"> 2. Export current scripting settings with proxyman cli export ```bash /Applications/Proxyman.app/Contents/MacOS/proxyman-cli export -m enabledRules -o /tmp/proxy_script.json ``` <img width="567" alt="image" src="https://github.com/ProxymanApp/Proxyman/assets/24391573/6c3e2316-1225-4613-90a6-9e0f5424640e"> 3. Remove scripting rule and disable system environment permission to reset Proxyman state 4. Close Proxyman 5. Import scripting settings with proxyman cli import ```bash /Applications/Proxyman.app/Contents/MacOS/proxyman-cli import -m override -i /tmp/proxy_script.json ``` <img width="478" alt="image" src="https://github.com/ProxymanApp/Proxyman/assets/24391573/90ddbccd-19c2-450b-96ef-8de7bb21caf1"> 6. Open Proxyman and observe script imported and scripting enabled but environment variable option not activated <img width="1182" alt="image" src="https://github.com/ProxymanApp/Proxyman/assets/24391573/1fac5730-2b01-4665-b27f-f38beb393446"> ## Current Behavior proxyman cli import does not activate "allow system environment" permission of Scripting on import of settings ## Expected Behavior proxyman cli export should keep the state of Scripting advanced permission and proxyman cli import should be able to import it ## Environment Proxyman macOS 4.16.0

kerem added the

bug

label

2026-03-03 19:55:26 +03:00

kerem commented

2026-03-03 19:55:26 +03:00

Author

Owner

@samybenatt commented on GitHub (Feb 19, 2024):

@NghiaTranUIT Not sure if this one is related to the previous bug you fixed or not #(1924)
I marked it as a bug but might be a enhancement, let me know if you need me to update the label

@samybenatt commented on GitHub (Feb 19, 2024): @NghiaTranUIT Not sure if this one is related to the previous bug you fixed or not [#(1924)](https://github.com/ProxymanApp/Proxyman/issues/1924) I marked it as a bug but might be a enhancement, let me know if you need me to update the label

kerem commented

2026-03-03 19:55:26 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Feb 20, 2024):

@samybenatt from what I see, the Export Scripting data doesn't include the Scripting Setting. For now, it only exports the Script data itself.

Do you need these settings should be exported too ?

@NghiaTranUIT commented on GitHub (Feb 20, 2024): @samybenatt from what I see, the Export Scripting data doesn't include the Scripting Setting. For now, it only exports the Script data itself. Do you need these settings should be exported too ?

kerem commented

2026-03-03 19:55:27 +03:00

Author

Owner

@samybenatt commented on GitHub (Feb 20, 2024):

@samybenatt from what I see, the Export Scripting data doesn't include the Scripting Setting. For now, it only exports the Script data itself.

Do you need these settings should be exported too ?

@NghiaTranUIT Thanks for your reply.
For consistent CLI import/export, I feel that the script options should be included into the exported json too so it's easy to restore the exact same Proxyman script overall configuration (script + options enabled) from one environment to another (especially when those options are used within the script)

@samybenatt commented on GitHub (Feb 20, 2024): > @samybenatt from what I see, the Export Scripting data doesn't include the Scripting Setting. For now, it only exports the Script data itself. > > Do you need these settings should be exported too ? @NghiaTranUIT Thanks for your reply. For consistent CLI import/export, I feel that the script options should be included into the exported json too so it's easy to restore the exact same Proxyman script overall configuration (script + options enabled) from one environment to another (especially when those options are used within the script)