During a recent test cycle requiring Safari on macOS 14 and higher configurations, Safari failed silently, likely due to macOS privacy restrictions.

There was no option to change the environment; Safari was pre-selected. I initially recorded the bug using Chrome and marked Safari as the environment, fearing my bug would be rejected if I delayed further.

Later, with help from the Test IO Discord server, I discovered a working workaround using the PreProxy app, even though existing documentation is outdated. With PreProxy configured, I was finally able to run the test on Safari successfully — no prompts, no issues.

🔗 Reference: Discord Fix Discussion: https://discord.com/channels/562544573952294912/624515360170835988/879362209489223721

Suggestion:

Please consider:

Adding an article or Academy lesson covering proxy setup for macOS Safari, especially using PreProxy.

Mentioning known limitations with Safari and proxy.

Clarifying how testers can proceed when no prompt or fallback is available.

This would prevent confusion during time-sensitive cycles and support testers working with Safari environments.

Note: This is a known issue and not a bug report. Just feedback based on real experience. I’m not implying this is mandatory — just sharing for consideration.