Posts

Post marked as solved
4 Replies
976 Views
As of macOS 10.12, all default widget apperances are light. I couldn't find a setting in Xcode 8 to make my existing widget to adopt the light apperance.
Posted
by danteppc.
Last updated
.
Post not yet marked as solved
0 Replies
392 Views
Hey! The WWDC video "Building complication with SwiftUI" contains a code sample called "Coffee Tracker" that's supposed to include the new code the video presents, however, the code is old and does not contain the new APIs specifically using SwiftUI in building complications. Also, I was unable to find any documentations on how to actually link the CLKComplicationDescriptor with SwiftUI views. Thanks
Posted
by danteppc.
Last updated
.
Post not yet marked as solved
1 Replies
334 Views
I've an app that relies heavily on timers, when I leave the app running on debug (for hours), it wouldn't affect energy usage thus no fan noise is heard, but as soon as I publish the app for release and then run the app, you can hear the fans 10 meters away! why the difference? I don't have any specific conditions on different build configurations!I was wondering whether it has something to do with the debugger, e.g. lower the fans on debug
Posted
by danteppc.
Last updated
.
Post not yet marked as solved
13 Replies
6.4k Views
Since the release of watchOS 6 beta, I am recieving an invalid binary message every time I upload my app with the following description:ITMS-90338: Non-public API usage - The app contains or inherits from non-public classes in APPNAME: WKInterfaceDevice . If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. If you think this message was sent in error and that you have only used Apple-published APIs in accordance with the guidelines, send the app's Apple ID, along with detailed information about why you believe the above APIs were incorrectly flagged, to appreview@apple.com. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/I never had any problem with using WKInterfaceDevice methods like .play() and checking wrist position. what's changed?!
Posted
by danteppc.
Last updated
.
Post not yet marked as solved
2 Replies
1.4k Views
HiI have this watch app with the background processing entitlement enabled which means it can keep running my code even if it enters background. However, if the user decides to explicitly close the app by opening the task manager and swiping the app, and then relaunches it, every view controller is set to their initial state! Now I undrestand that begining with watchOS 5 there's recoverActiveWorkoutSession but that doesn't restore the app to previous state. I was wondering if there's some way to recover the entire app with all UI setups back to last running state?
Posted
by danteppc.
Last updated
.