I was surprised at how difficult it was to find this information, given that Chrome is certainly one of the most widely-used browsers in the world, and also that it is commonplace to have Macs connecting to Windows domains.
I found that the domains that would be sent IWA information are set in the AuthServerWhitelist policy. But how to change these policies?
After coming across this article, it appeared that changing the policy via the Terminal window would be the best – and possibly only – way to do this.
Enter the following line into Terminal, using comma-separated domains that you trust with your credentials (with or without wildcards), and press Enter.
This is not so much a software development topic as it is an iOS / iCloud issue that does not seem to be well-documented, but was solved only after discussing with Apple Support.
The scenario here is where an iOS device (an iPhone 8 Plus, in this case) gets restored from backup. During the time between the backup was made and was later restored onto the iPhone, a number of photos had been taken and uploaded to iCloud. After the phone was restored, the pictures were missing from the iPhone, yet could still be seen in the Photos app on a MacBook.
Having had some similar experience with this sort of thing before, I thought that turning off iCloud Photo Sharing in Settings and turning it back on might force a sync.
Before I turned it off, only ten or so pictures were missing. Now several thousand pictures disappeared from the iPhone. Needless to say, I was not pleased at this point. I checked Photos on the Mac, and they were still there, so I breathed a sigh of relief.
I then turned off Upload to My Photo Stream in Settings.
This didn’t seem to change anything, so I turned it back on. I then turned iCloud Photo Sharing back on, which automatically then turned Upload to My Photo Stream back off. I turned it back on so that both settings were on, as they were after the iPhone was restored. I then rebooted the iPhone. Still no change.
At this point, I thought time might solve the problem. Perhaps the photos needed to be re-downloaded from iCloud. I let the iPhone sit overnight to see if there was some change in the morning. By the next morning, there was still no change.
Time to contact Apple Support. After talking to a support tech for just a few minutes, a suggestion was made: on the Mac, navigate to iCloud.com, log in, and open Photos on the website. After doing so, all of the pictures – including the ones that were originally missing – appeared on the iPhone!
Whether or not this always works remains to be tested, but it solved my problem in this instance. For such an easy and quick fix, it’s worth trying.
I recently updated my MacBook Pro to macOS High Sierra. Like every other OS update, this one was fairly uneventful – with the exception of having to do a hard reboot to get the Mac to come back up after the upgrade. That was definitely a nail-biter!
Once the Mac rebooted, everything appeared to be as it should be. All was fine and dandy – or so I thought.
Though I have not had any other major issues, it would appear that High Sierra has broken the current version of MySQL Workbench (6.3.9). When trying to run a query, the Results Grid never appears. A status declaring that the query completed is shown, and the Action Output window will even tell how many rows were returned. However, the rows themselves cannot be seen.
It took quite a bit of searching to find this – apparently not too many folks have encountered this problem as yet – but I did find confirmation on Stack Overflow that this is now a known issue, and that the next release should have it fixed.
It is interesting that Oracle has closed the official bug report, despite the fact that no patch or new version is available. A user has devised a workaround that involves installing his build of MySQL Workbench, but that is not ideal in many production environments, for obvious security concerns. The only other solution given was to downgrade to an older version of MySQL Workbench – 6.1.7.
An excerpt of the comments show several users’ reactions to the bug report having been closed with no solution offered:
[20 Oct 10:32] Bob Davenport
Changing back to open
[20 Oct 10:36] Bob Davenport
I’ve changed back to open as its not fixed till the release is available.
I never clsed it perhaps the pperson who closed it could come forward and explain how a bug rendering a product 99% unusable can be marked as closed?
[20 Oct 12:12] Mike Lischke
This bug entry was closed as part of our internal processes. Please don’t touch the status of a bug anymore, once it closed.
[20 Oct 15:25] Bob Davenport
Why is a bug closed when their is no fix ?
Or can you advides the date the fix was released?
Very disappointing that the attitude of yours is so poor.
Maybe next time i wont bother to post a bug report or how to fix.
Also mustn’t forget Mike Lischke who also wasted time with the “Works on My PC” attitude in the firs place.
A discredit to the community.
[20 Oct 15:34] Michael Brogley
I agree with Bob. Based on my experience running just such an effort, a critical status bug should only be changed to “Status: Closed” if a fix has been tested and released. Otherwise any Oracle manager that’s tracking open bugs will be misled on the product’s status. Playing bug status games like this basically cuts the nerves between the user community and management, leading to misallocation of resource problems downstream, and managers and executives getting blindsided by angry users.
Is there no “Pending” status in this system?
[20 Oct 15:37] Darren Coleman
Why would a bug be closed if the problem is not fixed?
I’ve never heard of a bug tracking system where people close bugs without actually resolving the problem??
Is it just inconvenient for Oracle to see this (very simple) bug on their TODO list? It’s ridiculous enough as it is that a community member has to go out of their way to patch a bug that existed and was reported more than once while macOS High Sierra was in BETA.. but to close the bug without resolution is just egregious.
[20 Oct 15:57] Mike Lischke
The typical workflow for a bug report in this bug database is like this:
The bug gets reported.
A support person checks the validity and clarifies things when necessary.
The bug is transfered to our internal bug system where the developers are notified.
The developers fix the bug.
QA tests the fix.
The documentation team takes a note for the change log and sets the bug to closed (both internally and externally).
Once all bugs for a release are closed the new version is released.
Hopefully this makes the process more clear.
[21 Oct 15:12] Bob Davenport
Mike Lischke/ Oracle Can you please advise:
How many bugs are currently open and closed and a release date please?
The bug renders the application unable to display any query results on high sierra. This isn’t an insignificant or cosmetic issue, it’s a show stopper.
If some other bugs are still unfixed could you advise a cut-off date when a release will be provided?
Is this also affecting Oracle Enterprise customers?
I think it is.
For what it’s worth…
I was performing some beta testing for apple and found the fault so decided to report to Oracle.
I provided Oracle with a suggested fix which is relatively easy to implement and is verified as working.
The fix would be effortless & without risk to deploy as a ‘patch’ if in an Agile development environment was utilised.
I would have thought Oracle would be up to date on this technology by now.
[22 Oct 22:19] Aaron Langley
It’s becoming apparent that Oracle’s senior management intends to starve MySQL of oxygen in the hope it’s user base with move on to other alternatives.
Obviously not an ideal situation. Hopefully, Oracle will release a patch soon!