Hey folks,
We have made changes here to hopefully resolve this issue, would you be able to retest from your side and confirm?
Hey folks,
We have made changes here to hopefully resolve this issue, would you be able to retest from your side and confirm?
It’s working correctly today
Thanks ![]()
Since yesterday we have this same issue again on our postman mock server
Works on iOS devices only Android devices cannot reach the mock server.
Seems like Android devices are able to reach the mock server only when Proxyman is running but not without.
https://0d315650-ee45-476f-8b31-14d5ddc86a89.mock.pstmn.io/
Hey @technical-architect5,
The UnknownHostException issue on Android has returned for my mock server (7d2c3f90-d028-47d3-a3db-770688edfff8.mock.pstmn.io). While browsers and desktop nslookup resolve fine, Android environments (emulator and physical) are failing to associate any address with the hostname. I have confirmed this isn’t a local DNS or config issue by testing across multiple networks and performing a cold boot. This seems to be a recurrence of the routing bug discussed earlier in this thread. Could the team please investigate if another server-side fix is required?
I’m experiencing a recurrence of the UnknownHostException issue specifically on Android both emulators and physical devices
The Problem: Since today it was working fine before, Android apps are failing with: java.net.UnknownHostException: Unable to resolve host “d485539a-0ef9-43a2-a382-35de2beb5d6f.mock.pstmn.io”: No address associated with hostname
What I’ve verified
iOS & Browsers: The mock server works perfectly fine on iOS and desktop browsers using the same network
Android Environment: Tested on physical devices and emulators
Network: Verified on multiple Wi-Fi networks and mobile data
Config: AndroidManifest has Internet permissions and network-security-config is correctly set
Could the Postman team check if there’s a server-side issue or a DNS propagation problem affecting Android’s resolution for this region?
Hey folks,
This should now be fixed, we appreciate you reporting this. ![]()
Thx for the quick reply and fix.
Works on our end again! ![]()