Whenever I launch my iOS/iPhone Target the app is removed from the Watch.
Also of interest: When the watch app is deployed from Xcode, it quits with signal 9, something with XPC
Related
For the past days I had major issues with deploying the android version of my app. I found out that I am only ever able to get the app to work when "Fast Deployment" is checked. However, this means I can never archieve my app. If fast deploy is enabled, the app, even though it is in release mode, is treated like a DEBUG build and therefore not accepted in the playstore.
If i uncheck fast deploy for release builds the app starts and then idles, not doing the first rest call it is supposed to do. If I leave the rest calls out, the app again works.
How can this be correlated?
The symptom that it works when set "Fast Deployment" suggests this situation:
If you are testing a release build on a device that previously had a debug build, its possible that the debug version did not get fully uninstalled. Specifically, "Fast Deployment" stores the xamarin library as a separate DLL. Because your release build has the same "bundle id" as the debug build, Android can get confused.
To fix.
Best Fix for emulator:
Tools / Android Device Manager / Select virtual device / Edit / Clear to Factory Defaults.
Quickest fix for phone (but not sure if it helps):
Drag app to trash can.
Power down the phone. Power it back on.
Deploy release build to device. Either by installing apk, or by "Start Without Debugging" menu item.
Quick Fix:
Run debug version again on the device. This makes sure Android "knows" that the debug version of app is there.
Stop the app.
On the device, "uninstall" the app. (Drag it to trash can).
Deploy release build to device. Either by installing apk, or by "Start Without Debugging" menu item.
If that doesn't work, then use "adb uninstall":
Run debug version again on the device. This makes sure Android "knows" that the debug version of app is there.
Stop the app.
menu Tools / Android / Android Adb Command Prompt.
adb uninstall com.companyname.appname <-- substitute your app's bundle id
deploy release build to device.
It turnes out that turning ON my linker to link assemblies only actually decreased the app size AND made everything work again. Before, the linker was set to LINK NONE (which should've been the safer bet, but turned out to be an error...).
Our test automation sometimes makes the simulator crash. In these cases, we often see the dialog below throw on the simulator's next launch. This modal UI dialog breaks automation by preventing application execution until the user chooses an action.
When the iOS Simulator crashes, the application state may be saved in ~/Library/Saved Application State/com.apple.iphonesimulator.savedState. The presence of this folder or values in the data within triggers the modal dialog.
Removing this folder (rm -rf "~/Library/Saved Application State/com.apple.iphonesimulator.savedState") before restarting iOS Simulator will prevent the dialog from appearing. This has been tested with iOS Simulator shipped in Xcode 9.4.1.
It runs just fine on the iPhone. When I select the Watch App Target, however, it simply won't run on the watch.
I don't get any errors or anything. I can see the app downloading on the Watch sometimes; when it does download, it deletes itself the moment the download is complete.
I've tried uninstalling the watch app and reinstalling via the Apple Watch app on the iPhone, and the same thing happens: it downloads and deletes itself before I can run it.
I've also reset the watch, reset Xcode, deleted the iOS app, and just about everything else I could possibly think off, but I'm starting to lose my mind.
The problem started happening when I (attempted to) set up the Watch Connectivity framework. I don't know if this is related. I've been unable to verify that WC is working properly as I can't open the app.
I've been lucky enough to get it to actually load on the watch only a few times since integrating WC framework, but even when I have, all I got was the loading screen for about a minute each time.
UPDATE:
I'm now seeing some consistent behavior.
I'm now able to debug my app by launching the watch app via Xcode. The app icon does not appear at all on the watch when this happens, however. (Weirdly enough, it shows the launch screen for a different watch app when launching.) So I can't run the app at all unless it is launched from Xcode.
Also, I am not able to download the app to the watch via the phone. I want to be able to run it outside of debug mode, and I can't. When I attempt to install it from the Apple Watch iOS9 app, the install begins, I see the icon on the watch as it downloads, and just as it finishes, it deletes itself from the watch before I can run it. This just keeps happening.
Please help!
Make sure your Apple Watch device ID is in your provisioning profile.
So, this kind of sucks as an answer, but I've had enough.
I decided to copy all of my code and storyboards into a new Xcode project. The Watch App now works exactly as it should. Hopefully Apple sorts out these bugs in an update.
I believe repairing the watch would help as well. I had the same problem before and the only thing which helped was repairing the watch.
I also have other issues debugging the watch app properly - see my question here Proper way to debug watchos2 app in XCode7
I cannot start iOS Watch App on simulator. Installed latest Beta 6.2 on Yosemite
1) I create a single view based application,
2) Add App Watch target
3) Extension and Watch App automatically created
4) Run App and start simulator and enable Apple Watch simulator
5) Switch Scheme to app Watch App and start Run
Xcode status bar showing Running App...... and never jumping to second step of
Running App extension, so nothing is showing on Apple Watch!!
1. Select you "... Watch App" Run it on iPhone 5 simulator and higher
(watch simulator not working with iPhone 4s)
2. Go to Hardware > External Displays > Select one of Watch external displays.
As a result you should see the log on the console from your WKInterfaceController WathcKit Extension
I have exactly same problem. I created a new project and added WatchKit extension in Xcode 6.2 beta 4 with WatchKit. I tried all ways mentioned in other answers but still failed to let watch app run in the simulator. Finally, I made it work.
My steps:
Delete the containing app in the iPhone simulator.
Clean your project in Xcode.
Do not run the containing app, run the WatchKit app from Xcode.
1. Dont run main target, run watch extension target. you can find below attachment, so that you can get an idea
2. Go to Hardware > External Displays > Select one of Watch external displays
An iPad app I'm starting compiles and builds fine, I get a packaged application. But when I try to debug it, it fails with "Unknown error" after trying to install in the simulator. Inspecting the simulator directory, no Application sub-dir for my app is ever created.
It works perfectly for other iPad projects and I'm not really sure where to start - what does this imply is wrong inside my package? Does the simulator inspect the package before installing it?
I should add, this XCode project was a working iOS sample app that previously DID deploy and run on the simulator. I have only changed the source files and linked in some additional libs, not changed the underlying project structure. I don't expect it to run without errors, but I did expect it to at least start up!