ntentUrl or the optional settings.removeUrl, or settings.websiteUrl are provided but not valid.See the next section, Common problems with the settings object. The provided settings were invalid: The other reason the settings may not be saved is if the call to tSettings(settings) provided an invalid settings object, or the call wasn't made at all. If no save handler was registered, the saveEvent.notifySuccess() call is made automatically when the user selects Save.If the callback doesn't call saveEvent.notifySuccess() within 30 seconds or calls saveEvent.notifyFailure(reason) instead, this error is shown.The save success message was never received: If a save handler was registered using (handler), the callback must call saveEvent.notifySuccess(). When adding a tab, if you select Save but receive an error message indicating the settings can't be saved, the problem could be one of two classes of issues: The tab settings can't be saved on selecting Save The Save button isn't enabled on the settings dialogĮnsure to call (true) after the user has input or selected all required data on your settings page to enable the save button.

If you experience consistent or intermittent caching issues where updates to your web app aren't appearing when it's hosted within a Teams tab, check your server cache settings and use Cache-Control headers to ensure your desired client caching behavior. Changes to my web app aren't reflected in its Teams tab

Your authentication logic must use a method other than redirect. Login pages don’t render in iFrames as a safeguard against clickjacking. A blank tab appears when the given tab URL redirects to login screen.

Microsoft teams app issues