We have a Xamarin app for Android.
We are attempting to show a Webview (in Xamarin).
It works perfectly when the app first starts - whether we are on WiFi or mobile networks.
However, if we are on a WiFi network and switch to the mobile network it fails with the following:
chromium: [WARNING:net_errors_posix.cc(127)] Unknown error Machine is not on the network (64) mapped to net::ERR_FAILED
chromium: [ERROR:socket_posix.cc(96)] CreatePlatformSocket() failed: Machine is not on the network (64)
if we then switch back to the wifi network - it works again.
If we create a native Android app with a webview it works perfectly.
It's only when we use the Xamarin webview that the problem occurs.
Ping still works and so does going to a site via a web browser in Android. It's only through the webview that it fails.
One important note:
We call a native Android aar which performs all sorts of initialisations for an SDK.
Our guess is it is something in there that is causing the problems since, when we remove it, everything works.
What could be out problem?
Related
I've been trying to get my iOS device to show me network traffic on Charles proxy but I haven't found any solution yet.
The code presented in here is the closest thing I have found that works:
https://medium.com/hoursofoperation/use-charles-proxy-to-debug-network-requests-in-flutter-apps-2f2083275cad
However, this only shows traffic in Charles if the project is run on simulator.
I don't know why simulator works and Device doesn't.
I tried changing the ip address of the proxy from code in the above blog to the ip address of the phone, to my computer, and to the proxy server.
Nothing works and all calls just flat out fail.
I know my phone can go through Charles normally, because other web calls still happen.
So what do I need to change for Flutter to work on my device?
I have been working on a react native project in Windows 10 for a while now using Expo to scan the given QR code and test the app on my IOS device. The other day I ran $expo start and everything seemed to go fine until I tried to load the app on my IOS device. I received this message:
Could not connect to server
I then "Run in Web Browser" which worked fine, so I tried accessing 127.0.0.1:19000 in my Iphone's browser (firefox) and it as well could not connect to server. My phone is connected via wifi which is 2.4 or 5g. I wasn't sure how this would effect this so I used a wifi adapter on PC to match which wifi connection phone and PC were on and that didn't help.
I am using react version 17.0.1, expo version 3.28.5, and "react-native": "https://github.com/expo/react-native/archive/sdk-38.0.0.tar.gz"
I have tried:
Turning off windows firewall
Using different Iphones to connect
npm install --global expo-cli
Changing Connection from "LAN" to "Local"
Reinstalling Node
Creating a System Variable called: "REACT_NATIVE_PACKAGER_HOSTNAME" with the value "192.168.2.108". This did change the LAN IP address as intended but it did not resolve the problem. I just got the same message with the new IP address.
This problem just started happening out of the blue and I'm not really sure what to do next. If you need any additional information I'd be happy to give it.
try to use
expo start --tunnel
When you get the message:
"Error loading DevTools ValidationError: "urlType" must be one of [exp, http, redirect, no-protocol]"
Just wait for a bit and the QR code for tunnel will appear. It does the same for me as well.
I have created react-native app for IOS. I have installed it on different different iPhones. It works fine. If I change my WiFi (named ABC) to another network (named DEF) on my mac and then upload it again on my mobile then it will crash. My Mac and my mobile WiFi network is the same. I have also tested it on mobile data and it's not working. But if I connect to WiFi (named ABC) and same on mobile then it works properly. It works only with one network. Why its not working with another WiFi netoworks and also with mobile data?
I have made the simplest app possible to connect to a Mavic Pro (basically the Swift version of this code (which comes from the Aircraft Binding and Activation demo on DJI's website.
My setup is as follows: iPhone running the App is connected via lightning cable to the main USB port on the RC (between the two joysticks on the bottom). The switch on the Mavic is set to "RC" (not Wifi).
When I run the app, the aircraft binding state is unknown and the DJISDKManager.product() returns nil, even though registration of the app completed successfully.
Here are some strange but helpful pieces of information:
With the same setup as above, running the DJI Go App from the same device works perfectly.
Using either the wireless bridge app or the wifi connections works perfectly and I'm able to connect with the aircraft no problem.
Is there some setting I'm missing? I looked at all of DJI's documentation very carefully, and have found no solutions.
The hardware accessory (the remote controller) may be associated with DJI Go now. With your app open, un-plug the lightening cable, and plug it back in. Now it will be associated with your app. With iOS 11 apps sharing hardware devices got a bit challenging.
(but thanks for mentioning DJI Go did work, then we don't have to worry the microUSB in the upper left corner of the RC was activated. Leaving the pigtail connector in will block the USB port you are using.)
I almost had the same problem. Here is the fix that worked for me.
Make sure in your info.plist file you have the following.
DJI-SDK
Also I am assuming that you calling DJISDKManager.startConnectionToProduct() after appRegisteredWithError(_ error: Error?) is called.
I haven't used it in a while until now but I cannot get it to work anymore even with a new, generated and unchanged, project. It worked perfectly fine before. It's been updated and the mobile app has been updated.. I've tried the desktop and CLI version.
Details:
Using Windows 10. Desktop App or CLI Phonegap.
Using iPhone iOS 9.0.2 mobile Phonegap app.
Using the basic, generated Phonegap Hello World.
What happens:
1. I serve the application.
2. I open the mobile app and enter credentials.
3. It sits on "Downloading" indefinitely
Note: If I open the URL in a browser on the serving machine it WILL open. If I open it on any other machine it will not.. This confuses me because they're on the same WiFi network so that has nothing to do with it. I even tried turning off my firewall in case the port was being blocked or something. I've tried 3000 and 8080.
Has anyone else experienced this?
I've uninstalled, re-reinstalled, used different versions, etc...
EDIT: I've found a solution, kind of.. If I use the --localtunnel flag it will work. I'm not sure why given that they ARE on the same network. Of course this also means that every single time I serve it is a different address which is quite a hassle. But at least I can test now.