I created a "native" webworks app for the Blackberry Playbook and it required to have an url whitelist in the config.xml for accessing the internet.
Now, I converted my Android app, and I could not access the internet. How I could allow that?
Do you have <uses-permission android:name="android.permission.INTERNET" /> in your AndroidManifest.xml? That's all you need, I think.
Apparently the VMWare VM must be setted with network in bridged mode, instead of NAT mode, as they twitted here.
In this way my app can pass the network check, but still can't access the internet.
Related
Good day to all,
I am trying to create my website locally, and perhaps access the website through my phone from the localhost. Forgive me I am just a beginner.
So I used ipconfig -all to find my IPV4 address and it was e.g
192.168.1.102
And on the ASP.net webapplication I ran, the address was:
https://localhost:44337
Hence, I was trying to access this Web Application of mine created on my PC, to be accessed on my phone. On my phone, I entered the address:
192.168.1.102:44337
I went into my firewall setting to add a new rule for inbound connection to allow all ports to be connected as well. But it still don't work. Both my PC and phone is connected to the same wifi.
Does anyone know the fix? Thank you in advance.
You might have to configure an IIS server. This tool comes default in Windows (professional?), and there's lots of good resources on how to do this, all of which do a better job of explaining the process than I could do.
Essentially, you will need to:
Publish your site (Done through visual studio or cli)
Enable and configure your IIS
Create a new website in the IIS manager and point it towards the output of your web app publish
After opening the neccessary firewall ports, check to see in which IP address your web application is running. I am assuming you are using some sort of HTTP webserver software like IIS(windows) or Apache(Linux). In IIS to do that you must go to your site bindings and where it says "IP Address", select "All Unassigned" (NOT localhost or 127.0.0.1)so that the web application runs in all network adapters and IP addresses.
See full IIS documentation here: https://learn.microsoft.com/en-us/iis/get-started/getting-started-with-iis/getting-started-with-the-iis-manager-in-iis-7-and-iis-8
Follow the guide: https://medium.com/#manujsdeveloper/debug-a-website-local-or-remote-hosted-on-an-android-mobile-device-ff2c43527be1
You will need to set your phone in developer mode and get the OEM USB driver specific for your phone. and get a ADB running on your computer
I suggest supplement your knowledge with with links below, as some things are left out in the above guide and vice versa:
https://developer.android.com/studio/command-line/adb
https://developers.google.com/web/tools/chrome-devtools/remote-debugging
I am developing an UWP Application that should be able to accept incomming TCP connections.
I have given it the following capabilities in the package manifest:
Internet (Client)
Internet (Client/Server)
Private Networks (Client/Server)
I am using the StreamSocketListener from Windows.Networking.Sockets
Connections from other devices are established just fine.
Hovever: I can not connect from my own device over the loopback interface
As per this document from Microsoft, UWP does indeed restrict connections over the loopback interface, but:
Apps installed and run in Visual Studio will automatically be registered as being exempt from the loopback restrictions.
This is the scenario I'm in. And checking the Debug section in the application properties reveals that the Allow local network loopback is checked.
I checked the loopback excemptions on the system via
CheckNetIsolation.exe LoopbackExempt -s
My apps SID does appear in the list.
A comment under this SO answer suggested clearing the list and adding each entry manually. This did not resolve the problem.
Other things I have attempted:
Changing the release version of the App (Did not help)
Uninstalling and redeploying the App (Didi not help)
Setting up a fresh project. (Did not help)
Rebooting the system. (Did not help)
Using my LAN IP Address instead of the Loopback Address (Did not help)
Bashing my head against the wall (Did not help)
So the final question:
How can I enable loopback connections to a UWP app despite doing every step nescessary
Has anybody further experience with this? Is there some hidden trick I need to perform so I can connect from the local device?
If you have more than 682 records CheckNetIsolation.exe LoopbackExempt -s none of your app will be exempted. I don't know why. Try to delete temp apps with PowerShell:
Get-AppxPackage *app.a* | Remove-AppxPackage
This helped me a lot.
I had also come across a similar situation, I had resolved this using Fiddler which comes with a tool WinConfig in its menubar to restrict LoopbackExempt.
We have developed a mobile app using Meteor+Ionic2. We use our internal NodeJS server which is not in internet zone. We got the app deployed to our enterprise app store which enables AirWatch VPN tunneling to get the access to server in intranet zone.
Everything works great when tested with iOS device level using "F5 Access" VPN when deployed using Xcode or enterprise app store with NO VPN tunneling . But when download the app from our enterprise app store which does per-app VPN using AirWatch VPN Tunneling, iOS app gets stuck at the splash screen. It is not seems to call any client side or server side code of Meteor+Ionic2.
When redeploying it using development distribution, It seems to be stays at about:blank and not going to localhost and getting "Failed to load resource" error in about:blank.
The same AirWatch VPN Tunneling works great in Android. This issue seems to be happening only in iOS. I checked device level logs and also AirWatch VPN tunnel logs which donesn't report any errors.
I'm not sure whether Meteor+Ionic2 supports AirWatch VPN Tunneling for iOS as none of framework codes get called. Is there anyway to debug the enterprise distributed app? Is VPN-Tunneling not supported in iOS app development using Meteor?
Thanks,
Annadurai.
The root cause of the issue seems to be AirWatch config which causes the localhost to be appended with domain name like localhost.mycompany.com. As AirWatch couldn't fix this issue, we dropped plan of using AirWatch VPN tunneling.
I've developed an Android app relying on a REST server. The app works great on mobile network and also on my WiFi.
But when I try it at the university, it cannot connect to the server. The connection is an https on the standards ports (which aren't blocked). If I try to load the server URL in chrome it can reach the server.
I don't think it's a code related issue because some other android apps don't work here either. I think it's a firewall rule but what?
When I curl the the address of the server (the same as the android app), it returns correctly. Is it an user-agent filter or something like that ?
I don't know if it can be the cause but I self-signed my ssl certificate. Can it be related ?
What can cause this issue ? Is it a solution on my side ?
Deployment failed: 1
Error: Cannot connect: Connection to https://192.168.79.131 refused. Please check IP address settings for the target. You may have to reboot the target.
My app deploys fine in Air, but I can't get it to push to the simulator. Whenever it gets to the point where it tries to install the app, I get the above error. I've checked and made sure that the IP adress is correct. I've searched high and low on the internet, and nothing I've found has worked. So, if anyone has any ideas how I can install the app on the simulator please let me know. By the way, it used to work fine with Burrito, if that means anything. Thank you. :)
Have you tried ping 192.168.79.131
And checked there is no firewall rule preventing access to that IP address from your host (i.e. PC)?
Check if your PlayBook is on the same networks as your PC.
if your PlayBook is 192.168.79.131, your PC migh be 192.168.79.xxx, else you wont access it.
What you can try to do is change your network settings of your vmware to use a bridged network instead of NAT.
Shutdown the simulator and then locate the settings option. Under network settings select bridged. Resart the simulator. refer the below link
http://supportforums.blackberry.com/t5/Native-Development/Deployment-setup-wizard-issue/m-p/1388315#M173