So I read some old threads here about Google deactivating the Google Yolo/One tap option (that was at the end of 2019). I'm not sure what's the status now since the documentation seems to work again.
Anybody has any idea about the current status of the feature?
Thanks
The project seems to be active again and here are some recent release notes.
I have tried it and it seems to work pretty well.
PS: Please check the browser support and know your user base if you plan to use that as your only authentication mechanism though. Always have a fallback auth mechanism if onetap isnt supported or not displayed.
Related
I have a react-admin app where we are making frequent changes.
Is there an existing plugin or a way to detect a new version of app and provide user with a toast to refresh the application so that they are working with latest version?
If not with react-admin, is anyone familiar with a way to do this easily with react?
I have found some manual way to do this in following places but I am asking here in case there is an existing package or a more elegant solution that I can leverage directly.
How to force update Single Page Application (SPA) pages?
https://medium.com/#kellyrmilligan/create-react-app-let-your-users-know-when-the-app-has-been-updated-with-a-notification-21335d85481c
Any help is appreciated even if its, nothing exist and I should just hand-roll.
Thanks for reading.
This is not the responsibility of React Admin to handle this kind of issue.
You can think of RA as a simple React component that helps you define an admin.
Hence, RA doesn't provide any helper to manage code update or something similar.
You have to implement this refresh system by hand, and your links are a good start for that.
With the serviceWorker you can do that :
https://github.com/marmelab/react-admin/blob/master/examples/tutorial/src/registerServiceWorker.js
But i don't know why in the demo the service worker is not used ?
https://github.com/marmelab/react-admin/tree/master/examples/demo/src
Not the most pressing problem facing humanity at the moment, but a frequent if minor annoyance:
When using Google BigQuery, you can only seem to use the default Google Account that your browser is logged into. Currently when I need to use BQ from a browser, I have to start an incognito window and log in using my secondary Google Account. This is unlike any other Google service (cloud or not); generally I can switch accounts in the top right.
Is there a way around this?
This is not implemented yet in Web UI!
See respective issue tracker - Multilogin Support
Quotes from link:
We don't yet have a version of the BQ UI in Pantheon that is far enough along to be a solution to this problem. We hope to have a version ready to try out this summer, but it may not be feature-complete even then.
In the meantime I'd recommend using Chrome profiles (or equivalent in your browser of choice) to switch users rather than using multilogin. Or, if you still want to use multilogin and you have only one account that you use BQ with, make it your primary multilogin account (i.e., sign out of everything else and sign in to that account first).
Pretty late, but the problem still persists.
Firefox(quantum) users(afaik from v57) can open color coded container tabs. This way you can have multiple (default) google sessions per tabs/tab groups. That solves not only BQ, but also google product problems
colored container tab groups
There used to be a little icon I'd press on my jsfiddle and then it'd give me a url where I could point my phone's browser to and see my fiddle running. But they see to have taken it out (?) or maybe I can't find it.
If so, maybe there's another site that you guys know, codepen, jsbin, that does this?
I miss this feature as well and can't find it.
codepen.io allows this, but requires you to sign up for an account (free) and then does so using text messages to send the link to your mobile phone and restricts it to 10 a month.
Not the greatest solution, but it works for intermittent use.
I had a really frustrating issue recently with Tweetdeck, a tool to manage multiple twitter accounts. Since we get feedback and support questions on Twitter accounts with our projects, it is MUCH easier to see all the information in one place. That said, I had a recent issue and couldn't find ANY help online. I was able to find and test a workaround though, and have decided since it helped me I should post it here.
First, let me explain the exact issue, so you can see if my solution might work for you (YES, I already have the answer and posted it below)
I know my Tweetdeck was working previously (as I had multiple accounts). Since some of the projects were going away, and new ones were starting, I removed the existing ones and started trying to add the new ones.
The twitter page would come up asking to authenticate, then after typing in the information, I would get a generic "You have been logged into Tweetdeck, please return to the application" in the new window, but when closing it, I would not be logged in on Tweetdeck with the other account (only the original one)
I tried NUMEROUS steps to fix this including some of the following (NONE of these steps worked):
Tried different computers (with different Operating Systems). These included Windows 7 and Linux (Ubuntu 10.04) and more than one browser (Google Chrome, Firefox, etc). I also tried clearing cache, cookies, history, etc.
NOTE: I also tried to contact both Tweetdeck and Twitter support, neither of which have ever responded to any question I have ever had in years.
So the initial question was... "How do I get Tweetdeck to authenticate with other accounts successfully" with the error "You have been logged into Tweetdeck, please return to the application", but the new accounts do not actually authenticate and I cannot use them in Tweetdeck.
After extensive attempts to find a way to make my Tweetdeck work once again, I found a workaround that has worked great for me. I am not sure exactly why this works, but I have a feeling it has to do with the difference between the authentication method of just Tweetdeck online vs. the Google Chrome App.
On a whim, I decided to install the actual Google Chrome App plugin (as I was running out of options). Then, when using the app, it succeeded with no problems.
While I have posted an answer that works for me here, I would appreciate any comments that might give more real information (not guesses) on why this happened. If there is something else I can try so that I am not limited to the Google Chrome App if I want to add new accounts, I would also be happy to try those possible solutions. Please make sure to read my question which covers what I have already done.
NOTE: Since I have a working workaround, if your solution will take substantial effort, I will probably not try it .
The context is a desktop app using the client-side OAuth flow for authentication.
When I first built this app nearly a year ago, Facebook's documentation said to use the following URL to generate the login/authorization dialog:
https://graph.facebook.com/oauth/authorize?client_id=XXXXXXXX&redirect_uri=YYYYYYY
This is working right now. However, I've reviewed the newly updated Authentication Guide and now see that Facebook is saying to use:
https://www.facebook.com/dialog/oauth?client_id=XXXXXXXX&redirect_uri=YYYYYYY
Does anyone know what the difference is between them, and more importantly do I need to change it? Like I said, it is working now, but I'm a little concerned about something changing when the 10/01/2011 deadline comes around.
My second question is: Does anyone know what enabling the "OAuth Migration" setting in the Apps -> AppName -> Advanced page does?
The URLs redirect to each other. But still, please make the change to the new URL. Whenever the docs change urls and the semantics are the same, you should update so as to avoid unnecessary breaking changes. Even more so with desktop apps.
Second answer: That will issue you different access tokens for now.