Post not yet marked as solved
I cannot figure how to post without replying, so this is really a new question.I notice you can only seemingly ask for both Webpage contents and also Browsing History but I only need to read URLs from a specific domain and never need contents of the DOM which leaves everything readable, like passwords!Is there a permission that only requires access to the URLs and not the page data itself?
Post not yet marked as solved
This is now fixed for me with today's update of Xcode 11 beta 6
Post not yet marked as solved
I also see this in Beta 7 and 6 both, all devices, watch, TV -- ipad and iPhoneBut Simulator conteinues to be fine, of course, Beta 5 is the last XCode I see.I filed a Radar report with Apple but I have not heard and I don't see any Apple folks chime in here.Seems like the thread would be swamped if this were happening to everyoen and it's hard to see that going for two beta releases in a row with no mention of it.So, it seems to me that only a subset of us must be experiencing it or somethingCan anyone confirm anyone successfully using Beta 6 or Beta 7 on a device?I have reached out, but get no confirmations thus far.
If this happens to everyone, would't there be tons of posts on here? Can anyone confirm that most folks do not have this issue?Anything else known at this time?
Post not yet marked as solved
that does not seem to work for me, plus, I think we're using the code syntax correctly, this seems to be a bug - I am surprised nobody confirms they can use it ok, or there are not more people here posting about it.that seems odd for something that I would expect nearly everyone would be running into.
Post not yet marked as solved
I have not seen a workaround or fix, I have not heard from Apple, has anyone got any formal information on this? Again, I'd think nearly everyone working on the Beta would be playing with Combine and SwiftUI and as far as I can see, we'd all have this same issue.Anyone know where to go next on this issue?How to get a word from Apple on it?
@ObservableObject does not work on any device running Beta 6 that I have been able to test.We're using xCode beta 5 which is odd, but @ObservableObject code runs as expected while using xcode and simulator.ObservableObject does not seem to work on Watch simulator at all.Can anyone confirm this? Apple?seems like this would be in the release notes or noted somewhere?
Post not yet marked as solved
I get the same issue.Any time I install from XCode Beta 5 onto a device running Beta 6, I get a EXC_BAD_ACCESS when using @ObservedObjectThis seems like it would hit nearly everyone on the Beta, so this doesn't make senseIt could be that the XCode being on Beta 5 is a sign the releases did not sync up properly for Beta 6 but I do not see any response from Apple that this happens or that there is a fix or workaround.Apps run as expected in XCode Simulator.Can anyone else confirm this happens?Can Apple chime in about this?
SpaceMan, can you help us understand what you did exactly and what you think is going on with the @ObservedObject protocol?I kind of assume since this is Xcode beta 5 installing onto Beta 6 and failing while working as expected on the beta 5 Simulator that this is a bug in the Beta 6 iOS release and we may get an update or the Xcode will be updated very shortly to resolve this.Do you think this is a permanent change?
I am also having troubles with anything relating to @ObservableObject and I see some effort to use @EnvironmentObject instead -- but this requires some amount of making changes and I notice there is no xcode update to go with the Beta?Has anyone from Apple verified this? Seems like a major bug late in the beta?
Post not yet marked as solved
I have not found this either, but I did notice that.background(Color.primary.colorInvert())produces the effect we are after, I suspect that there will be a few color choices like primaryBackground or whatever to be revealed in a future beta but I'd be interested to see what the correct solution is.
