I have noticed that my Apple Watch app seems to randomly quit from time to time. It's not crashing and I have not been able to reproduce it in a controlled setting, but have noticed that it seems to only happen when I'm in very high or low temperatures. For instance, I was skiing recently and my app was supposed to stay running the whole time, but often when I would raise my wrist it would be back on the home screen and my app wasn't running. This also happened when I was on the beach on a very hot day. But when I'm testing it at home I can keep it running for hours and it never crashes, which leads me to believe it may have to do with the temperature. Does the OS kill apps when it's running in very high or low temperatures? If so, is there anything I can do to prevent this from occurring? Would doing less things in my app possibly prevent this? For instance, I have a timer, and use a bunch of sensors, would turning those off at times and using less of the display make a difference or does the OS not care what the apps are actually doing? If not, any other ideas? Thanks

When I initiate WKExtendedRuntimeSession with a background mode of "Underwater Depth" I get an orange indicator showing the Action button on the screen that stays showing all the time and then animates when you press the action button. I believe this started with a recent WatchOS update, because it never happened before. Does anyone know how to hide it? Or keep it and be able to detect the Action button presses within my app (if possible)?

I'm using Text(date, style: .timer) to display a timer in a WatchOS widget, which works great. The problem is that when the watchface goes dim the time goes from showing the time as "MM:SS" to showing "M minutes". Why is this occuring and how can I change the behavior? I understand it needs to remove seconds to preseve battery life, but why it is putting the word "minutes" at the end, this is messing up my layout. Thanks.

I have an NSSecureTextField field in my MacOS app. I want to disable the password autofill option from coming up (the "Passwords..." button). How can I do this?

I'm using VNImageRequestHandler to recognize text using the camera. In my handler I'm using the topLeft, topRight, bottomLeft, bottomRight properties, which I'm scaling to the size of the canvas, to draw an outline around each text object. When I do this the Y position and Height are correct, but the Width is slightly smaller, and the X position centers the outline around the text. Any idea why this would be a different size?

In all the years of developing for the Apple Watch, the process of trying to run my app on a physical watch or simulator through Xcode is still an absolute nightmare. I probably waste hours each day trying to get my app running. Either the watch doesn't show as paired in Xcode, or it's stuck setting the watch up for development, or it says it's running but Xcode just hangs, or it just doesn't show up in Xcode at all. I have to do so many combinations of restarting my watch, my iPhone, my Mac to try and get it working again. Sometimes it works, sometimes it doesn't and I just give up for the day. Once I get it running I may have 5 times the app will start properly before going back to not running. When trying to use the simulator the watch keeps coming unpaired with the iPhone and won't run. And it's not possible to use Xcode with an iPhone that has multiple Apple Watches paired to it, which is annoying because I can't have one dedicated watch for testing. I just don't understand after all these years Apple Watch development just keeps getting worse and worse. I'm almost ready to just drop my Watch app completely, it's just not worth the headache we go through trying to develop it.

My app suddenly won't run on the simulator. It still runs on my iPhone, but if I try to run it in the simulator it just freezes. The UI comes up but it's completely unresponsive and I can't tap anything. If I pause the project and look at the call stack I see a message saying "Application violated contract by causing UIApplicationMain() to return. This incident will be reported.". And in the console the last message I get is "void * _Nullable NSMapGet(NSMapTable * _Nonnull, const void * _Nullable): map table argument is NULL". Not sure if those are related but that's all I could find.

Does anyone have any idea why this is happening? It does this anywhere in my app where the keyboard is shown. I don't see any way I can be influencing how the keyboard is displayed so I am confused why this is happening and how to resolve it.

I'm scheduling local notifications on my WatchOS app, but they are always alerting exactly 13 seconds later than scheduled. I have read other users having the exact same issue but there is no solution anywhere. I'm not sure how one is supposed to write any sort of timer app when they are always coming in delayed. Any idea why this occurs and how to resolve it? For now I am subtracting 13 seconds from the end time, but that's not really a solution I'm happy with. Thanks

I've been having this issue with X-Code for years and have never found a fix. I've seen many people post this issue but no solutions that work. When typing in X-Code, ever few letters I type the editor just hangs, sometimes the rainbow beachball spinner even comes up. Just pressing return takes a second to complete. Any ideas? There's got to be a fix for this

Can you initiate a live activity from a Watch app? From what I can tell you can only do it from an iOS app and then have the Watch mirror it, is that true? If you were builiding a standalone timer app for WatchOS for instance and wanted the timer to show up automatically in Smart Stacks when the app is in the background, is this possible? Thanks

We are having an issue with our app after upgrading to WatchOS 26. After some time our complication disappears from the watch face. If you go to add it back, our app shows up with an empty icon placeholder and you are unable to tap it to add it back. Sometimes restarting the watch will bring it back, sometimes it does not. Has anyone experienced this? What should we be looking at to figure out why this is happening? Or could this be a bug in WatchOS 26?

I'm trying to update our app, but every time I try to upload screenshots for our Watch App it just freezes and never finishes uploading the picture. The progress indicator on the image just gets stuck in place at about 10% and there are tons of Javascript errors. I wrote Apple and gave them all the logs and errors but they haven't fixed it and won't even tell me if/when it will be fixed. I've been having this problem for over 2 months now and am unable to submit app updates, which is a big problem. Anyone else having this problem? Anything I can try?

After updating to Watch OS 9 our app suddenly cannot connect to the internet with my app using a NSURLSession. It gets an error NSURLErrorNotConnectedToInternet every time. But this still works fine on Watch OS 8. I'm definitely connected to the Internet over WIFI on my Watch and iPhone. It still works fine in the simulator but not on my Watch. Are there any new requirements in Watch OS 9 to get internet access, such as request permission from the user or adding anything to info.plist? Thanks

I'm trying to connect to a web socket server using WatchKit. I already have a Javascript app and a Windows application that can connect to this WebSocket server, but with iOS and WatchOS it fails with the errors below. Any idea how I can figure out what's wrong? I already added the App Transport Security Settings to my plist file. Connection 1: default TLS Trust evaluation failed(-9807) Connection 1: TLS Trust encountered error 3:-9807 Connection 1: encountered error(3:-9807) Connection 1: unable to determine interface type without an established connection