On iOS 14 calling itms-watchs:// calling URL scheme opens watch app and show "Watch Face Unavailable" "This watch face is not available with your current version of watchOS". However, I used to watchos 7.02 version which is the latest one. And no Watch Face was not implemented on the application.
Use 'itms-watchs://bridge:root=GENERAL_LINK' it works fine.
For more references
https://medium.com/#contact.jmeyers/complete-list-of-ios-url-schemes-for-apple-apps-and-services-always-updated-800c64f450f
Related
I'm building Sticker messaging application. When I try to run the app on iPhone SE simulator with iOS 10 it throws a window to select application through which Sticker app extension should run.
However, in this list there is Siri, Today and Watch app only. There is no Message app. This was working when tested on last week.
Due to this Sticker messaging app extension cannot be tested on iMessage app on simulator.
Why this is happening?
This is probably just a bug in the beta. I've found that this happens with the iPhone SE simulator but the iPhone 6S simulator works fine.
To solve this, if you run the app with one of the other options, the option to launch the Messages app should be available the next time you run the application. So run the app in the simulator, select Siri, and open the Messages app manually. Next time you run the application the option for Messages should be available.
Also you aren't running the latest Xcode beta. The latest version is Xcode 8 beta 4.
Guys from Apple who talked in 2 sessions dedicated to iMessage app and Stickers showed few demos all using iOS Simulator, but as we know it doesn't emulate camera features. When trying to install iMessage extension on real device it just opens iMessage app with latest received message without being able to tap on "Message App Store" button. I'm interested in testing my extension on real device because it's using device camera, but couldn't make it work.
Thanks.
It was a bug. After updating device to iOS 10 beta 4 and Xcode to version 8 beta 4, the extension is installed and running on device.
I am using Xcode 7. My apple watch app works fine in the simulator. It also can be successfully built on device. However, the app seems not to be installed neither on iPhone 5 or apple watch (1.0).
The iPhone and watch pair is ineligible. And it states "The OS version installed on apple watch does not support watchkit app product. I tried everything in SwampThingTom's Question, but I still change the status of the phone-watch pair. The app on phone without watch works well. The problem only comes when watch is included to test app on watch. Does it mean something is wrong with apple watch?
I am new in app developing. Can anyone help me? I appreciate any help.
Since you marked your question with watch-os-2, it is possible that this is correct and you develop against watch OS 2.
If this is the case: you can't run a watch OS 2 app on watch OS 1.
I see to ways to tolve this:
You could set your development target to iOS 8.x and Watch OS 2.
Or you could wait a few weeks until you can install the new OS version on your devices. Since developing for watch OS 2 is much more fun I'd suggest the latter.
In WWDC 2015 it is mentioned that watch supports native apps but I fail to see the option in new Xcode 7 for the way to just build an apple watch app without the companion app. Please let me know the way to do so, if it exists.
In fact, watchOS apps are linked to the iOS companion app.
In both versions, each watchOS app has two targets: WatchKit App - which contains storyboard, icons, etc - and WatchKit Extension, which contains the code.
In watchOS 1 (old WatchKit) + iOS 8 combination, WatchKit App is installed on Apple Watch, and both WatchKit Extension and iOS app are installed on user's iPhone.
In other way, in watchOS 2 + iOS 9 combination, both WatchKit App and WatchKit Extension are installed on user's Apple Watch, and iOS App is the only code and view installed on iPhone.
Running iOS app only requires one target, so it can run without Apple Watch (since the first iPhone OS).
But running watchOS apps needs both WatchKit App and WatchKit Extension. In watchOS 1 (the old WatchKit) because one is on iPhone and other on Apple Watch, so running apps need connecting between them with Bluetooth, so you have to carry your iPhone nearby. In watchOS 2, both are on Apple Watch, so running apps does not need connecting to iPhone and having iPhone nearby. You can connect them with WatchConnectivity framework included in watchOS 2 SDK (in Xcode 7).
So in watchOS 2 apps can run standalone, but they are not standalone at all. They install on Apple Watch when installing on iPhone, and they can connect with each other. When you create a new watchOS App, you must include it with your iPhone app when submitting it to the iTunes Connect.
NOTE: This makes watchOS apps faster and more reliable.
You can't build native watch apps yet. Maybe in a later build of Xcode 7, but so far all Apple has announced is that "at some point in the near future" you will be able to build a native Watch app.
In watchOS 2, watch apps are "native" in the sense that the WatchKit extension now runs on the Apple Watch instead of the user's iPhone. This means it can no longer share data with the iPhone app using shared app groups but must instead use the new Watch Connectivity framework to pass data back and forth. It also means that watch apps can be much faster and much more capable without the phone being present.
However, a watch app must still be bundled with a companion iOS app, at least for this year.
In iOS 13 it's possible to create independent watchOS application. More information can be found here. You have to download Xcode 11 to be able to create independent watchOS application.
To create it simply go to File -> New -> Project and select watchOS -> App as it's shown on a screenshot:
I've been building an iPhone game for the last couple months using XCode 3.2.5 and iOS 4.2 and I'm about to submit it to the App Store. Before I do that, however, I wanted to test it against iOS 4.3 Beta 3, so I downloaded the latest beta SDK, installed it in a separate location, and updated the device to iOS 4.3 Beta 3. Now, when I run the game and it attempts to authenticate the local player in Game Center, it pops up a box saying "This game is not recognized by Game Center". Why?
I tried logging out of Game Center though the Game Center app and restarting my app, but I was already logged out, so the problem doesn't appear to be the result of trying to use a non-sandboxed account. Also, I noticed that it runs fine in the 4.3 Beta 3 Simulator. I only get this error on the updated device. Any ideas?
Thanks so much for you wisdom!
Are you code signing with the provisioning profile specific to your app or with a wildcard provisioning profile?
As far as I know, signing with a wildcard profile isn't allowed for accessing Game Center.
In the Game Center app, make sure you're not connected with an account in the production environment. If you have doubt, log out and start your application.