Netip 0.2.0 doesn’t snow public IPs. Screenshot attached. Downgrading to previous version works fine.
Launch NEtIP. Reproduced 100% of launches. Refresh doesn’t help.
Hi!
Thanks for submitting this issue!
I’m unfortunately unable to reproduce the issue on my end, public IPv4 and IPv6 always show up even behind a VPN… 
I suspect this could be related to your previous issue, but I’m not sure. Does http://ipv4.icanhazip.com/ and http://ipv6.icanhazip.com/ still return your expected public IPs?
I plan on releasing a quick v0.2.1 patch early next week for other bugs I found this week while using the app. I’ll try to include a hotfix for this bug as well, and also add more internal logging to understand why none of your public IPs are showing up.
Bug validated.
Issue 8 on the repository tracker.
Strange thing downgrading to 0.1.0 works fine…
v0.2.0 checks if the Public IP values are not null and actually v6/v4 respectively before actually showing them in the popup. Otherwise, nothing is displayed in the popup field (which is not amazing UX-wise by the way. It should instead display something like “N/A” and/or an error message, but I digress).
v0.1.0 doesn’t check if the public IP values are actual IPv4 or v6. It only checks if the values are not null and displays them. I’ll have to investigate this further. 
Good news! I was able to reproduce your issue this morning. I’m not 100% sure on this, but I think it could be related to a timeout issue.
When connected to a slow connection and/or a VPN that just started, Windows can take a little while to resolve DNS, which means any HTTP request will fail or take longer than usual.
To avoid leaving hanging the network popup UI, NetIP times out the public IP request after 5 seconds, which is too short in this exact case. I could increase the timeout value and definitively must implement a user feedback for this error.
@bashik Could you confirm if navigating with a web browser to http://ipv4.icanhazip.com/ and http://ipv6.icanhazip.com/ takes a little while when reproducing the issue?
Hey!
Actually it shows result immediately.
Interesting… And not what I expected… 
If your browser can resolve icanhazip DNS immediately, there’s no reason NetIP should be any different.
Either way, I’ll improve the timeout and add more logging in v0.2.1 to better diagnose your issue. If the timeout doesn’t help, hopefully logging will help fixing it for patch v0.2.2! 
Quick update: I’ve made some progress this week, but this issue turned out to be way more challenging than I anticipated…
The patch v0.2.1 is therefore delayed, sorry about that! 
I am ok on version 0.1 )
What I am really looking for is the geo flag implementation, for me it is a killer feature. I am patient though)
Potential fix merged into branch develop & scheduled for release v0.2.1.
I had to change a lot of things… Hopefully it will fix the issue. I’m not marking this thread as completed yet until you’ll confirm the bug is gone. I’ll let you know when it’s released! 
@bashik The patch v0.2.1 is out, let me know if your issue is gone !
