Same issue here. I also see "Installing symbols for watchOS 7.0.1 (18R395)" when launching Xcode, but my watch app development is now at a standstill because of this issue. Seems pretty basic that Apple QA would check if Xcode can install on a watch after all of the major updates and the emergency updates (e.g. Xcode crashing trying to open documentation).
I used one of my annual tickets to ask code support for a resolution. We'll see how long this issue sticks around.
nickredding
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
A workaround is to duplicate the 7.0 symbols and rename them to 7.0.1
Go to Library/Developer/Xcode/WatchOS DeviceSupport and find the 7.0 symbol entry -- mine is "Watch5,2 7.0 (18R382)" and duplicate it and rename it to "Watch5,2 7.0.1 (18R395)" Your entry may be different depending on your watch model.
I'm guessing (based on other messages in this thread) that those clever folks at Apple didn't set the appropriate permissions on the 7.0.1 symbol resource. It doesn't have anything to do with your account status (mine is fine).
It's one thing for Apple to ***** up beta releases, it's quite another for them to ***** up official releases. WatchOS 7.0.1 is an official release that Xcode will not support because of this issue, and I find that totally unacceptable, especially because Apple is dragging its feet resolving this.
My ticket to developer support drew the predictable demand for sysdiagnose information, despite the fact that this thread (which I referenced) actually contains all the information they need to solve the issue. They were too lazy to even lookout this thread.
I'm still waiting for a response from developer support, three days later.
Apple has fixed this from their end (which was always where the problem was). I still don't have a response to my ticket. Pretty sad.
WatchOS 7.0.2 has been released and Xcode can’t download the symbol files!!
To the frameworks engineer who last replied to this thread: can someone put a yellow post it note on their monitor reminding them that making the symbol files available at the same time as a new release is not an optional “if I remember” type of task?
This is really quite unbelievable. Resolving the 7.0.1 issue took two weeks. Is everyone in watchOS development asleep at the wheel?