deno-slack-sdk: [BUG] Adding a Outgoing domain requires reinstall
The deno-slack versions
“deno-slack-sdk/”: “https://deno.land/x/deno_slack_sdk@2.2.0/”,
“deno-slack-api/”: “https://deno.land/x/deno_slack_api@2.1.1/”,
Deno runtime version deno 1.36.4 (release, aarch64-apple-darwin)
OS info ProductName: macOS ProductVersion: 13.5.2 BuildVersion: 22G91 Darwin Kernel Version 22.6.0
Describe the bug
My app has been live for some time with an integration to Salesforce (using outgoing domain). I now wrote a new integration for Marketing Cloud, adding the outgoing domain as needed. That worked fine using ‘Slack Run’, but when using ‘Slack deploy’ I would get an error
error: 'Requires net access to "mcm....."
After scratching my head a lot and testing a wide array of tests - the simple solution was to do a full uninstall 'Slack add delete" and then “Slack deploy” 🤯
Until this bug can be fixed (maybe in the CLI?), I suggest the documentation is updated so others save time 😄 (it’s also quite inconvenient to have to delete and then reinstall, since all triggers are lost and needs to be re-added. Additionally I need to add the App to all relevant channels +++)
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 2
- Comments: 30 (15 by maintainers)
The only workaround I’ve been able to find, is have a non-admin request approval to deploy, and have an admin approve it. If you’re the one that needs to deploy, have your IT team downgrade you to a regular Member > request the new deploy > wait for an Admin to approve > deploy again > once installed, your access can be upgraded back to Admin or Owner as needed, but only once the app has been deployed.
Update here: we are able to reproduce the core of this bug, I think:
We have a bug somewhere on our backend - we are investigating / addressing. Thanks for the reports and patience as we work through this!
This has been a hard to identify bug with no solid reproduction steps, unfortunately 😦
Due to the app-specific nature of these issues, if you are having problems here, you will need to request technical support from our feedback@slack.com support line, as our friends in Customer Success will have access to your production data, application IDs, logs and so on - which I am not authorized to access 😞
Sorry for the runaround 😢 if repro steps are ever able to be identified, then I can certainly more directly look into it.
I had the exact same bug, updated an existing app with brand new independent triggers/workflows/functions that was communicating with a new external domain, added this domain to outgoingDomains in the manifest and the app worked fine in local but not in remote (deployed). Switching around the 2 values in the outgoingDomains didn’t work.
Un-installing, deleting, and re-installing the app worked.
In my testing, as an admin in an enterprise workspace with app admin approval enabled, this now works.
Does it work for you as well now?
We are on Enterprise Select. No grid or multiple workspaces