True, Apple removed the special processing of certain third-party social networking sites (FB, Flickr, Twitter), but Google was never among this list. So your mistake should not be related to this.
The library you use relies on a well-accepted mechanism for providing OAuth input out of context. Basically, the application is an SFSafariViewController with an OAuth page, and then after authorization is complete, a special URL is opened, which is sent back to the application, which then rejects the SFSafariViewController. Google and FB I know for sure in my SDKs.
In iOS 11, Apple provides a new mechanism for executing this workflow. It is called SFAuthenticationSession . They do not discount the method currently supported, and you will probably see that the libraries you use are migrated to this new mechanism for iOS 11 devices.
The answer to your question is that these libraries are still relevant , and you should continue to investigate your error (make sure you are not getting the error on iOS 10, obviously)
Update
In response to a further survey, I released a sample project from the link provided. I ran into the same problem on the simulator, but when I ran it on my old iPhone 6 with iOS 11 beta 3, it worked fine. Thus, when moving, it looks like a simulator error. One theory might be a simulator that relies on a host operating system for specific libraries, so itโs possible that if you use High Sierra, you might not have this problem.
I tried to mess with all types of switches in the settings so that the page loads correctly to no avail. It seems that the course of action:
Update # 2
Simulator issue seems fixed in Xcode 9 beta 4. ๐
source share