Member Avatar for castajiz_2

The title says everything, I was searching through google why this is the case but haven't been able to find any answers.
Any reference would be greatly apreciated...

  • 2 Contributors
  • 2 Replies
  • 241 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by castajiz_2

Dani AI

Generated

Emulator behavior is not a reliable substitute for a physical phone when networking or security is involved. The emulator uses the PC network stack and often reaches hosts or accepts certificates that a real device will not. Common causes when HTML loads in the emulator but not on-device are: missing network capability in the app manifest, calling a host reachable only from the dev PC (for example localhost), TLS/certificate or cipher mismatches, carrier/Wi-Fi restrictions, or exceptions that are swallowed by the app.

A short, practical checklist to isolate the problem:

  • Open the same URL in the phone's browser. Failure there points to network/certificate issues outside the app.
  • Verify manifest capabilities: for Silverlight projects inspect WMAppManifest.xml (ensure ID_CAP_NETWORKING or equivalent is enabled); for WinRT/8.1 projects open Package.appxmanifest and enable Internet (Client) or Internet (Client & Server).
  • Confirm the app is not targeting localhost/127.0.0.1. The emulator can reach the dev PC; a physical phone cannot. Use the PC's LAN IP or a public endpoint and allow the firewall and server to accept external connections.
  • Try both Wi‑Fi and cellular networks to check for carrier or AP restrictions.
  • Add explicit try/catch with logging so any exceptions are not silently ignored.

Example minimal pattern to surface errors and logs:

async Task<string> FetchHtmlAsync(string url)
{
    try
    {
        using (var client = new HttpClient())
        {
            client.Timeout = TimeSpan.FromSeconds(30);
            return await client.GetStringAsync(url);
        }
    }
    catch (Exception ex)
    {
        System.Diagnostics.Debug.WriteLine("Fetch error: " + ex);
        return null;
    }
}

For deeper diagnostics, capture traffic with Fiddler: enable remote connections, set the phone's Wi‑Fi proxy to the PC, and install the Fiddler root cert on the phone to inspect HTTPS. As noted, deployment/registration must be correct, and since indicates deployment was done, the most productive next steps are the manifest check, browser test, proxy capture, and collecting the debug output. Most cases turn out to be either a missing capability or the app pointing at a host the phone cannot reach.

Recommended Answers

All 2 Replies

Member Avatar for peter_budo

Without any actual error people are not gone be able to help you.

Also please make sure you folleoded instructions how to deploy to device and that device is registered http://goo.gl/TPK2uU (I had to use google url shortener as daniweb formatting did not liked msdn url format)

Member Avatar for castajiz_2

No errors are shown, all the instructions have been folowed this is fourth app that I have uploaded, everything worked fine previously. The thing is that I'm reading HTML from a webpage. I don't get any erros whatsoever on the emulator, but it seems that I can not fetch the data on the actual device. I'm stuck in a deadpoint where I don't know how to move on since no erros are show (as mentioned before).

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.