Application stuck at "Powered by Titanium screen" - titanium

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.

Related

Stuck on Downloading Javascript Bundle 100% - Expo

I guess that I've tried every solution that exists on the internet about this issue, and nothing works, and I don't even know where to look anymore. It started to happen from nowhere and I can't even open the app settings shaking the phone, it's completely stuck on this screen.
I cleaned up NPM, Yarn, Expo's caches and disabled the Remote Dev Tools.
I would be so much thankful for any help.
In my case it was due to the a remote debugger.
I left the remote debugging on, put the mac in sleep and when I turned it on again the iOS Simulator remained stuck at bundling 100%, irrespective of what I've tried (kill simulator, expo r -c, Reload app, etc.)
However, I could have realized the root cause earlier because on the physical device it was working the entire time.
Hope this saves someone some time.
You could try reverting to your last known working commit, then incrementally adding back the changes until this happens again. This often is a result of delaying hiding the splash screen (perhaps via AppLoading or SplashScreen) and then not hiding it because of some error in the app code preventing the code to hide it from being called.
Try Disable Debug Remote JS in the IOS Simulator
by clicking ctrl + cmd +Z on Mac
It works for me.
Seems like something is wrong with the dependencies, just close down the react-native environment ( android studio) and your IDE, just closing and restarting may work if not, check for updates or delete and reinstall your dependencies ( expo i )

Successfully setting up React Native in Visual Studio Code for Mac

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!

Adobe Air iOS app - blank white screen

We have a fairly large air app, and for some reason, when we package it for iOS, it does not launch correctly. Just a plain white screen. When we launch it in debug mode (or even using Fast packaging), it works fine. Only with the export release build it simply launches a plain white screen and does nothing.
Anybody seen anything similar? Any idea if there is an error of some sort, any way to find out what the error is?
SO it turns out after hours of struggling with this is the issue was loading swf files. We had some embedded Image assets that were swf files, which works great in debug mode, but fails spectacularly in release mode. Given that the app we are working on is a behemoth that takes over 30 minutes to build a release version (on a very powerful box), this was quite a pain to nail down. We finally converted swfs to fxg and the error went away
I've just experienced a similar white screen issue when building an AIR iOS app (in any mode). The app builds and launches with no errors but just displays a white screen after the launch image has disappeared.
This issue was different to the one above but I want to post this here for future reference.
It turns out that this was due to incorrect read/write permissions on the source files. i.e. I had copied the source files onto another computer and then logged into that computer as a different user.
The solution was to simply re-copy the source files onto the computer whilst logged in as the correct user.

iOS Simulator Crash Logs

When I use the iOS simulator and the app crashes, I can't find the crash logs. I've been looking all over the internets and can't figure out how to enable them. I know I can just run on an actual device and get the crash logs that way, but the bug I'm trying to fix right now tends to cause the program to be hung in the debugger. Then there's no qlaunchsuccess packet sending and it's a huge pain, especially when I have to run the program over and over. The only advice I've been able to find says the use CrashReporterPrefs, but a search of my hard drive reveals nothing named something even close to this. I've also dug into the package contents of XCode and the files of the iOS simulator. The iOS simulator has a crash logs folder, but it is empty. Anyone know how to get this working? Thanks.
Run your App with Xcode to install the App to iOS Simulator
Launch your App on Simulator without Xcode
reproduce steps for crash
the Crash log should show up under this directory
~/Library/Logs/DiagnosticReports/
It appears if you aren't running Xcode (mine is 4.5.2) but just the simulator (mine is 6.0) that when an app crashes it does save a crash report. To view it bring up the Application/Utilities/Console and
(1) make sure it shows the log list (see top left of console to make sure not hidden)
(2) under "DIAGNOSTIC AND USAGE INFORMATION" there is a "User Diagnostic Reports" that if you open up should have your crash reports
(3) the area on the right of the console has the log
A Crash log is just an output of what the debugger already gives you. When you are running in the simulator attached to the debugger, and you hit the crash, you can view the back trace information in the debug navigator (default key binding is cmd+5)

Cannot run project after updating Xcode project settings

Recently I updated my project settings as Xcode recommended. I just pressed a button and they did "everything". However now when I try to run my app on my device it freezes on the loading bar at about 75% and then after 15 seconds it says "build succeeded" but does not run on my device and everything stops as if I had pressed the stop button. I am getting no errors but I am getting the following warnings. It works on the simulator just fine.
For the record I have looked this up and everyone says to add "armv6 or armv7" and I already have this done. I am running deployment target iOS 3.0+
If anyone can help me, it would be appreciated. Thank you!
EDIT
Works on my device when I run leaks in instruments... but won't without instruments
Well, I can't really say much specific here, but if all else fails, I'd try making a new project and copying the content of this project to the new one. This could fix some underlying problems that may have developed in the build settings etc.