Recently, our (published) app stopped working on mobile, with the above message, "This tab is not available on mobile". The app is a custom teams tab basically.
What can be causing this issue?
From our side, we have not changed anything (neither in the manifest nor in the hosting).
Are there some changes in the teams policy or maybe some new requirements or changes?
In the desktop/web client the app works like it did before. On the mobile, if you try to click a link to the app tab, it shows this notification tooltip "not available on mobile" instead of opening the tab.
Manifest version: 1.9
"#microsoft/teams-js": "^1.12.1",
Not sure, if the versions are related, the mobile client shows that tooltip without even trying to open the tab.
It looks like the problem appeared with some latest update of the Teams client. The app is still working fine with Teams client from June 2022, but starts showing this message "tab is not available on mobile" if the Teams mobile client is updated to the latest version.
I have noticed that now there is a button to "Add an app.." in the teams app on mobile. Are there some new requirements for existing apps because of this maybe (so that existing apps won't work on mobile unless adapted)?
Related observation: all app tabs created disappeared on "More..." tab after mobile teams client is updated
Appreciate any insights what might be causing the issue?
Posting the solution here from the linked issue if somebody else faces it. The message was appearing because websiteUrl property was not set in the tab configuration. It is now required for the tab to appear in the mobile client. Setting this property in the tab configuration resolves the issue.
Related
I (the owner of the channel) added a Lists tab to the Channel. It works fine when I view it in the browser. For one member, when he uses the web version of Teams, this tab refuses to load. It displays "There was a problem reaching this app". It works fine when he views this on the phone.
How can he fix this issue?
I'm currently learning Teams development and I just installed the Teams Toolkit extension. Following the quickstart guide, launching the app opens my browser with the Teams web app and the message
App not found, Please verify the app and it's[sic] access
permissions.
Fortunately, this app can still be launched when selecting the "Preview in Teams" option in the Developer Portal.
Quoting the GettingStarted.txt:
If you Start Debugging in a browser and Teams shows the message "App not found, Please verify the app and it's access permissions", it means the app hasn't been uploaded to Teams Dev Portal. To resolve this, follow the steps in the Quick start section above. The Project > TeamsFx > Configure for SSO menu command will do this step for you.
Except it was successfully uploaded to Dev Portal.
What I did
Did this "Configure for SSO" thing. No problems with that and the app was successfully added to the Developer Portal.
Where I searched for an answer
VS Marketplace page for Teams Toolkit (Reviews, Q&A)
Github page (issues) for Teams Toolkit
This very site - Stack Overflow.
Obviously, I'm not 100% sure that I haven't missed anything.
Temporary solution
In the meantime, I set the "launchBrowser" property to "false" in launchSettings.json. However, it's a waste of time to constantly go back to the Developer Portal to launch it, especially when the functionality is there.
Visual Studio 2019, Microsoft Development Account.
Thanks in advance.
We tried to repro this issue at our end and it is working fine for us. Could you please make sure app is opened in same tenant with which you configured for SSO. Also please remove all credentials from cache to make sure its not taking another credentials and try again.
Assuming nothing else was changed from the new project template, there are a few things you can try to narrow down the issue.
Open your browsers web dev tools and watch the console after clicking the Add button (before you see the error message). Sometimes a useful error message from the developer portal helps identify the issue.
Verify that when Visual Studio launches the URL, the correct tenant is loaded in Teams.
Run the project in VS, then manually navigate in your browser to the endpoint of your tab that you expect to work. It would be something like https://localhost:44357/tab by default (the value is in the manifest.json). The sample won't work completely because it's not running inside Teams, but you should be able to verify it's working locally.
If none of that helps, please log an issue on the GitHub page and we can investigate a bug.
I'm working on a project, which integrates with some G Suite services, and is implemented using G Suite Marketplace SDK, so we can have it published on the GSM. We have unpublished versions of the app, which are used for testing.
Up until a few days ago, we were able to test the app, by going to Cloud Console at https://console.developers.google.com/, then to "G Suite Marketplace SDK", then to "Configuration", where we had a an "Integrate with Google" button. Earlier, this button had a "Test installation flow" label.
A few days ago, the button disappeared. No errors are shown. What I did notice as well, is that the Cloud Console UI changed as well (e.g. Configuration renamed to App Configuration, there's also a "Store listing" option etc.)
Does anyone have any idea about why the button might have disappeared?
Reported in Issue Tracker:
I have filed a bug in Issue Tracker regarding this behaviour:
Button “Integrate with Google” does not get displayed in the “Configuration” tab of Marketplace SDK
To anyone affected by this, I'd suggest clicking the star on the top-left of the referenced page, in order to keep track of its development and to prioritize it.
Update from Issue Tracker: Marketplace SDK UI has recently changed:
The disappearance of this button is caused by a change in Marketplace SDK UI, which also explains the other changes you noticed (e.g. App Configuration). This from Issue Tracker:
There as been an update in the UI, and the button Integrate with Google has been removed from the new UI.In any case, there are other ways to test add-ons before publishing them publicly (see here), including installing an unpublished one, deploying an Apps Script web app for testing or publishing the app privately so that it's only visible to users in your domain.As a sidenote, recording a video of an app is no longer required for OAuth review when trying to publish it to the Marketplace (for which this button was useful).
I have the below queries:
We were trying to expose the SharePoint portal in Microsoft Teams by creating a Personal Tabs App. In order to display it in the side app bar, we have added the app in Global Policy (admin.teams->Teams app->setup policy) and rearranged the App to top.
But the app is not getting displayed in the app bar for any user. Are there any more configurations need to be implemented?
Will this take hours to get displayed in the Teams UI, does E3 subscription will take more time to render the APP in Teams compare to E5?
If so, how many hours do we need to wait to see the update in Teams UI?
Please note this app is created via App Studio, not custom code.
Reference links:
https://www.youtube.com/watch?v=WyB4MBQwICs
https://learn.microsoft.com/en-US/microsoftteams/teams-app-setup-policies
Yes it is taking 24 hours to get displayed in the side bar. The configured tabs are displaying successfully in Teams web app/via browser. But not rendering in the desktop version. The tabs url changed in the below format to overcome this issue but not sure why this is replicating. Tab url format: https://tenant.sharepoint.com/_layouts/15/teamslogon.aspx?spfx=true&dest=/SitePages/Home.aspx
I am trying to build a Teams tab using an SPFx web part for a demo.
On my inital app the Sync to teams button in the app catalog was failing with this console error being returned...
https://{TENANT}/sites/AppCatalog/_api/web/tenantappcatalog/SyncSolutionToTeams 400
After running into this problem I started again and this time followed the below tutorial step by step but on my tenant the Sync to Teams button is disabled (This step is near in the end in the Making the web part available in Microsoft Teams section)
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/using-web-part-as-ms-teams-tab
I then tried to follow the alternative method of side-loading the app by creating a manifest manually using this tutorial...
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/creating-team-manifest-manually-for-webpart
This resuted in the installation succeeding as far as the setup tab screen (this provides a preview of your tab in a model popup before adding the tab to a channel)
The result was "Sorry, something went wrong" (This was the end result of side-loading both my customised web part another freshly yo sharepoint generated scaffold.
Really stuck on whether there's a tenant issue or maybe some node package or SPFx version issue.
Any thoughts would be greatly appreciated.
I received a same error from console which led me to this article.
In this case, the app was already synced to Teams store. If that's the case, you should find and remove it by opening Teams -> Apps -> Built for [tenantname]. After removing it here, I am able to successfully sync my app once more.
I'm using SPFx 1.8.1 version and added TeamsTab in supportedHosts manifest file. Deployed in tenant app catalog and tried to Sync to Teams. Then I'm getting same issue of SyncSolutionToTeams with 400 error. Please find the attached screenshot from console windwow.
The error occurs if the app is still in the Teams catalog. It doesn't override it and instead throws the error. This is a known bug and we will look to fix it in the future. For now, please try either manually updating the app from Teams (not from the SharePoint app catalog) or to delete the Teams app and then to resync from SharePoint.
In my case this error occurs when I changed title in webpart manifest file (webpart.manifest.json). When I rejected the change, it works. Probably there was some inconsistency in project files.