Skip to content

Conversation

@autopulated
Copy link
Contributor

On OS X 14.7, I experienced an issue where attempting to connect would timeout. This turned out to be because NetworksetupWireless.current() was calling ipconfig to get the current SSID, even after a successful call to networksetup. ipconfig was returning <redacted>, overwriting the correct result from networksetup.

Happily, my problem was fixed by just skipping the ipconfig call (which seems like the original intention of this code, and a straightforward bug), but I've also added an explicit exception if a <redacted> value is returned, which will make the cause easier to diagnose if this happens for anyone else.

I'm not sure under which circumstances exactly these commands can return <redacted> values, but it seems like it's a privacy protection measure in recent OS X, which can be resolved by explicitly asking for location services permission.

Do not call ipconfig getsummary unnecessarily if networksetup succeeded:
In some cases networksetup has returned the correct SSID, but ipconfig
will return a <redacted> value. If the ssid value is still redacted,
then throwing an error prevents mysterious timeout failures, and exposes
the real cause.
tcamise-gpsw added a commit that referenced this pull request Nov 7, 2025
Incorporate error handling from PR #819 by @autopulated:
- Add RuntimeError when SSID is redacted in ipconfig getsummary
- Add RuntimeError when SSID is redacted in system_profiler
- Add Raises section to current() method docstring

This makes debugging easier when macOS privacy features redact WiFi information,
providing a clear error message instead of silent failures.

Co-authored-by: autopulated <autopulated@users.noreply.github.com>
@tcamise-gpsw
Copy link
Collaborator

This will be resolved by #856

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

Successfully merging this pull request may close these issues.

2 participants