search

MicrosoftDocs / msteams-docs

Source for the Microsoft Teams developer platform documentation.
https://aka.ms/teamsdev
Creative Commons Attribution 4.0 International
277 stars 501 forks source link

'Open Developer Preview' Still Missing 48 Hours After Enabling Custom Apps #5114

Closed bweitzman closed 2 years ago

bweitzman commented 2 years ago

As others have posted about, we've enabled Custom Apps but the option for Developer Preview (to then turn on DevTools) is still missing from my desktop client after 48 hours. We've tried restarting PCs, closing/reopening the Teams app, etc. All I have in my Settings > About menu are Version, Legal, Privacy and cookies, and the two Third party notice options.

Side note, the guidance for enabling Developer Preview on this page is seemingly out of date as it says to click on my profile to get to About, but that button/menu no longer contains About. About is now under the ... menu left of my profile.

P.S. - I really don't appreciate that you made me sign up for a github account to tell you that your product is broken & the guidance on your published support page is wrong. I have a million other Microsoft accounts already, just let me use one of those when I need support!

ghost commented 2 years ago

Hi bweitzman! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

sayali-MSFT commented 2 years ago

@bweitzman -We are mainly responsible for Microsoft Teams app development related issues.

For Microsoft Teams product issues/failures your tenant Admin can reach out to Microsoft 365 Product Support.

For general questions about Microsoft Teams please post your question on Microsoft Teams Community.

bweitzman commented 2 years ago

@sayali-MSFT this is a really disappointing response. From other comments this is clearly an issue that others are also having, and forcing us to navigate Product Support via a tenant admin (slower and resource constrained for me, higher cost of responding for Microsoft as it has to be handled individually for every affected customer) is much less effective than acknowledging what is clearly a known issue and sharing the information on how to resolve/work around where anyone can see it so they don't too have to go down the Product Support rabbit hole. 100 times out of 100 I'm going to ask a web search (which inevitably leads to these support forums) before I bother a person directly.

ghost commented 2 years ago

Tell us about your experience!

Hi bweitzman! This issue is closed in our system. We would like your feedback on your experience with our support team and Platform.

Best regards, Teams Platform

ChetanSharma-msft commented 2 years ago

@bweitzman - We will check on it from our end and act on it accordingly.

sayali-MSFT commented 2 years ago

@bweitzman - Please have a look at this doc- https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/prepare-your-o365-tenant#enable-teams-for-your-organization Let us know if you have any query.

bweitzman commented 2 years ago

@sayali-MSFT I really appreciate your continuing to attempt to work with me on this. I can confirm that the setting you've linked is the one we enabled three weeks ago and the Developer Preview option is still not appearing for any of our users. This is the "known issue" I have been referring to, having seen several other threads reporting the same when browsing all feedback from the page I was originally following the instructions on.

Wajeed-msft commented 2 years ago

@bweitzman - could you please share screenshots of following?

Org-wide app settings:

image

Setup policies:

image
ghost commented 2 years ago

Hi bweitzman! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

bweitzman commented 2 years ago

Hi Wajeed-msft, thanks again for continuing to work this issue with me! I was hopeful that the first of your two screenshots would be what I was missing--as the documentation to enable Developer Tools only refers to the setting under Setup Policies from screenshot 2--but unfortunately we already had both set to On. Glad this exchange is happening in the comments though, as it may be the step others who stumble across this thread are missing!

Screenshots from our admin center are attached showing these settings enabled. Please let me know if you have any other ideas I can try out, or would like additional details from me.

screenshot-1

screenshot-2

Wajeed-msft commented 2 years ago

@bweitzman - Thanks for sharing the screenshots. Based on the screenshot I could see that this policy is applied to Viva Connections Pilot Group. Just to isolate the issue could you please try these two options and retry?

  1. Enable the custom apps for Global instead of custom group. Or
  2. Re-apply "Viva Connections Pilot" policy to specific user.
bweitzman commented 2 years ago

Thanks for these ideas. My IT department won't be ok with applying this policy globally. Everyone I've been working with to test this is in the pilot group, which we used to target viva connections before rolling it out broadly. The need for developer tools rose out of that test group as we are having some glitchy behavior pulling in our home page to Teams, and none of us on that testing team see developer tools.

I'll ask about reapplying the policy and let you know after 24-48 hours if that changes anything.

On Tue, Feb 22, 2022, 8:53 PM Wajeed-msft @.***> wrote:

@bweitzman https://github.com/bweitzman - Thanks for sharing the screenshots. Based on the screenshot I could see that this policy is applied to Viva Connections Pilot Group. Just to isolate the issue could you please try these two options and retry?

  1. Enable the custom apps for Global instead of custom group. Or
  2. Re-apply "Viva Connections Pilot" policy to specific user.

— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/msteams-docs/issues/5114#issuecomment-1048448165, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXQNFSGMXLIG2LHZYCWF7R3U4RR4XANCNFSM5NB2BBPA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

bweitzman commented 2 years ago

Confirming we've reapplied the policy for all members in our core team working this issue. Per documentation we'll give it 24 hours to take effect, then close/reopen Teams and see if that did the trick. I'll check back tomorrow with the results. Thanks again for all your help!

bweitzman commented 2 years ago

Back with good news: Removing and reapplying the policy seems to have worked, and I can now access DevTools to troubleshoot my wonky CSS in Viva Connections! Thanks to everyone on the team who helped me step through all of this.

For the sake of leaving some breadcrumbs behind that others experiencing the same issue can follow in the future, here's everything we stepped through:

  1. Verify these instructions were followed to enable uploading of custom apps, in Teams Admin Center under Teams Apps > Setup Policies.
  2. Verify the additional Teams Admin Center setting at Teams Apps > Manage Apps > Custom Apps > Interaction With Custom Apps is set to on, as shown in this screenshot.
  3. If still not seeing the option to Enable Developer Preview under ... > About in the Teams desktop app menu, remove and reapply the settings in Admin Center, wait 24 hours, reboot, and check again. This is what fixed it for us: screen-dev-preview-present screen-devtools-present

Adding a couple of suggestions for consideration by the Microsoft team(s) maintaining the support pages that pointed me to this forum, in case they see this comment as well:

  1. Add guidance for the 2nd bullet above (Interaction With Custom Apps setting) on either Teams Developer documentation page Test Your App > Prepare Your Microsoft 365 Tenant -- if Interaction With Custom Apps is necessary for all custom app scenarios -- or App Manifest > Public Developer Preview > Overview -- if this additional setting is only pertinent to enabling Developer Preview.
  2. Update guidance on the App Manifest > Public Developer Preview > Overview page to reflect the current location of Developer Preview (under the ... menu in Desktop, not under the profile menu as instructed).
  3. It seems from our troubleshooting in this thread that there may be a glitch with non-global policies not taking hold on the first application of these settings. The other threads in this forum detailing the same experience I had trouble with were closed before cause/resolution could be shared, but if this continues to pop up it may be worth further exploration by a QA team. If repeatable, a troubleshooting note on the Developer Preview Overview page would be helpful until the glitch can be patched.

Thanks again for all your help in seeing this through to resolution!

ghost commented 2 years ago

Tell us about your experience!

Hi bweitzman! This issue is closed in our system. We would like your feedback on your experience with our support team and Platform.

Best regards, Teams Platform