i'm using kony mobile fabric i'm trying to access the hostname http://youxel--tech:8080/mfconsole
from my android device but it says ERR_CONNECTION_REFUSEDit randomly works and randomly stops working is there anyone has an idea about solving this issue
Related
I am trying to create a layout for our teams channel tab app but when running the app locally and inspecting it as a mobile device, teams throws an error that the browser is not supported.
Can anyone point me in the correct direction to develop my app for mobile use or how I can view the mobile app from the VS Code Teams Toolkit debugging tools?
I have tried to run the app in chrome and in MS Edge browsers and use the inspector device emulators in both but get the same error. I have also tried connecting via my local machine's IP /the FE port 53000 and also have had no luck there.
I used directly my mobile device (android) with Teams App installed for debugging teams custom tab (both phone and tablet worked fine). Connect your android device to your laptop/desktop (using USB), and then on the phone:
Enable USB debugging
Enable "Developer Preview" in Teams options
In the desktop chrome, navigate to chrome://inspect/devices and you should see your device there in the list available for inspection/debugging. You could probably also connect using local WIFI (?), but I have not tried that. Also never tried that with Edge, so not sure if it works.
https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/developer-tools#access-devtools-from-an-android-device
It's not possible to debug a Teams tab on iOS using Windows (or Mac). Using Dev Tools, we can debug Teams tab in desktop and Android clients.
Ref Document: https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/developer-tools
Let say I have an angular project on local, separating back-end and front-end. After starting my BE, I am able to consume my front-end accessing http://localhost:4200/ in browser.
If both my BE and FE have been started, is there a way to access http://localhost:4200/ or http://[myipaddress]:4200/ in an iOS simulator safari, so that I can see my staging result in the simulator?
I know Chrome and any other browser is able to simulate mobile devices in device mode, unfortunately, there are results in a real device that are different than that in device mode. Thus I really want to find a way to see the bug fixing result in an iOS simulator without deploying to production.
I tried to set inbound rule for port 4200 and accessed http://[myipaddress]:4200 in safari in a simulator , it said 'Safari could not open the page because the server stopped responding'. (myipaddress = IPv4 Address in ipconfig).
Any hints?
You may have something in your specific setup stopping you from doing so, but you could just use the simulator included with Xcode, which should have no issues connecting to your localhost address on a given port.
Hi I am developing an app and it is working great in Emulator or in my android device through my USB cable but when I try to run my app using Xamarin Live Player it showing debugging errors as shown in image below
Please suggest me what to do as I really want to use this feature it's time-saving!
I am developing a DayDream app and working with a Pixel XL and real DayDream Controller (on a MacBook Pro). I would really like to be able to test with the DayDream Controller when running the app from Unity Editor. Currently, I am forced to make a build for every little change and its killing me (slow).
I believe that I can do this by connecting my Pixel XL via USB cable to my Mac and then using adb to configure it. But, all attempts have failed so far.
I don't know about real Daydream Controller, but you can try using your phone as DayDream Controller Emulator.
As it said here, you should download emulator APK from here, install it and run on phone connected to WiFi.
In your Unity project find GvrControllerMain and change Emulator Connection Mode to Wi-Fi. Also find Assets/GoogleVR/Scripts/Controller/Internal/Emulator/EmulatorConfig.cs and change line to IP address displayed on daydream controller emulator app on phone.
// IP address of the phone, when connected to the PC via WiFi.
public static readonly string WIFI_SERVER_IP = "192.168.0.78";//"192.168.43.1";
Click "Play" in Unity, it should work.
In addition to diesersamat's answer, I would like to add two things:
You could run the controller emulator via USB by choosing "USB" from the Emulator Connection property of the GvrController script that is attached to the GvrControllerMain component. For the USB connection to be made, you have to make sure that %AndroidSDKHome%/platform-tools is added to your PATH variable.
You could use the real controller via Emulator: Open the Controller Emulator app --> open the Emulator's overflow menu --> select Switch to Real Controller. For this to work, the phone that runs the emulator has to be Daydream ready. I usually use the same phone that I use for Daydream VR as a controller emulator.
At Google I/O 2017, the Daydream team announced instant-preview which supports a "headless" controller-only mode.
The repo is on github: https://github.com/googlevr/gvr-instant-preview
The moment in the Daydream keynote where it is mentioned is here: https://youtu.be/tto90e-DfeM?t=26m45s
I had the same problem trying to get the emulator to work. The solution for me was to set up the player settings to android and click the VR supported tab with the daydream SDK selected in the VR SDKs dropdown BEFORE importing any daydream/google VR packages.
Took a lot of trial and error for me to figure that out. Hope that helps.
I enabled debugging over bluetooth on my Moto 360
and enabled Android Wear app on my Nexus4.
Status displays target : disconnected
Forwarding the port from my computer shows the status host will be changed to connected, but the target status remains disconnected.
I toggled debug via the bluetooth switch which had no effect.
My phone is a Nexus 4. Is there a problem with my phone or the Moto 360?
I eventually managed to get it working. The issue seems to be related to having paired your device with an emulator first. Take a look at this post to see how I fixed it: http://melix.github.io/blog/2014/10/android-moto360.html
open the applications settings, search for the Android Wear application, then force stop it
clear its data and cache
Search for Google Play Services
Click on Manage space. Delete all data.
reboot your phone
reset your Moto 360
Pair watch with phone
Following the instructions from android.com https://developer.android.com/training/wearables/apps/bt-debugging.html to setup debugging and it should work now.
Done.
I tried it on a Sony z1.
It succeeded without any problems.
So, maybe it's not supported perfectly in Nexus 4.
If you have the same problem, I suggest using another device.
I fixed without factory reset with these steps
-Force stop android wear application and clear cache
-Disconnect emulator on android wear app
-Forget emulator on android wear app
-Connect your real device via bluetooth
-Open debugging over bluetooth
Make sure that debugging options are also active in android wear device
Run this commands in command window:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444