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.
Related
We have a web app that uses OAuth to sync user's gmail account asking for some credentials. Now since last week we are getting this message that "sign in with Google is temporarily disabled for app" but we haven't changed anything from our settings at all. Also we have everything approved and configured because it was working fine before that time.
You need to follow the process described [here][1] to request verification for your app.
[1] https://support.google.com/cloud/answer/7454865?hl=en
Also see https://gsuite-developers.googleblog.com/2018/06/new-oauth-protections-to-reduce-risk.html
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.
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.
I'm developing an app for a client and together we agreed to try Heroku, though neither of us has any experience with it. The client will be in control and will add me as a collaborator. The instructions at https://devcenter.heroku.com/articles/sharing seem pretty simple... except they don't seem to work.
I made an account and so did the client. The client ran the following:
heroku apps:create appname
heroku sharing:add myemail#gmail -app appname
The client says both of these actions reported success, but I haven't received an e-mail inviting me to collaborate on the app. Presumably some additional steps are required to get things going before collaborators can be added?
Can anyone explain what else we need to do? Alternately, I understand it's possible to transfer ownership of an app, would it be easier for me to create it and then transfer ownership to the client?
You can verify if the collaborator was added from the web UI on heroku.com - go to the 'My Apps' page, find the app and click on the collaborators icon and you should see your new collaborator listed. It's also possible to invite people directly from this page.
Our typical workflow is to build a site for the client in an app in our account and then transfer ownership of the application to the client for golive so they become responsible for billing and such like.
In order to be able to transfer the account, the person who you are transferring to needs to be a collaborator on the application.
We found the issue. We needed another dash in front of app in the add collaborator command; it should have been:
heroku sharing:add myemail#gmail --app appname