Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would suggest the following debugging steps:</p> <p>a) Go to your device browser and browse to http: //xx.xx.xx.xx:8080/console</p> <p>-> If this doesn't work, you have an obvious ip address issue. Then you have to figure out why, maybe you have a Symantec thingy that blocks any incoming traffic to your desktop - which they do. You should do an explicit allow.</p> <p>b) If a) works, then you need to check in your code to make sure your app does try to connect to the server at startup. Or else the app will only try to connect when it calls adapter. </p> <p>Now, go to your code. open the initOptions.js file. I typically, would set connectOnStartup to true, but also enable the onConnectionFailure so that it runs offline when there is no connection. </p> <p>var wlInitOptions = {</p> <pre><code>// # Should application automatically attempt to connect to Worklight Server on application start up // # The default value is true, we are overriding it to false here. connectOnStartup : true, // # The callback function to invoke in case application fails to connect to Worklight Server onConnectionFailure: function (){wlCommonInit();}, // # Worklight server connection timeout timeout: 2000, </code></pre> <p>};</p> <p>3) Make sure you have the right URL in the application-descriptor.xml</p> <p>&lt;worklightServerRootURL&gt;<a href="http://xx.xx.xx.xx:8080" rel="nofollow">http://xx.xx.xx.xx:8080</a> &lt;/worklightServerRootURL&gt;</p> <p>If you are using the consumer edition (the real purchased WL), your URL would be. &lt;worklightServerRootURL&gt;<a href="http://xx.xx.xx.xx:9080/worklight" rel="nofollow">http://xx.xx.xx.xx:9080/worklight</a> &lt;/worklightServerRootURL&gt;</p> <p>(Note no space in between those URL - it's just this website putting a space there when there is a line break)</p> <p>Redeploy your code to the WL server and create a new APK file. Update your device with the new APK file.</p> <p>4) Do a test with the console again, you should see the console. Click on the Preview app link, it should work.</p> <p>5) Now that you have updated your code on the server and the APK file. Open it up again on the device.</p> <p>Do you still see the error message?</p> <p>If things still not work.</p> <p>6) Go to the app setting, since you have enable offline mode, it would allow you to access the App settings (it's the 4th button in Android) Go to <strong>Worklight Settings</strong>. Select <strong>Server Address</strong> -> Add the worklight URL to the Server URL. When you go back to the app, this will automatically reload the content from your WL server.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload