I ran into this error this morning when I tried to run a new App in the simulator and I have not clue why. There is no stacktrace or anything like that, the picture is the only output there is.
I am not doing anything special, I only followed the tutorial on how to access Webservices and that happened when I tried to launch it for the first time.
I came to the solution, that it was my eclipse having trouble to start the app besides a running spring rest application, that I set up for testing purpose.
Maybe the two plugins don't like each other.
Related
I've added detox to our project and configured it following the documentation. I have set permission for clearText as documented in https://github.com/wix/Detox/blob/master/docs/Introduction.Android.md#problem-the-app-loads-but-tests-fail-to-start-in-sdk--28 but I am still receiving the same error. I have tried running the example tests from the Detox project on my machine and it's working fine. I've compared all configuration between the two projects and I'm positive it's the same. The only thing that strikes me as odd, is that the app is not even being launched when I get the error. Y'all have any clue on what the issue could be?
Solved: In the end it was a generic error related to a crash happening on the native side. Turns out that it was related to SOloaderand this fixed the issue. :D
I'm having a real difficult time setting up React Native on Visual Studio Code on my mac. I have read multiple tutorials and watched youtube and Lynda videos on how to do it - follow the steps exactly as they are presented, but still it doesn't completely works. It seems like every other terminal command I run gets an error.
I have managed to get it running on my physical iPhone and in the Android emulator. But when I try get it up and running on my iOS simulator using the appropriate terminal command, it won't work. The simulator opens, but then the terminal seems to get stuck loading and the app isn't showing in the simulator. There's no error, but it doesn't run.
Another thing is that I don't seem to find the index.ios and index.android files respectively - just a single App.js file.
I guess what I'm asking for is a good thorough guid on setting it up. Most guides I come across seem to leave out or under-explain certain steps, assuming that you already understand certain concepts. Please post a link if you know any super guides :) Thanks!
I'm trying to run an app made on Titanium in my cellphone. At first it was working fine, until i decided to debug my code. After that whenever i try to run it on my cellphone, it gets stuck # the powered by titanium screen (that red one).
I tried to delete my build folder as some people said after a bit o research but it won't work.
How can i solve this?
What I would try to do is:
clean the project (it also deletes the build folder, but I think it also cleans some more stuff in there).
when the app starts try to set an alert in app.js as the first thing - see if this alert shows, and if it does - move it to the next step until you find a place where it is no longer shown which might indicate that this is where you problem is.
Look at the device logs - if it's an android device open ddms and look at the logs while you run the app - see if anything pops up. If it's an iPhone on xCode you have some sort of console viewer for the phone (sorry - can't remember the name right now).
make sure you are not still running under debug mode.
BTW - you didn't mention if it happens on iPhone or Android? does it happens on the simulator as well?
I was having the same issue. From digging through Appcelerator's Jira I found we weren't alone, and also got a workaround that allows us to get past the splash screen. Check to see if there is a deploy.json file located in your application's directory on the device. If so delete it!
Here is more info on the issue https://jira.appcelerator.org/browse/TIMOB-16086.
It's rated as a high priority to be corrected for the 3.3.0 SDK release.
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
I have such problem
I am making an application with xcode 4.3.1 iOS 4.0 as target.
I have default picture as starting image.
I am using core data.
When I start application then type some info into it and then push it to background. Its all ok. If I try to start after I went to background it become crash after start image is loaded. Second launch is good without crashes. When I try to start application with some delay it does not crash.
The problem that I have no errors in debbuger and no logs about crash in iPod. All seems well.
If you had such problems, please say how you fix this issue.
P.S. Sorry for my English
You can try using logs and check out Xcode's organizer's console for your device so you can get additional info about functions that were called last.