I am unhappy to report that this issue has come back on my Note 8 after the Oreo upgrade. It reappeared within 24 hours of the upgrade (which was this past Friday). For the record, I upgraded my phone to Oreo, allowed the update to complete entirely, and then factory reset my phone for a clean Oreo install. The problem reappeared.
Today I clicked on the link that billykac posted a while up the thread. In that link, there is a "one on one" support option whereby Google calls you to initiate a support thread. To Google's credit, they did in fact call me within 3 minutes. After 45 minutes of discussion and the usual progression of recommendations such as wiping caches, data, factory reset, etc., I was ultimately told this was a Samsung issue. I was transferred to Samsung directly (again to Google's credit I might add). The Google support had already explained the entire issue to the Samsung rep. The Samsung rep was clueless. Despite my polite explanations that there are 10 threads on the internet and Google support forums on the same issue, same symptoms, and same frustrations, I was told that my support avenue was to go to Best Buy and speak to a person st the "Samsung Experience Shop" at that Best Buy. Samsung will not progress the issue until I go to Best Buy and the local employee analyzes my phone. If the rep at Best Buy cannot fix it, the phone will need to be sent to Samsung for service.
I am thinking not. To do this, it means I must factory wipe my phone and ultimately send it to Samsung with my google account intact. And who knows when I get the phone back. And maybe I am assuming too much but I do not see a local Best Buy employee troubleshooting the issue to the extent I already have for probably 30 hours of my time and 8 factory resets.
All of the above said, maybe it actually is a Samsung issue and not a Google issue after all. We know there are threads where S8 folks have the same issue. I will be going to Verizon instead and I will obtain a Google Pixel 2 to continue this troubleshooting mission. If the Google Pixel 2 is trouble free, I will have confirmed it is not Google, and it is in fact Samsung, that has the issue. If this is the case, I will work out a swap with Verizon or they'll lose my business, and Samsung will be dropped as my hardware device. Perhaps Ill try again with the Note 9. Perhaps not.
I will update the thread with my findings.