I've just created an app (slash command) and install it in one of my workspaces. But now I want to add the same app to another one. Is it possible without distribution to App Directory?
If you want to add you Slack app to another workspace, you can do so without going through the process of placing it on the App directory.
All you need to do is
add the ability to install your app to an workspace using OAuth 2.0.
enable public distribution
So instead of clicking "Install app to this workspace", which works great for private Slack app, which live in one workspace only, you need a script than can be called from a web browser to run the Oauth installation routine. This is usually done by adding a Slack button to your website.
You also need to enable "public distribution" for your app. Note, that is not the same as putting them on the App Directory, which requires submitting your app and undergoing a review by the Slack team.
Found the answer, in the small grey caption in the app creation form
Your app belongs to this workspace—leaving this workspace will remove your ability to manage this app. Unfortunately, this can’t be changed later.
Related
Summary: when other users find my Google Slides add-on in the Google Workspace Marketplace and try to install it, they hit a screen saying they need to request access. When they click the button to request access, it sends me (the script owner) a request to share the script file, which should not be necessary. How do I fix this?
I have a Google Slides add-on which has been publicly listed in the marketplace for years (predating the rebranding to Google Workspace). I last updated it in 2019, and recently I wanted to publish another update.
Since this is an old project, I had to go through migrating the add-on to its own standard GCP project and then getting OAuth verification for the (not very sensitive) scopes it needed. This is all done now. All throughout, the add-on has continued being listed in the Google Workspace Marketplace, even though no new users could use it.
All that is done, but other users are still unable to install the add-on from the Marketplace. Now, when they try to do so, they'll get a small new window pop up saying they need to request access - seemingly to the script file of the add-on. This shouldn't be necessary. Does anybody know why it's happening?
If you want to try yourself, the add-on is called Superuser Tools, and the Marketplace listing is here.
I have an app uploaded to the App Store but not submitted. I want to test with internal testers (me) and under the app’s TestFlight pane I have the one build which is indicated as “Testing”. When I click on the build and go to “App Store Connect Users” my email is listed as “invited” with the option to resend the invite.
But I haven’t received the invite and it’s not showing up in my TestFlight.
I’ve also tried adding myself in the external tester area but when I select my name in “add existing testers” window, “next” remains disabled.
I uploaded the app with an ad hoc provisioning profile, that may be the problem? I’m actually only aiming to use the app myself, so if there’s an easier way to use the existing ad hoc provisioned upload without fixing this while TestFlight issue I’d welcome that as well.
Thanks for the help!
We're trying to set up a new marketplace app. As suggested by the Google Apps setup UI, we have provided a Setup URL for setting up an account with the service.
However, if I click on the Test Install Flow button, it redirects to the Universal Navigation link instead of the dedicated application Setup url.
What's going on?
The setup URL is never invoked by Google. I don't know why, and I don't know why they provide a field for it.
An answer I got from a Google guy is that if you need an interactive setup you should just implement it in your Universal Navigation link (on the first time the admin opens it or something). The full answer is here: Google Apps Marketplace app installation callback
When a user goes to my unlisted marketplace app page and installs my app the authorization popup window just white screens and doesn't close. If I manually close the popup everything moves on like normal. I have a suspicion that it's because my app is unlisted, since I haven't seen the issue with other marketplace apps, but as of right now I can't change that.
Another issue we've had with that page is the Integrate with Google button doesn't seem to respect the current profile the user is using. It always seems to always use the default profile which can be confusing for the user if they wanted to use a different google profile they were currently using.
note: the app url i've posted is used for local development but it happens on our production app as well
When installing a Google Marketplace App, the flow usually ends with the admin in the app's settings on Google with the option to sign in now. Is there a way to end with the user actually using the app (i.e. not having to click the link to sign in to start using the app)? Could the user just be sent to the app on the optional setup without returning to the app settings page on Google without that causing other problems?
Some of the documentation says:
We strongly recommend that the administrator be directed through a short, linear series of actions and returned to Google quickly so additional users can start using the application.
I tried testing this out, but it seems like there's some lag between installing and the app showing up in the "more" drop down for Google (I tried installing another app and did end up on the final page but the app still didn't show up in another account. It's been a few hours and it still isn't there) so it's hard to tell if it's just slow or not actually installed on other users' accounts.
Sorry the last section was misleading. This is not a question about the link not showing up immediately.
The new experience for Google Apps Marketplace lets you land the user in the app instead of the admin console. There's now a popup for the app to request permissions and to agree to terms and then the user ends up in the app. One-step installation. Good work Google.