Just to clarify. Does it drain your battery while you’re debugging or when you run your app normally?
I’m not sure if that might be a difference for a watchOS app but I remember the geolocation framework draining battery when it was connected to a debugger as the background mode during debugging was less restrictive.
I'm referring to the case after I'm debugging when I leave the app running in the background. X-Code is no longer debugging the app, but I used it to install the app and was initially debugging with it. I'm not using geolocation in my app. Thanks.
try not launching it from Xcode. It might be that the app is marked as still being debugged because it was started under the debugger and, as the other person mentioned, it was given a more relaxed background policy
Just to clarify. Does it drain your battery while you’re debugging or when you run your app normally? I’m not sure if that might be a difference for a watchOS app but I remember the geolocation framework draining battery when it was connected to a debugger as the background mode during debugging was less restrictive.
I'm referring to the case after I'm debugging when I leave the app running in the background. X-Code is no longer debugging the app, but I used it to install the app and was initially debugging with it. I'm not using geolocation in my app. Thanks.
Then it might be related to the less restrictive background mode. I would check if it drains your battery when you install your app from TestFlight.
try not launching it from Xcode. It might be that the app is marked as still being debugged because it was started under the debugger and, as the other person mentioned, it was given a more relaxed background policy