I have a cordova/phonegap app that is supposed to connect itself to a websocket server. It works fine on ios & android 4.4 but not on my Samsung Galaxy Tab 2 running android 4.2.
I know that the webview in 4.2 doesn't have a native implementation of WebSockets but I loaded a phonegap plugin for this. The plugin loads successfully and I waited for the deviceready event before attempting a connection. When I try the example provided by the plugin, the onerror event is trigered but I have no additionnal details.
Running the app using Google Chrome on the same device works, so I exclude a network issue. The application has the INTERNET permission. I'm a little out of clues at this point, any ideas are welcome :-)
Ok, after taking a look at the adb log as #Nicholas suggested (thanks!) I had an exec() call to unknown plugin. Somewhat following this answer solved the problem.
Related
I have to debug some problems on website I recently created that occur only in native android browser on some tablets. I don't have access to physical device so I decided to to install Android Studio and created tablet AVD(android virtual device). Process run smoothly and now I can open native browser in virtual device and check my website.
I can see the same errors as those reported on tablets(that's great) but I cannot figure out how to run any kind of devtools in native browser. Even access to console output would be enough.
I'm running android studio on Ubuntu 18.x LTS, but I guess my question is not platform specific.
I would prefer any solution that can be run on virtual device(like some additional app that acts as debugger), even if it would give me only console output, over more sophisticated ones that require more complicated configuration.
But, honestly, I would really appreciate any kind of help.
you have to use the Chrome debug bridge; accessible through chrome://inspect on the desktop browser... connected devices will show up there, as long as USB debugging is enabled; that should work with an emulator, as well.
I have a hybrid mobile application which works on both android and ios devices.
The problem with it is that the application works fine when run on Android. However, there is a Network Error: XMLHttp Request Exception 101: saying server is unresponsive while running the application in iOS.
The application uses Cordova 2.9
I have been trying out solutions like setting async to true(initially it was false). But it does not solve my issue.
Can you please tell me the reason and the solution to be provided.
Thanks.
Make sure that you are using JSONP data format in IOS. This same as Json, but a callback function is needed.
I've tried building an app using Android open source Bluetooth chat sample project. you can find the source code here: https://github.com/googlesamples/android-BluetoothChat
The problem is that the sample itself has a bug sometimes two way communication fail and one of the two devices fail to receive messages
you can find the problem in this video: https://www.youtube.com/watch?v=zVyW7yBBwa0&t=4m16s
I've tested it using Samsung GT-N7000 running 4.1.2 and Samsung Galaxy Mega running KitKat.
Can anyone help me figure out how can I edit the source code to fix this bug as the two devices fail two way communication each time I try to connect them using the app.
I've used Android Studio to build the signed apk.
I'm working on a web app for note-taking called VideoNot.es (http://videonot.es). This app is build with AngularJS and webapp2 and hosted on the Google App Engine.
My app is working fine on Chrome for the major OS (Windows, Mac, Linux) but some users have started to report issues with Chrome OS (mainly teachers with GAFE accounts).
I've decided to run it in Virtualbox and there is effectively an issue.
The app never receives answer send over the Google Channel API (https://developers.google.com/appengine/docs/python/channel/overview) while the backend is logging that it sent it. I had received reports before we moved to it so it is not really link to it.
I really don't understand what is wrong here.
Thanks for your help.
If it's a bug in the Javascript, you'd want to file it on the issue tracker. I haven't noticed much progress on Channel API bugs, so I wouldn't expect much though.
I'd recommend working around it by polling, or another solution, like Node.js hosted elsewhere.
I'm evaluating SignalR technology for use in our new product (mobile web application for the broad audience, among other things it needs a real-time chat on some pages).
I've followed the guide to create a very basic chat demo.
Then I deployed the demo on my IIS, and started chatting to myself.
All clients were on the same WiFi network.
Desktop browsers worked more or less OK.
However, Safari on iOS 4.2, and IE on WP7.10 - they both sucked.
Sometimes nothing happened when I pressed the "post" button.
Sometimes outgoing messages were sent OK to the desktop firefox, however there was no incoming messages.
Maybe I'm missing something obvious? Maybe I need jquery mobile instead of the normal one? Maybe I should just tune the IIS/web.config/whatever, and the SignalR will flourish and start to work flawlessly even through the crappy mobile internet?
Or does it mean that since it doesn't work even while on WiFi within a single hop from the web server, I should throw SignalR away and just write some JavaScript to poll a JSON endpoint for new messages?
Thanks in advance!
I have been developing an app with phonegap (that means that uses the Safari browser) and SignalR for Android and IPhone. The major issue I had was with iOS 6.x because SignalR did not connect with default config. I have found a workaround for that and I had explained it here. Let me know if you find it useful.
This code will simulate a connect, check for messages, disconnect and wait 5 secs to solve the iOS issue.
In js add
$.connection.hub.start({ transport: 'longPolling' }).done(function (myHubConnection) { });
and in Application_Start() add
GlobalHost.Configuration.ConnectionTimeout = TimeSpan.FromSeconds(1);
Microsoft.AspNet.SignalR.Transports.LongPollingTransport.LongPollDelay = 5000;
RouteTable.Routes.MapHubs();
Not all mobile browsers (e.g. android, opera mini) support websockets. You'll find a nice chart of supporting browsers at http://www.hanselman.com/blog/YourUsersDontCareIfYouUseWebSockets.aspx