MacOS: R2017a keeps asking "Allow incoming connections"
2 visualizzazioni (ultimi 30 giorni)
Mostra commenti meno recenti
Noah Kanovsky
il 26 Mar 2017
Modificato: Noah Kanovsky
il 25 Ago 2017
Running MacOS 10.12.3 On each invocation of Matlab R2017a, MacOS asks "Allow incoming connections, Allow / Deny". The answer doesn't get remembered for the next time I open Matlab. I have Matlab 2016a and 2017a installed side-by-side. The issue doesn't occur on MATLAB_R2016a, only on MATLAB_R2017a. I have worked around this by adding manually the file "/Applications/MATLAB_R2017a.app/Contents/MacOS/MATLAB" to the Firewall allowed list. I had to do this manually, as it wouldn't remember the setting from the prompt.
7 Commenti
Walter Roberson
il 11 Mag 2017
I did not observe this with the R2017a official running on a Sierra virtual machine.
Ian
il 11 Ago 2017
Modificato: Ian
il 11 Ago 2017
Problem persists for R2017a in MacOS Sierra 10.12.6, when opening via clicking on app icon or icon in dock. Adding Matlab (either the main /Applications entry or the actual executable mentioned by Kanovsky) did not solve the problem.
Matlab also does not remember previous screen position, and opens all windows, including figures on the wrong (for me) screen. It appears to always open on the screen where the dock is positioned (which for me is on the side of my smaller screen), regardless of where the window was positioned previously. Moving dock back to my main window fixes the problem, but I keep the dock on the side of the secondary window so I have more screen real estate for working.
Workaround in J Robin's link (see below) of opening matlab from the shell script (/Applications/Matlab.../bin/matlab) via command line seems to fix both problems for me.
Risposta accettata
Jyotish Robin
il 31 Mar 2017
Hi Noah!
Take a look at the below MATLAB answers post:
I hope this will help you solve the issue.
Regards,
Jyotish
0 Commenti
Più risposte (1)
Noah Kanovsky
il 31 Mar 2017
Modificato: Noah Kanovsky
il 25 Ago 2017
3 Commenti
Irl Smith
il 14 Lug 2017
Modificato: Irl Smith
il 14 Lug 2017
If this works, it implies that the startup code was changed (and the bug introduced) between 2016 and 2017. FWIW, there is no StartMATLAB in R2017a at the location listed, so that code seems to have been moved somewhere else. Mathworks, please fix! (I can't test it because I didn't retain my R2016 when I updated to R2017a.)
Vedere anche
Categorie
Scopri di più su Introduction to Installation and Licensing in Help Center e File Exchange
Prodotti
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!