Hey Mike. I haven’t entirely solved this problem. But I found this issue on github very helpful. From what I can gather, Safari’s sparse support of manifest.json is to blame – try using PWA Compat with the changes in the previously linked issue. Using pwacompat.js (with the outlined changes) allowed me to successfully login with Google as the social provider while maintaining the app in standalone mode .
That being said, I’m having some trouble using my Google access_token. Specifically, I’m receiving a CORS error:
“…blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.”
However, if you don’t need access to Google APIs, then using pwacompat.js (with the slight customization outlined in issue #77) should solve your problem.
Hope this helps.
EDIT (correction to above quote): Now able to access user Google APIs using the access/refresh tokens supplied when user logs in using Google as the social IdP. The previous problem was caused by an unrelated, erroneous environment variable. So using pwacompat.js should solve your problem. Let me know if you would like further assistance.