Xamarin.iOS App crashes after showing launch screen when distributed through TestFlight - ios

I'm currently working on an Application using Xamarin.iOS framework. The App runs as expected when I run it on Simulator & in iPhone using debug configuration. But, when the App is uploaded to TestFlight using a Distribution Profile, it crashes immediately after showing the Splash Screen for a second. My TestFlight users have repeatedly reported that it crashes only on TestFlight builds. Not sure why this happens?
When the build is distributed using Ad-Hoc profile, it works fine as it should.
I have tried updating MacOS, Xamarin Studio, XCode, but in vain.
Any ideas would be appreciated.

Related

iOS app closes/crashing after splash screen only in Debug configuration mode

My app works absolutely perfectly on the simulator and when it is distributed as a Release configuration via my CI - all good. However, if I distributed it in Debug configuration (everything else remains the same) it always automatically closes or crashes straight after splash screen.
I was trying to export it as a development and development provisioning profile and adhoc and adHoc provisioning profile same result.
I have been battling with this issue for a few days now, please advise where to start and how to identify where the problem is.
I am running XCode 11.5 and the app has been developed using react-native. I am using crashalytics to capture the crash reports but for some reason, there is nothing in there.

over-the-air ipa download crashes on splash

I created an app with Nativescript + Angular, the app is running fine on the simulator and when the app is running using 'tns run ios' on my connected iPhone. However when archiving the project to an .ipa and use a link to download the app from my server it crashes or gets stuck on the splash screen. The console doesn't really show any errors.
I've archived the app using Nativescript Sidekick, NS CLI and Xcode but all methods result in the same error. I'm using a developing provision profile that shows no errors in Xcode when assigned manually.
Does anyone have experience with this problem and knows how to fix it?

Xamarin.iOS App - TestFlight Build Crashing without Logging Anything

I have been using TestFlight for several months now to distribute new builds to our beta testers and for the most part I haven't had any problems. As of yesterday (4/11/2017) however, the app is crashing immediately after launch on all of our test devices - without generating any crash reports, so I have no idea how to identify the problem.
I thought that the issue may have been related to using HockeyApp for crash logging (although I have been using that for weeks without any problems), but after removing the related code the crashes are still occurring.
The app runs fine in the simulator, and runs fine on all of our test devices if installed directly through Xamarin Studio (both debug and release versions are working). These crashes are only occurring installing the app through TestFlight. Can anyone offer any suggestions as to how I can track this problem down?

Launch Failed, LibGDX IOS Device

I have trying to make an ios app out of libgdx. I have an Ipad (no iphone yet) an I am trying to upload my app to the device. I have an XCode 7.2, which means that it guarantees that I can upload an app to an apple device without an Apple Developer Account, which currently I have none. I had successfully uploaded an app onto my Ipad with XCode alone. In Eclipse, a simple test app runs perfectly on an IOS Simulator. But when I tried to run it in an IOS device, it does not work. Since it is just a free provision, I was hoping this would work. The Bundle identifier of the xcode app with free provisioning is the same as the app id and main class of my eclipse ios app. Before this, there was an error that no provision was set, so I set the bundle identifier of the xcode app the same with the eclipse app, according to roboVM(http://docs.robovm.com/getting-started/provisioning.html#free-provisioning). But then this error shows up,
"Launch IOS Device App" has encountered a problem.
Launch failed. Check the RoboVM console for more information.
The given data is not a property list of a supported format.
I need to test my app on a real device because I am going to try to implement an online multiplayer with it. As of now I am still using LibGDX 1.5.5. Is it because roboVM needs an apple developer account?
Edit: Even without any device connected, the error persists
I had the same problem as the original poster and it persists in IntelliJ. After some tinkering, it was also showing up on the command line. THanks to some help on the libgdx irc forum, we coudl solve the problem. It was due to running iOS 9.2 on my iOS device and a too old robovm-plugin 1.12.0 seems not to work with libgdx and iOS 9.2. An upgrade to 1.12.1.-SNAPSHOT solved it.
Attention, you have to update two lines in build.gradle:
in buildscript - dependencies: classpath 'org.robovm:robovm-gradle-plugin:1.12.1-SNAPSHOT'
in allprojects - ext: roboVMVersion = '1.12.1-SNAPSHOT'
If you want to compile in IntelliJ, you need to manually install the nightly robovm-plugin from the nightlies download section from the robovm webpage.

WatchKit app hangs & crashes via Crashlytics

Setup:
Xcode 6.3.2
iOS/WatchKit SDK 8.3
What Works:
App groups are configured and tested to be working.
Local development builds with development provisioning profiles work.
I can build & debug to my Apple Watch hardware.
Simulator also works (not that this matters).
Now, enter ad hoc distributions via Crashlytic using our CI (Jenkins) environment. The application is distributed fine, and installs on device fine.
But....
Issue:
Launching the application once installed on the Watch (via Crashlytics) results in a spinner that hangs forvever.
Eventually (after about a minute) the app crashes.
I've stripped the application down to a single controller with a button (no networking or heavy async stuff going on).
To re-iterate - my local development builds to device work perfectly fine.
Any ideas!? Is there a way to get the logs for what is going on with the watch?
Fixed!
For anyone interested, we accidently had left a ARCHS='armv7' argument in our xcodebuild script.

Resources