I need to make sure that our iPhone App (implemented with Monotouch) will still be be working from the very first day that iOS 6 is released to the public.
I've installed XCode 4.5 and iOS 6 Beta 3 and upgraded Monotouch to the latest version. Then I ran my app in the iOS 6 emulator and the app crashed instantly with the following error message:
Terminating since there is no system event server.
(Run the EventPump or pass the argument "-RegisterForSystemEvents" if you want to run without SpringBoard.
I've tried googling for similar problems but could not find anything. What can I do to make my App run on iOS 6?
Thanks,
Adrian
Details on iOS 6 and Xcode 4.5 are under NDA and won't be discussed publicly. Please either contact support#xamarin.com or fill private bug reports on http://bugzilla.xamarin.com
Related
I have a Mac running Catalina with Xcode 12. This month, my iPhone upgraded to iOS 14.6, which requires Xcode 13. Xcode 13 requires Big Sur. Unfortunately, I don't have the money right now to upgrade my Mac to one with the hardware the Big Sur requires.
I installed VMWare Fusion 12 on this Mac and created a Virtual Machine running MacOS Big Sur 11.4. Then I installed Xcode 13 Beta 2, installed its dependencies, added the provisioning profile required to deploy, and selected my iPhone in Xcode as the target. When I build and attempt to deploy to the device, there are no errors, though it hangs/stalls right near the end of the process, around the time that Xcode says: "Preparing Editor Functionality". MetroBundler starts correctly and I see no issues in Terminal, Console, or Xcode. It just stops compiling/deploying.
I'm not super savvy when it comes to Xcode or the deployment process. I was hoping someone might be able to give me some tips as to how to figure out what's preventing the app from deploying to the device. Does Xcode have logs somewhere (other than Device Logs) that might help inform what's hanging?
Thank you for your time and I'm happy to provide screenshots or further information upon your suggestions.
I reuploaded my app to TestFlight via Xcode 9.4 but it is continuously crash after splash screen on that test flight build in IOS 11 while same test flight working in IOS 10. While when running in the Adhoc build in the device, it is working fine without any issue.
And my last submission by Xcode 9.2 is working fine in all IOS devices including 11.4 too.
When I am getting crash logs from Organizer, it says, App crash on a statement like self.viewInput.refreshRewardCount(current: current, max: max) where current and max value passed static as 0 and 50 respectively first time when app start.
Additionality, I have also checked my Optimization Flags for LLVM and Swift compiler which are set properly as my other app and people suggested on the stack too.
Help me to solve that issue.
Thanks
We ran into this before. If you have not resolved this try using ImageOptim (downloaded from the Mac AppStore) and optimize all of your images. iOS 9 had a bug where it couldn't process certain metadata of PNG files.
I am getting this error in Xcode 9 beta . What does it mean? Attaching snapshot for the same.
The problem seems to be that Xcode 9 Beta does/can not close the iPhone app if it is open on the simulator when the app is built and run (which it used to do). Simply closing the app on the iPhone simulator (shift-command-h) seems to do the trick. Another option is to restart the simulator. Hopefully Apple will fix this issue soon.
We have a Xamarin.Forms app for iOS and Android that we have in the stores for some months now. We develop with VS 2017. For testing the iOS-version, we use TestFlight.
Everything worked pretty well, until mid-april when we wanted to test a new release via TestFlight:
We installed the iOS-App on our test devices via TestFlight, and now on our test devices the app closes down right after the splash screen without generating a crash report (we use HockeyApp).
The app works fine though on the iOS-simulator and when being published directly on a device (iPad) via VS.
We found out that the problem is the update of Xamarin.Forms from version 2.3.3.180 to version 2.3.4.231 or later.
We would like to use latest version of Xamarin.Forms. Does anyone have the same issue and did you find a solution?
We just found the solution for this problem:
We use a custom font for our app and changed the font of the navigation bar in the AppDelegate.FinishedLaunching method by using UINavigationBar.Appearance.SetTitleTextAttributes.
This caused the iOS version of our app to crash when distributing via TestFlight. We removed the code to change the font and now we can publish the app again.
I just pushed my app to the App Store after building release/AppStore build using xamarin's Studio...
Everything was green lighted and ready to go, I only had one person who had not installed the release version.... They installed it and it takes 17 seconds to try to start and is killed (I presume). it does NOT create a crash log on the device.
In the Settings there is a "Debug Settings" section under the app - that I didn't put there, including an option for Xamarin Studio Host which is set to automatic but appears to be able to be set to some other string.. (Another message on what the heck this is, and how come it shows up in the first place, and how to get rid of it)
I'm at a loss how to debug this. I just downloaded and upgraded XCode to the latest, in hopes that will help.. (Although, I'm not using the XCode interface to build, but I expect that under the hood it is using that for parts of this, maybe the libraries or something.) Still, unless the iOS writers are nuts, it should be backward compatible with apps written for iOS 4.0 and later... (Mine is a 4.0 targeted app)
Also, on her phone (which has always been 6.x for all the testing she has done), my app has always taken a LONG time to start up.. but on 5.1 it is very fast.. (I.E. 1-2 seconds vs 10+ seconds on her phone)
Anyone got a clue, I sure could use one right now.. I expect that I'll have to reject the binary, and submit another one...
-Chert
Figured it out.... The issue was with the TestFlightApp SDK...
I removed it and now the app starts up OK... Resubmitted to App Store for approval.