ok, so I am running this phone gap app in Xcode4. It finally runs fine in an iPad simulator. I was even able to make it work in a real iPad device. Then after couple of times downloading the code from Xcode to iPad, it started giving me this error:
int retVal = UIApplicationMain(argc, argv, nil, #"AppDelegate");
The app just gets stuck there. I am new to this and really need help with this.
You may be having an issue with the linked Phonegap files. Try doing a clean and then a run build.
Unfortunately, when the app fails on the Main line it doesn't help to debug the error any. Check the console and try hitting the continue button to see if it throws a better error.
Related
I'm writing this post because I don't know what I can do.
I'm developing an big app for iOS with a lot of users for my company; to log error and crashes I'm using Microsoft MobileCenter (Analytics and Crashed ver. 0.6), Xamarin.Forms ver. 2.3.3.168 and a lot of components such as Xam.Plugins, SQLite, PCLStorage, SharpZipLib.
As MobileCenter request the minimum target version for the app is 8.
Apart from minor bugs, the big problem is difficult to explain. I'm trying to ask you an advice.
The app is working fine. If I test it, I can't have any problems. At same point the app crashed for any apparently reason. No logs, no crashed, no nothing in MobileCenter. From this moment it's impossible to start the app and I can't have any logs about it: I can see the splash screen but after than the app is crashed again. It seems the problem raises after taking photo with camera.
When the app starts, it deletes images (if there are any in the folder), send a file to my server, and check with CrossDeviceInfo what the OS version is. Then the first page is called.
I tried to understand the problem to read the log in Xcode after connecting my device to my iMac but it's incomprehensible.
If I try to read the View Device Logs I can find one crash for my app but the log is still incomprehensible for me.
Then from Xcode I tried to open Organizer and under Crashes...
If I connect the device with this issue to my iMac and I deploy the app on it, the app is working fine. How can I understand where the problem is to fix it?
Update
In my App.xaml.cs I initialise MobileCenter like the following code:
public partial class App : Application
{
public App() {
// my code
}
protected override void OnStart()
{
MobileCenter.LogLevel = LogLevel.Verbose;
MobileCenter.Start(typeof(Analytics), typeof(Crashes));
}
}
It's Benjamin. I've already replied to you issues in our intercom but I wanted to reply to your issue here.
This scenario is not an actual crash but a kill of the app process by the operation system. The SDK runs as part of the app process and therefor can’t ever figure out that this kill even happened because the process is fully removed right away. Technically this is not a crash from an SDK perspective that it can detect and provide details for. Every single 3rd party SDK has this limitation and there is no way around it as Apple doesn’t provide the technical possibilities to do so.
In addition, none of your provided crash reports contain any reference to Mobile Center thus I can rule out our SDK is the cause of the kill.
I hope you find the cause for the issue.🖖
It runs just fine on the iPhone. When I select the Watch App Target, however, it simply won't run on the watch.
I don't get any errors or anything. I can see the app downloading on the Watch sometimes; when it does download, it deletes itself the moment the download is complete.
I've tried uninstalling the watch app and reinstalling via the Apple Watch app on the iPhone, and the same thing happens: it downloads and deletes itself before I can run it.
I've also reset the watch, reset Xcode, deleted the iOS app, and just about everything else I could possibly think off, but I'm starting to lose my mind.
The problem started happening when I (attempted to) set up the Watch Connectivity framework. I don't know if this is related. I've been unable to verify that WC is working properly as I can't open the app.
I've been lucky enough to get it to actually load on the watch only a few times since integrating WC framework, but even when I have, all I got was the loading screen for about a minute each time.
UPDATE:
I'm now seeing some consistent behavior.
I'm now able to debug my app by launching the watch app via Xcode. The app icon does not appear at all on the watch when this happens, however. (Weirdly enough, it shows the launch screen for a different watch app when launching.) So I can't run the app at all unless it is launched from Xcode.
Also, I am not able to download the app to the watch via the phone. I want to be able to run it outside of debug mode, and I can't. When I attempt to install it from the Apple Watch iOS9 app, the install begins, I see the icon on the watch as it downloads, and just as it finishes, it deletes itself from the watch before I can run it. This just keeps happening.
Please help!
Make sure your Apple Watch device ID is in your provisioning profile.
So, this kind of sucks as an answer, but I've had enough.
I decided to copy all of my code and storyboards into a new Xcode project. The Watch App now works exactly as it should. Hopefully Apple sorts out these bugs in an update.
I believe repairing the watch would help as well. I had the same problem before and the only thing which helped was repairing the watch.
I also have other issues debugging the watch app properly - see my question here Proper way to debug watchos2 app in XCode7
I'm using Xcode 6.1, iPhone 6 simulator for my Appium automation tests.
I'm having a trouble of reset iOS simulator. The first time after reboot using simulator is always fine. But if I quit the simulator, and tried to use it again (both manually and load using Appium tool), I'll keep getting blackscreen for simulator. I got the following info from my automation log 'Could not reset simulator. Leaving as is. Error: Command failed: // stderr'
I've tried the 'Reset Content and Settings' from simulator, it would not help. I still getting the black screen. and I've also tried to kill the simulator from command line using 'killall SimulatorBridge', still not work.
The only way that I could get this working is - reboot my laptop... this gives me a big pain. I'm thinking if reboot could help, there must be some process that I could kill to reset it? Anyone could kindly give me some help here? Many thanks!
I know this is an issue that was already discussed here many times before, But there is now solution for my problem and its really serious.
Every second time I try to run the simulator i get get this bothering message:
"The Simulator can't be launched because it is already in use."
Closing the simulator does not help.
I need to quit Xcode every single time this happens!
I trying restarting my computer several times.
Please help me, I find my self restarting Xcode 50 times a day. This is totally frustrating.
Very simple, to avoid further problems we will do "complete" procedure.
On iOS Simulator, you must force quit.
In Xcode, press COMMAND + SHIFT + "K" (letter k) keys; to empty the cache of the application and ensure that all works out.
On then quit Xcode (I recommend that you restart your Mac after this procedure done, if the problem persists)
Good luck
I had the same issue. Turned out that the developer tools path was set to a different location than the Xcode I was using. So check with
xcode-select -p
that your dev tools path is set correctly. If not, fix with
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer/
if you're using the current AppStore version of Xcode (or the appropriate path to your alternate Xcode).
I think it a bug in Xcode 5.1. Update your Xcode and it will resolve your issue
and i use this solution for this issue. "Close all application from background and then run"
To close application from background use
Select simulator then press "Ctrl+Shift+H+H" So it open background task screen in this close all application from background and then run your application from Xcode.
i hope this will solve you lots of time of restarting the Xcode.
Solution that seems to be working :
double press CMD+Shift+H (in simulator )
close All other apps on
sim.
Works for me. Let me know!:)
I have a creationComplete="myMethod(event)" in my s:Application, and it runs fine on my 3 flex (Flash Builder 4) development machines. However it is not working on the 2 end user machines I tried it on today!
It is not executing the creationComplete at all, but it is running the application and it seems like all the other code is running fine - with the exception of possibly some other creationComplete code for other components in the app.
On my machines I have tested it under IE 8 and 9, FireFox and Chrome - on all 3 machines.
On these two machines it has the problem on both IE 7 and IE 8. I even installed FireFox new and it also has the issue. After installing the latest flash player and deleting all browser history/cookies it still has the problem.
What might cause the creationComplete to not execute?
Update:
I tried using initialize() and no difference.
However, I believe I found the line of code causing the problem:
var isDebug:Boolean = new Error().getStackTrace().search(/:[0-9]+\]$/m) > -1;
If I comment that out, it works fine. Why? I need that to know if my app is running in development/debug mode or on an end users machine.
It appears (I haven't tested this myself) that you are unable to get the stackTrace of an error in non-debug mode?
That's my assumption from your description of the problem. If this is the case, you could just check if getStackTrace() != null.
EDIT: Confirmed, getStackTrace() returns null in a non-debug environment
Maybe this line throws an exception (that'd be funny, wouldn't it ? ) that you can't catch when in non-debug mode...
Have you tried this :
import flash.system.Capabilities;
[...]
var isDebug:Boolean = Capabilities.isDebugger;