After upgrading to GoogleAppEngineLauncher 1.9.18 and clicking on the Deploy button, a new tab appears in the browser with a page reading:
Google App Engine appcfg would like to:
* View and manage your applications deployed on Google App Engine
* View and manage your data across Google Cloud Platform services
By clicking Accept, you allow this app and Google to use your information in accordance with their respective terms of service and privacy policies. You can change this and other Account Permissions at any time.
So I click the Accept button and a new page appears:
The authentication flow has completed.
The deploy completes, but this happens every time I Deploy a new version. What's up with this? Why doesn't it remember that I accepted the TOS and Privacy Policy? This is annoying!
Another question: How can I turn off this new "feature"?
Update: This only seems to apply to Mac launchers
Update on 2015-04-20: Upgrading to 1.9.19 has solved this problem
Did you just upgrade the appenginelauncher to version 1.9.18?
Per the release notes:
Mac Launcher now uses OAuth2 exclusively for app deployments.
Permissions are granted through the browser instead of a login dialog.
It looks like this is the way it is now.
Related
We have review apps enabled for our app in Heroku. The feature was enabled by a developer who no longer works with us. When we revoke his access to the app from which the review apps are build, the review apps are not built any more. If we disable and re-enable the review apps, Heroku assumes we are doing so as the original user so we get an error message that we don't have access to that app...
Is there a way to switch the owner of the automaticlly built review apps?
Here is the response I got from the Heroku support:
You can fix this by visiting your pipeline, clicking "Manage GitHub connection", then clicking "Disconnect". Wait a few seconds, refresh the page, and reconnect from the same menu. This will make you the default user for provisioning and deploying review apps.
Once that's done, you'll need to re-enable review apps for your pipeline. Also, if you had any apps set to auto-deploy from GitHub, you'll need to configure that again as well.
I am trying to integrate facebook into a Windows Store App.
I have created a new FB App and started working through the steps described in this blog post. http://blogs.windows.com/buildingapps/2013/11/14/facebook-login-for-windows-store-apps/
Here is where I ran into a problem. Step 2 describes how to obtain a Windows SID for an App that has yet to be published. However my app is already published. Does anyone know how to obtain a SID for an app that is already published in the Windows Store?
Instructions in this post should help you find how to locate SID for published app: https://msdn.microsoft.com/en-us/library/windows/apps/hh465407.aspx
It's listed under step 3 for obtaining the credentials for your app. Here are the steps:
Go to the Windows Store apps page of the Windows Dev Center and sign in with your Microsoft account.
Once you have signed in, click the Dashboard link.
On the Dashboard, select Submit an app.
On the Submit an app page, select App name.
Select the Services link.
On the Services page, select the Live Services link found under the Microsoft Azure Mobile Services section.
On the Push notifications and Live Connect services info page, select Identifying your app.
The Identifying your app page gives you an identity element to include in your app's manifest. Open your manifest in a text editor and add that element as the page instructs.
9.Click the Authenticating your service link at the bottom of that same Identifying your app page.
The Authenticating your service page provides your security identifier (SID) and client secret.
I see it's an old post, but I guess it's better to show a simpler solution, which is the one told by microsoft in this thread: https://msdn.microsoft.com/en-us/windows/uwp/publish/view-app-identity-details
You can just go to your application from the developer dashboard, then on the left you should expand the "App Management" option and choose "App Identity". There you can find many informations, including the App SID.
We've migrated our app from the old marketplace to the new one. After a few days we've received an email that we don't comply with an SSO policy - the user is not recognized after he installs the application.
In the old app we had a specific setup link, that was opened for the user after he installed the app - thus making him recognizable. Is there such a function in the market? Is there some sort of a callback for the installation event in the new marketplace?
P.S. the guy from Google told me to post technical questions on Stackoverflow and that "Our developer relations team monitors that forum and will be able to assist you."
EDIT:
There's the Additional app setup link in this after-installation popup (which clearly no user will click):
Is there a way to call the URL that of the Additional app setup in the background, without needing the user to click an obscure link?
That was an intentional design change which is different than how it used to work in v1 of the marketplace.
If you need interactive setup, best thing to do is put in a check on login to see if the domain has been configured. You can use the licensing API to check for a marketplace install record or directory API to check user permissions if those matter for your use case.
If you just need to run a background task, you can periodically poll the licensing API to detect new installations of the app. This shouldn't be done too often, so if you need to do things before a user logs you're still better off going with a check on login to route them to the setup flow as needed.
I'm developing a google apps marketplace app. There's the Test install flow button on the dashboard, but I'd like to test installation on another domain of ours - to see that permissions, token etc. work as expected. Is there a way to install an (it's non published yet) on a domain which is not related to development?
Found a solution, this was surprisingly straightforward, but it worked for me:
Open two browser windows, one for your dev account (dev.com) and one for the domain you wish to test on (test.com)
In you dev account, go to the dashboard and click the Test installation flow button
In the popup that you get, go to the address bar and copy the link
Now go to the browser with your test.com domain, and enter this address
You'll be asked to login, and then you'll get the consent screen
You should now see the app in your test.com`s marketplace apps list
You can do this by creating a new application in the chrome web store.
Make sure that you create this application in the web store with an account that belongs to the given domain. Next, restrict access to your domain.
Finally, you can install the application on the domain.
I've created a test listing for Google Apps Marketplace (GAMv2) and have specified a setup url. When testing using the "TEST INSTALL FLOW" button, the authorization screen pops up and clicking the "Accept" button takes me to a popup that confirms the application has been added. There's a "Launch app" button and a "Manage app" link on this 2nd popup. The "Launch app" button goes to the setup url that I entered in the listing definition.
Isn't the install flow supposed to redirect there automatically? I've seen other questions where this behaviour seems to be working on and off:
Google Marketplace App Install Flow
Google Apps Marketplace SDK install does not forward user to Setup URL
Google app marketplace sdk setup url stopped working
There's also this page in the marketplace documentation which says it is supposed to redirect:
https://developers.google.com/google-apps/marketplace/eap/oauthwalkthrough
Are other people having this problem?
In v1 of the marketplace, yes, set up links were automatically included in the linear install flow. In the new install flow set up links are presented separately. They're presented to users, but there is no guarantee that that a user will click it. Even in V1 there were some cases where a user could end up bypassing the setup link.
There are some improvements that can be made to encourage admins to revisit the setup if they skipped it. In either case, apps should be tolerant of these cases and adapt.
My recommendation is to check on login and enter the setup flow if it hasn't yet been performed. You can use the licensing API to check if the domain has installed from the marketplace or not. If you need to enforce things like requiring admin permissions, you can add further checks to see if the current user is an admin for the domain and give non-admin users a polite message indicating the app isn't ready for them to use yet.