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
Related
I am using Xcode 8 and trying to upload my watchKit app to Testflight but its failing all the time.so far i have tried these options,
tried uploading it from Application Loader 3.6 and get invalid swift support, invalid watchkit support,and invalid executable error.
tried from Xcode 8. The app validates succesfully but upon upload to store, it just gets stuck. when i refresh, i do get an upload sccessful message but nothing is visible on testflight.
how to upload my watch app on testflight? please help
Have you enabled the version of your app to test on the iTunes Connect website?
I hope I'm not stating the obvious here, but if you:
Select your app in the "My Apps" section
Select the "TestFlight" tab at the top
Select "Internal Testing" on the left hand menu
Click on the "Select version to test" link in the page
Uploading an archive with a new version number doesn't automatically add it to TestFlight, so you have to go through this procedure every time you change version number (or on the first upload).
Once it's added, you should see the app appear in the TestFlight app on your phone. When it also has a Apple Watch app, and you have a watch paired with your phone, TestFlight will also install the app to your watch.
Hope that helps!
I have configured the WatchKit App to run in my project (WatchOS2).
When I try to run it into the simulator the WatchKit App start perfectly, but each times I'm trying to start the iOS app, this one crash.
The simulator's log show me that :
com.apple.CoreSimulator.SimDevice.5F243C10-E98D-4A20-8950-2742FE6CABD5.launchd_sim[13288] (UIKitApplication:com.MyCompany.MyProject[0x847][13496]): Service exited due to signal: Trace/BPT trap: 5
All of my code in the application delegate is in comment. just enough to start
If I build and use my main app target with the same simulator setting, that works nicely. it just when I build and run the watchkit extension target.
I tried to clean everything (derived data, simulator setting and contents).
I know, it is not the simulator, because with a new project, the issue is not here. it might be something set somewhere ??
but nothing works, any idea ?.
Your application aborted, likely due to a failed assertion. You should look at the crash log (in ~/Library/Logs/DiagnosticReports) for more details.
I am trying to create enterprise build for apple watch project by xcode 6.3
I tried to build by archive and by auto-build (shenzhen tool)
When I run it at iPhone, it crashes immediately but with ad-hoc build it's work fine.
I've found that Xcode Automatic selections do not work properly for code signing and provisioning profile when used with Apple Watch; sometimes it makes the wrong choice and you only notice when it has problems installing and launching.
For each of the App, App Extension, and Watch App, select the code signing certificate and provisioning profile explicitly (not automatic) in the pop up list.
For issues upon launch on the device (from spring board) the device console gives good information. Install iOS Console, from lemonjar.com to easily see such information.
I want to know if anyone could suggest that how can I create Simulator build for Apple Watch.
I'm following the steps in this [link to create simulator build](https://developers.facebook.com/docs/iOS /creating-iOS -simulator-build-for-review)
but if we use command like xcodebuild -showsdks
It only showing iPhone Simulator.
Though I've created simulator build using these command for project having target for Apple Watch, but it do not run on watch simulator.
So, it will be helpful if anyone could suggest how to create Simulator build for Apple Watch.
Since your WatchKit app and extension are part of your iPhone app you just need to create simulator build for your iPhone app. Then when you install your iPhone app in the iPhone simulator it will also install your WatchKit app on the watch.
If you just want to run your app on the Apple Watch from Xcode then you can just select your WatchKit app in the list of schemes and then build & run. You will need to enable to Apple Watch display as Pablo A. mentions.
Go to the simulator (iOS 8.2 or greater) and
Hardware - External Displays - Apple Watch
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!