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.
Related
when I archive my app and send the build to app store for review, the approver said me the app starts with blank screen. I tried to replicate the issue on simulator in different ways without success:
On xcode: product>scheme>Edit Schema I select Build Configuration "Release"
I changed the build settings in Xcode in the Debug configuration and temporarily turn up the optimisation level from (-O0) to (-O3 or -Os)
The app works fine on simulator without error, If I archive the application and I distribute it with ad-hoc option and I install manually on my device the app works fine too.
The only way to reproduce the problem is distribute the buid to app store and install it via test flight but i can't debug it.
Someone does anyone know what may be causing the problem? I think it could be a configuration problem.
A couple things to try:
Delete the app from your device before installing it from the Xcode debugger.
Install the app using USB with the device in Airplane mode and WiFi turned off.
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?
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.
I have an iOS app which, when submitted to Apple is crashing during usage when you try to go to a new view. This also occurs if i package up the application for enterprise distribution and then go to use the app.
If i just plug the phone in and run from xcode to the device though, it runs perfectly.
Has anyone experienced this before and have any ideas what it could be? Running latest xcode and ios, not using betas.
EDIT - i've tested building straight to the device using both debug and release scehemes, and they both working, but again, only when the device is plugged into the computer and it's built straight to it. packaging it in anyway and installing remotely causes it to crash on a particular screen. The error logs end up as a basically unreadable mess at this point.
When we archive app it mostly builds with release mode on, and when we run build on devices simply by XCode it's with debug mode on. You can check these configuration by going
Edit Scheme -> Run -> Build configuration, same you can check for Archive.
Now for tracking the crash issue you can simply try changing Run's debug mode to release mode for time being.
I got the crash where I was doing configuration for firebase for production target which has different bundle identifier than dev build identifier. You case may be different.
Wow, to be honest, that is really odd... It really shouldn't have that affect if you distribute via enterprise... As of any idea on how to fix this issue: you did add entitlements to the app when signing via enterprise, right?
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.