I submitted a watchOS app (a Chromatic Tuner), mostly written in Swift, to the App Store, and it was rejected (twice) for loading/starting up too slowly. So I rewrote all of the Swift code in Objective C; the new the app loads onto the Watch much faster, and the Objective C version of the app was just approved.
So might the issue have been the Swift runtime causing a watchOS app to load onto the Watch too slowly (all the dylibs for SpriteKit, etc. it has to load before first launch), or was it just phase-of-the-moon during app approval?
