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.
Related
I'm creating a flutter plugin and I just tried the example project that gets created by flutter it self. This example project is an app that shows the operation system and its version. If I start it from Xcode on my iPhone SE, it works fine.
But if I close the app and open it without Xcode, that means that I tipp on the app icon to launche it, like every normal app, it doesn't start correctly.
It is showing for not even a second a white screen, followed by a black screen and is closing the app right after this.
Why is it behaving like that?
Is it, because it is a debug version and needs Xcode?
How can I put my example app on my iPhone without needing a connection to Xcode to start it?
Thanks in advance!
Edit: Thanks to the answer of Răzvan Puiu below, i know now that this is because xCode puts the app as a debug version on my iPhone. This debug version can only run with xCode. After I tried it with a 'normal' app and not the example app of a plugin project, i even got this text shown if i tried to start the debug version without xCode:
So the solution is to run the app with:
flutter run --release
I believe it behaves like that because you don't have an Apple developer account. "Without enrolling in the Apple Developer Program, your app will only last for 7 days on your device. After that, you’ll have to re-deploy it to your device via Xcode. If you’re enrolled in the Apple Developer Program, you won’t have this inconvenience."
Yes
You can run flutter run --release and then select your physical device. However the app will remain on your phone for only 7 days unless you have the Apple dev account.
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.
After installing 11.1 I created a new project, removed the multi-window stuff that Xcode now gives you by default, and started developing a test app that uses Vision Framework.
By the time I got to the point where I needed to test on the device instead of the simulator, I was struggling to make my app work correctly. I finally realized that running the app on my phone required me to delete the app and run a fresh install or the changes wouldn't be pushed to the device. This continues to be a problem. Even a new print statement won't be shown in the debugger output unless I go through the rigamarole of deleting the app and running fresh. Subsequent changes still use the initially installed build regardless of the number of times I clean/build/run.
I've cleaned the project, build folder, derived data, Xcode cache, rebooted my Mac, rebooted my phone, reinstalled Xcode, obliterated and reinstalled Xcode again, all with no success.
Anyone else with this issue? What am I missing?!
Ok, after two days of trying to fix this, it turns out to be some kind of Apple bug on iOS 13 (surprise, surprise).
Here's what I did/found:
I tried running on another device and was able to see changes on subsequent runs.
Back on the original test device, the issue still exists (Xcode issue ruled out)
I had a couple other test apps that were signed with the same development cert on the device, so I deleted those too.
Running the app from Xcode again prompted me to go to settings to trust the developer certificate
Changes and updates are now pushed to the device on each run from Xcode.
TLDR:
If you happen to run into a similar issue, try deleting other development certificate apps you have on your device and re-trust the certificate.
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?