Post not yet marked as solved
I've been banging my head against this for a while and found this thread. I am also having an identical issue to everyone here, but haven't been able to establish a workaround. I installed Xcode Beta 11.3 (11C24b) to determine if the issue is resolved (the latest at the time of writing), but this has not fixed the issue when running my app in a simulator. I guess we just play the waiting game for now? 😬
** Update. While this solution didn't work for me personally, another method did by installing the beta profile directly through the iPhone using Safari. I had been Airdropping the profile previously and that didn't seem to be working. See my full post further down the thread. **Thanks @kcft for sharing your suggestion.Unfortunately, this hasn't worked for me. I started with this during my own troubleshooting, then unpaired my watch, loaded the profile back on, and the same issue. Even so, I attempted your suggestion a few times after all of that and i'm still receiving the same error.I'm glad it worked for you, though. Thanks again for your suggestion.
I got it to work at 5:45pm Eastern Time on 07/17/2019Solution that worked for me:- Remove the WatchOS beta profile- Restart the Watch- Download and Install the beta profile by browsing to developer.apple.com on your iPhone with Safari that your Watch is connected to- Restart the Watch- Install the update 😀What I had been trying prior to that:- I usually log in via my Macbook and then Airdrop or otherwise share the profile with my iOS device. There might be some kind of descrepency between installing the profile via an Airdrop transfer vs direclty on the iPhone through Safari. I haven't had issues doing it this way before, but today it worked immediately after browsing to the website and downloading the profile directly through the iPhone and Safari.I hope this helps someone else install the update! Good luck.
Same issue here.I wish I stumbled across this thread prior to unpairing my watch and doing that whole dance...At least we can all take comfort in knowing that it isn't our fault or our devices -- it's an Apple thing. Hopefully Apple pushes something to resolve this issue. Keep your eyes peeled!
Doh, it looks like I figured it out...I've resolved this by simply adding: tag(1) and tag(2) to each tabItemLabel(See below)import SwiftUI
struct ContentView : View {
var body: some View {
TabbedView {
SettingsView()
.tabItemLabel(Text("Settings")).tag(1)
HistoryView()
.tabItemLabel(Text("History")).tag(2)
}
