I am running Worklight 6.1.0.1. I have a simple helloworld app. I can run the app on the android emulator. I instrument and create a Mobile Test Workbench project. I can connect the MTW client to eclipse and see the HW app. When I try to record a test, I get this error after the splash screen:
Application Error - The connection to the server was unsuccessful. (file:///android_asset/www/default/index.html)
Logcat shows the cordova loadUrlNow() but not much else. The app connects when I run it straight on the emulator, so its a bit perplexing.
One of the attempts spit out this message: E/CordovaWebView(800): CordovaWebView: TIMEOUT ERROR!
(Usually logcat was was just full of "RMoTIDLE: Thread[main,5,main] main loop queue is idle" and "Skipped 56 frames! The application may be doing too much work on its main thread" and I didn't see the timeout.)
So just adding "super.setIntegerProperty("loadUrlTimeoutValue", 70000);" to the main java class fixed this problem.
(Obviously the emulator is not the best place to be test driving this feature)
Related
I upgraded a react native project recently from expo SDK 36 to 38. It compiles now, but anytime I click on "Debug Remote JS", it causes the UI to become slow and unresponsive, only occasionally picking up the on click events. I created a bare bones project to duplicate it. To verify, either run expo init from cli or here's a project https://github.com/seniordevops/tab-application.git. Click the tabs without the debugger on, then turn on debug remote JS and watch the slow down. Happens on both Mac and PC. Any ideas on the root cause?
This is mostly due to the fact that the clock on your PC and mobile are not synchronized.
You either have to synchronize them or have the phone clock one second earlier than your PC/Mac.
I suspect the reason could be an upstream problem of react-native. Please check this expo-cli issue:
https://github.com/expo/expo-cli/issues/2405
a maintainer reports:
when you are debugging on your device, the javascript is being
executed in your browser on your computer :(
I have a launcher app, it runs well on android 4.2.
When I transplant it to android 5.1， there is a question：
1.I found when I run a third app which has exception;
2.the third app crashed immediately and exit;
3.my lanucher crashed too;
logcat shows:
force to finishing the third app...
force to finishing my launcher...
and I use startActivity to run the third app.
sorry for my poor english, has anybody got any good ideas or ways for that?
I've been developing a react-native app using the simulator for a while. On the simulator (iOS), the app loads very fast (on reload for eg). However, when I tried to load the app to the device, it spends between 1-3 minutes in the splash screen before loading into the app.
My project is fairly small, and has no extra resources other than the javascript. Looking at the documentation I couldn't find what might be the cause of the issue, though I suspect it has to do with the fact that it is not getting the JS from the packager local server.
What am I doing wrong?
(btw - react-native v0.31)
I ran into the same issue and discovered that it was because I was running my app on device in development mode. To get the performance you're looking for, you'll need to build and run the app in production or "release" mode. You can do this by passing in a --configuration option and setting it to Release using the React Native CLI:
$ react-native run-ios --configuration Release
If that doesn't do the trick, then you may need to build your app in "Release" mode from Xcode. To do that, navigate to your projects /ios directory and open the .xcodeproj file in Xcode. Choose your build target in the Toolbar. Scroll to the bottom and choose "Edit Scheme...". Then under Build Configuration, switch from "Debug" to "Release". Now build your app on your target device and it should be much more performant than before.
You can read more in the official React Native documentation under Running on Device: Building your app for production.
For me the issue was related to the wifi network of my development machine. I was using WPA2 Enterprise auth to connect to wifi on my development machine. I found that if I used a wired connection to connect to my network or if I used another wifi connection that used a different form of auth then the delay went away. I think the delay is a network timeout.
i ve developed an iphone application.i was able to install the application and was working properly.in the past two hours i m getting error while installing the application in the device.i tried restarting my device and mac but its in vain..could u guys help me out.
below is the error
Couldn't register com.upspl.bigbapp with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.(lldb)
Did you try to restart your Mac or kill the Debugger? You can also try to press cmd+. to stop the process.
For other references, take a look at similar posts:
iPhone - strange error when testing on simulator
Couldn't register […] with the bootstrap server
You can try: delete your application from device and iTunes, restart your device, and then relaunch it.
I've installed Appcelerator Titanium Studio on a PC and I was not able to run the android simulator on it, so I was saying to myself "it should work on Mac at least"... and I installed a new Mac with Titanium on it, downloaded the SDK, then I imported the Kitchen Sink example and configured the run configuration with the default settings... and I'm getting exactly the same problem which is an infinite loop with the 'audio_flinged died' problem! So the best I can do is to view the Android simulator with the black window and "Android..." written on it.
What can I do to finally launch that example that is supposed to run? The best I did with my Windows 7 setup was to get the screen of an android cellphone WITHOUT any app on it (default apps), so it's pretty unuseful.
I'd really like to see what Titanium is capable to do.
The Mac ends (after a few mins) with "Launching New_configuration" has encountered a problem. Session initialization failed. "Session initialization failed Failed to get version"
The problem of the infinite loop with "AudioFlinger" still persist in the two cases (PC/Mac).
Any help would be greatly appreciated.
I helped someone with a similar question. He was getting a error which you don't seem to be but my answer walked him through checking the configuration was ok etc.
might help you:
Error running Android emulator from Titanium Studio