User Profile

Posts

Posts

Post not yet marked as solved
2 Replies
451 Views

Watch app not listing in complication list of watch app in iPhone

We have an IOS app and its watch extension. The watch extension having complications as well created with clockKit Also we are providing a watch face with our custom complications for the user. Everything working fine watch series 6 and above Now we have an issue reported by a customer in watch series 3 (the watch Os version in 8.8), in which the watch face is not able to add as it showing the error "Watch Face Unavailable" So when we tried to create a another watch face for watch series 3, the complication list on the watch extension as well as the watch app of iPhone are not listing our app name Because of this issue we can't create a custom watch face for the watch series 3 with our complications So why the watch app in iPhone is not listing our watch app name in the list of complications Please update if anyone having similar issues
Posted
by bobinabr88.
Last updated
.
Post not yet marked as solved
0 Replies
379 Views

Complication created with WidgetKit not showing on watch face

I have a watch extension app that is used to show the complications using ClockKit. Then when we upgraded to watch OS 9, I added the WidgetKit Extension and all migration code for clockKit as well. Everything was working fine in Watch OS 9 But now when we upgraded to watch OS 10. The widgetKit based complication not at all running, I can't even see any of our complication in watch face On top of that the WidgetKit extension is not showing any debug information as well, none of the break points are executed Please let me know if anyone knows the issue
Posted
by bobinabr88.
Last updated
.
Post not yet marked as solved
0 Replies
642 Views

Complication support in watch OS 9 with ClockKit

Hi Team, I am using the ClockKit to populate my watch app compilations. I have not added the WidgetKit target yet. As Apple start showing warnings for the storyboard in the watch extension, I replaced the storyboard with SwiftUI classes So now my app UI is created from SwiftUI and Complications are from ClockKit But when the watch is upgraded to 9, there are a few issues coming up related to complications most of them are actually related to the timeline and complications are becoming unresponsive So whether Apple still support ClockKit ? or is it mandatory to move to WidgetKIt?
Posted
by bobinabr88.
Last updated
.
Post not yet marked as solved
1 Replies
825 Views

App Navigation stuck while Air Play is enabled

My app needs to display through the iMac and Apple TV for the demonstration purpose But during the AirPlay the app navigation is stuck because of the root view controller is getting as nil I am using the below code to get the root view controller let scenes = UIApplication.shared.connectedScenes let windowScene = scenes.first as? UIWindowScene let window = windowScene?.windows.first return window?.rootViewController Since rootViewController is nil, I can't push a new VC or pop to a specific VC in the navigation stack Only when the Air Play is turned off, I can continue the navigation in the app So this really becoming a blocker issue. Please provide your comments I am running on iOS 16.1.1 in the iPhone and My Xcode version is 14.3
Posted
by bobinabr88.
Last updated
.
Post not yet marked as solved
1 Replies
1.2k Views

Xcode 14.1 and iOS 16.1 causing debugging issues when running from Xcode

When I updated to the new Xcode 14.1 and device to iOS version to 16.1, it is taking a long delay of 1 to 3 minutes to launch the app in the real device I can see the below warning in console "warning: libobjc.A.dylib is being read from process memory. This indicates that LLDB could not find the on-disk shared cache for this device. This will likely reduce debugging performance." I tried with the fix of executing the following command to clear the Device support files rm -r ~/Library/Developer/Xcode/iOS\ DeviceSupport. But even after I am facing the same issue. If we are taking the build using the option "Connect via network" the issue is even more severe, it takes 5 to 7 minutes to actually launch the app in the device Please do the needful to fix this issue. If
Posted
by bobinabr88.
Last updated
.