-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app presents wrong ip address #18
Comments
I have the same issue.
When choosing the other IP it seems to setup correctly but then of course I can't connect because 192.0.0.0/24 is not a range that is valid within my network. I'm on iPhone 15 Pro Max with iOS 17.4.1 |
Further investigation yielded that the xx.0.0.xx:8596 seems to be shown when Mobile Data is activated. It doesn't show for me when I switch it off. However the issue still persists that I can't establish a connection to my normal internal IP address (192.169.2.XX:8596) with the aforementioned error occuring. I dug out an old Android Phone (Samsung J5) and installed the app on there. The connection works perfectly fine on there and I can roll my dice which show up in Foundry. This suggests that the problem only occurs on iPhones (and presumably iPads, which I can't tests since I don't own an iPad). |
It might be a problem with how websockets are setup in iOS. The layout of the GoDice App suggest that it's written with Xamarin/Cordova or a similar cross-platform tool that utilisies a specific browser engine in the background as it looks exactly the same on Android and iOS leading to somewhat hail mary conclusion that setting up a socket in iOS needs to be handled a separate way than in Android (This is pure speculation at this point in time). However iOS has to be known to throw some tantrums when it comes down to websockets: Sources:
Might be that the GoDice App needs to be revisited here @ParticulaCode |
app providing inaccurate ip address
putting 0s in middle of ips
xx.0.0.xx:8596
instead of actual ip provided by phone.
The text was updated successfully, but these errors were encountered: