Why my app immediately quit after open in iOS simulator? - ios

I installed Xcode(9.4.1) from App Store and create a iphone simulator.
After that I tried to install some .ipa(https://github.com/OWASP/owasp-mstg/tree/master/Crackmes/iOS) app to it but it immediately quit when I opened it.
I tried couple app but the error is the same But when I wrote sample app on Xcode and build to my simulator it run very well.
Even if I try another iphone simulator or reinstall Xcode, I still get same error.

you need to find where is the error located in your application ,
here is a link reference explaining about how to find the cause error
also it will explain the most common mistakes in xbasic
click here

Related

This app could not be installed at this time.Xcode 9.2

I have changed my application name and bundle identifier and now when i'm trying to run my app it is showing an error that This app could not be installed at this time . Why it is so? Why it isn't running the app?
I know the question has been answered but for others encountering the same issue I suggest following:
Check simulator logs, if its printing something useful. First, selecte simulator then from menu option open Debug -> Open System Logs.
Make sure only 1 simulator is running.
Delete the older version of app from the simulator.
If you importing a custom framework, make sure custom framework->bundle-id is not same as currentAppProject->bundle-id. If you are not sure then simply change the bundle-id of current project.
Also some of the simulators can be buggy -> Simply change the simulator, it may resolve the issue, for me changing the simulator worked.

app iOS accepted by Apple, crashes at launching, but works after plugging iPhone to the Mac/Xcode

UPDATE 2 :
We have at last a crash log : https://www.dropbox.com/s/62sq0ybyr4mhkkh/Screenshot%202015-09-02%2012.26.54.png?dl=0
It seems that a library is not loaded...
UPDATE 1:
Here's what we have :
- no crash log on Xcode with a device where the app crashes at launch
- We didn't run the app via Xcode, we downloaded it via Diawi
- We plugged the iPhone on the Mac, we didn't run the app via Xcode, we just looked at the crash log (nothing to see). After we unplugged the iPhone from the Mac, the app launches perfetecly ! Besides, when we uninstall the app and install it again via Diawi, it launches perfectly again !
- So the simple fact that we plugged the iPhone to the Mac makes the app work.
Any idea ?
Below the first message
I have a serious issue with my iOS app, here's what we know :
The app has been approved on App Store
But if we download it via App Store promo codes (it's like a private beta), it crashes at launch, mostly on iOS 8.3 or below.
We had the same issue by adding UDIDs and sending the app via Diawi before the submission
We have already an app on the store (let's call it v1) and we have submitted a new version (v2) which has been a new project on Xcode.
The crash happens with people who had already the app v1 as well as people who hadn't
The crash remains even if you uninstall the v1 and install v2
We put crashlytics : impossible to get any crash report, it crashes before the init, although we can see the launch page with the logo. We tried to put a delay of 10 seconds to let crashlytics initialize, but it doesn't last untill the 10 sec
Weirdest thing : when we plug the device on Xcode to see what happens, then it works ! Impossible to see the crash again. Then, even if you uninstall and repeat the process by installing via Diawi, it will work ! As soon as you plug the iPhone on Xcode, it will always work...
Some people told us that it crashes and it works the day after.
What we did :
We updated the Pods
We changed the certificates and provisionning profiles and made it clean
We had some issues due to the Parse SDK, but we fixed it
The target is iOS 7.1
Here are the pods that we have (screenshot):
https://drive.google.com/file/d/0BzHfUya4Va4rb2dQSVJYazN1MFBxcG1DQnpBNXAybU9SVzk4/view?usp=sharing
Has someone seen already such an issue ? The weirdest thing is that Apple hasn't rejected it.
Thank you for your help !
So I had exactly the same problem today with my app Macro Defense: https://itunes.apple.com/us/app/macro-defense/id955086416?ls=1&mt=8
I found that by turning wi-fi off on the device, the app runs perfectly. If this is also the case with you, then my guess is that the problem lies in trying to perform some network functions in the appDelegate.
Have contacted apple support, and will repost if I get a definitive answer to this.
Cheers!

xCode 6 (beta 4) keep getting "The Simulator can't be launched because it is already in use."

I keep getting the "The Simulator can't be launched because it is already in use." when trying to run my app, this only happens about 20% of the time but once so far the only way to get around it is to restart my Mac.
Tried the following but doesn't help:
Cleaning my build folder
Closing and re-opening xCode
Force close of simulator
I'm Using xCode 6 (beta 4)
Any Ideas for a solution that doesn't entail me restarting my Mac?
Thanks
"The Simulator can't be launched because it is already in use.”
This messege will be shown only if there is another xcode project that has launched simulator and hasnt stopped it yet, and u try to run the simulator from another xcode project.
Ideally stopping the simulator from the respective project(PS. not closing the application from the simulator, clicking the STOP button) would do it,
But if it still is working like that, then Closing the simulator, or resetting the simulator contents.
If that still dsnt work, then as a last resort i would ask u to reinstall Xcode, as if this problem keeps going on, then ur downloaded file might be buggy.
P.S if u opt to re-download n install xcode please keep backup.
Hope it solves it. Although i want your problem to be solved by step 2.
This normally just happens when running an app (project) on the simulator and then trying to run another app while the simulator is open (and normally is still within the first app you launched and it can't quit automatically). As long as you keep running the same app you shouldn't get this error and as soon as you run another app just make sure you've closed the simulator before or at least left the previous app with the home button.
Just Restart Your Mac , It Will Fixed
I had the same problem and fixed it without restarting. You just need to reset the content on ios simulator, exit xcode, and then to make sure that you've completely exited, right clicking on the xcode icon on your mac nav bar and click Quit. Open it back up and it should work.

Xcode6 can't run any app in simulator ( Domain = NSPOSIXErrorDomain, Code = 3 )

No app can run in my simulator, although building is good.
Error messsage is below:
Unable to run app in Simulator
An error was encountered while running (Domain = NSPOSIXErrorDomain, Code = 3)
In my case, I tried to run the app on a iPhone 6 simulator when I got this error. Quitted the simulator only and re-ran the app on iPhone 5s (8.1) - it worked fine.
After a while I changed the target back to iPhone 6 (without quitting it), and ran the app against it - no error shown.
As mentioned in the Xcode 6.1 Release Notes and in my sticky post in the Apple Developer Forums for the iOS Simulator, this is a known bug in iOS.
Upon installation of an app, SpringBoard will SIGKILL that app's
process in order to force a relaunch of the app with the new
executable. The problem is that there is a race condition whereby
SpringBoard may accidentally SIGKILL a new process that we just
launched rather than the old process. Which of the various error
messages you get depends on exactly when in the launch process the
SIGKILL was delivered. Normally, this shouldn't happen, so the advise
is to just try again (sorry =/). If you find that this happes to you
all the time or more frequently than you can tollerate, we are
incredibly sorry. We are aware that systems with slower disk I/O will
see this happen more frequently than faster systems, so if you are
using an NFS home directory, you may want to create a local directory
for your simulator data and setup a simlink to it from
~/Library/Developer/CoreSimulator
By Quitting the Simulator and Run the application worked for me.
For me , just Reset Content and setting in your simulator
Restart Mac can solve the problem for me.
This error is less severe than "Domain = DTiPhoneSimulatorErrorDomain, Code = 2" error that I had when I switched to Xcode 6.
For this one, I just reset and cleared contents on my Simulator...quit. Rebuilt and ran my app...and it works.
Every time this has happened to me (as of this writing, still happening on Xcode 6.1) I do not need to restart my mac to fix it. Instead I only had to restart the simulator. I exit the simulator by right-clicking on its icon in the tray and selecting the option to Quit. The I re-run my app and the simulator starts from scratch and runs my app with no error. Much quicker than re-starting the mac.
Well, I had the same error popping up, but since I force quitted the simulator then ran the project again I got it fixed and running fine. Hope that helps you :)
If this error occurs with ionic framework, make sure you have an app id given in your config.xml
This is a generic error which says that it is unable to launch the app. The real error is in the log file. Go to the Simulator menu, Debug / Open System Log. Then press Reveal button to open the folder with actual Simulator logs. In my case it was CoreSimulator.log.
Here you will find the real error. My error was Could not register service com.apple.gputools.agent.producer.sim .
After a lot to struggle and trying all suggestions for half a day, I just went to simulator menu and chose File / GPU Selection / Use External GPU when available. That's it.
please download new xcode_6 beta 4. your project will work in simulator. As i have tested as well.
Sometimes the beta version of XCode is wrongly configured to use the command line tools from the previous xcode version.
This solution should fix the issue for you : https://stackoverflow.com/a/25415781/512504

ios Simulator Could Not Find The Application To Simulate

I'm having trouble with the iOS simulator. I'm currently on 10.7 and was using the simulator to test my website. During the testing, I switched the iOS version via the tool bar, and the application froze and quit. Upon restarting, I get the following error message, with a finder window, inviting me to choose an application:
"ios Simulator Could Not Find The Application To Simulate"
Here's what I've tried to fix the issue:
1: Attempt to identify the application it needs, but the only thing i could see to open was a printer app and the ios simulator app, which just results in a "only one iOS simulator can run at a time" error message.
2: Restart the Mac.
3: Download the new Xcode tools from the app store.
4: Restart again.
None of this has helped, and I'm really stuck without it at the moment. If anyone knows how to resolve the problem, I would be grateful to hear any suggestions. Thanks.
Give this a shot.
Open up a new shell, and shoot of this command: sudo <Xcode>/Library/uninstall-devtools --mode=all (assuming thats the location of the instal).
Then run the Xcode installer you got from the app store.
This removes all the plist files that were also installed with xcode, which aren't removed when you simply reinstall. This is as close as you can come to a complete xcode refresh without reinstalling your OS.
Here's an alternative solution that worked for me... the answer selected here did not. I created a blank, "hello world" project and simply ran it. When you run the app, it sends the app to the simulator and voila! iOS Simulator has an app to simulate. From that point forward, you should be able to open the iOS Simulator without a problem.
After a while longer trying various things, it seems like I may have fixed it.
When asking for an application to open, I opened Xcode, and (weirdly) that opened up and left the testing shell visible, with the tool bar intact. I then selected the current version from the device options and hit the home button, and suddenly everything appeared.
Weird thing to have suddenly happened, but there you go.
I still can't test in iOS 3, so that's a bit of a problem, but not a disaster either!

Resources