I developed an android application last year which uses lifelog api but I check recently that I can no longer initialise lifelog within my app and I want to know if there are other ways to see the app registration details such as the client id and secret etc.
Unfortunately the Lifelog API has been completely shut down at this point and there is no way to access it. We apologize for the inconvenience!
Related
I've developed an application that works through Google's GSuite using OAuth2. The app is working fine and is part of the GSuite account that was set up to allow testing while developing it (which is the owning account of the app in the Developer Console). However, I now want to give the app to another GSuite company but can't see how to get them to add it?
The application has been submitted for review with Google to get it added via the Marketplace but we're keen to get the second company using it ASAP. I've had a look through the Google docs but couldn't find anything that appeared relevant and even tried to see if I could find an existing question on here. If anyone can point me in the right direction that would be much appreciated!
Cheers
You won't be able to give it to another company until it's published, so if the review is taking linger than expected, your best is to contact Google GSuite support
The error I'm getting is BETTING_RESTRICTED_LOCATION. But when I run my app locally using London location from VPN I am able to login in perfectly.
Is there a way I can ensure that the app is running from places where betting is legal?
There is another question like this but its very old and doesn't help me.
The IPs of Google Cloud Platform share the same geolocation (US). And it could be possible that your bot doesn't allow connections from this part of the world. If this is the issue, there isn't any available solution within GCP just yet. You can follow this feature request or in the meantime, just point the requests to an on-prem service hosted in London that acts as a proxy.
I was wondering what would be a better way to let my jQuery Mobile app "know" the user of the app after completing a registration process.Since the handlers in my Python Google App Engine app expect a username, i decided to store the username in localstorage and then use this as part of any request made to the server.But i don't think this is a good design idea (?).After a lot of search, i have found that jQuery Mobile does not support Google login (Please correct me if am wrong) So i have decided to use the Users Service from the server end.I am confused on how to implement this, since the users service from Google has it's own sign-in form.
Is it possible to use this same service with jQuery? If so, can i change the design of the sign-in form to blend in with the design of my jQuery app?
jQuery Mobile is just a template designer created directly for mobile web applications using a mobile web browser. It does not possess any connections with server side scripting automatically.
You need to create a connection using server side scripting.
Once you login in using the Google Login, your app associates it with the Google account.
jQuery is just a browser scripting. It does not have an automatic connection with the server unless you connect using AJAX to request to a server, but still need to code the server using HTTP protocol (as a tunnel) and server side scripting language like Java, Python, or PHP.
If you just want to get the "username" using a javascript, you may use REST to get the user information after login. You may look for how JSON or XML REST is created (but putting the username on local storage is not a bad option, without the password, however it may get deleted if you clear the root), but knowing that you are already connected with Google Sign in, just as long as you are already logged in with Google, your app should be able to retrieve the Google username.
Udacity also contains a complete course about web development focused on Google App Engine using Python, and how you may use cookies, password encryption, as well as user login. A detailed information about HTTP protocol is also discussed.
https://www.udacity.com/course/cs253
Note that the course I took existed 2 years ago. It may be different now.
I recently created a new google account and registered a new domain for google app engine that i want to use now with a java gae project i wrote.
When i try to access
https://appengine.google.com/
or
https://appengine.google.com/a/my-domain.com
i always get redirected to a page
"Welcome to Google App Engine Before getting started, you want to
learn more about developing and deploying applications."..... Create
Application
When i push this button, and enter the phone number i used to create the account/domain this is refused with:
The phone number has been sent too many messages or has already been
used to confirm an account.
I am not able to deploy my GAE application as i simply dont know the Application ID. I can not create a new one and i can not find out if i already created one as there is no way to access the dashboard.
Any Hint?
Please help
You already used that number to validate a different Google account, you need to create the application with that account.
More information at the SMS Verification for App Creation FAQ
Google recommends to fill out the following form in this event to verify the account manually:
https://appengine.google.com/waitlist/sms_issues
I am still trying to wrap my mind around the workings of OAuth/OpenID, as such...
I am developing an "installed app" that will run on computers and iPhone. A given user may install the client app on multiple machines, and all of the user's installed clients will synchronize via a centralized Google App Engine service. The GAE service will also allow multiple users to collaborate on the data produced by the installed app, via a web app.
I don't want to roll my own authentication system, for my own ease and also to spare users from yet another set of credentials. As such I was initially thinking of using Google's clientlogin service, but then I thought OAuth/OpenID would be better because it would allow users to use not just Google credentials but also credentials from the other OpenID providers. Also, avoiding asking the user for a login/password seems more secure.
My question is... I'm not sure if this is the right use case for OAuth/OpenID. I am not accessing data from any other service, I am just looking for an authentication solution. Also, how difficult is this scenario to accomplish using Google App Engine (java)?
Any advice and/or starting points would be much appreciated!
My question is... I'm not sure if this is the right use case for OAuth/OpenID.
The "use case" for oAuth is: App X requires access to App Y. App X "asks" permission for access to App Y through your credentials. App X received an "authorized access token".
In your case, assuming I understood correctly, you could have the App on GAE implement an OpenID consumer and have your mobile app access the GAE app through oAuth.
In other words, your approach seems like a sensible one.