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.
Related
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.
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.
When I try to publish a release in the Google Play Console, I constantly get this error:
Your app cannot be published yet. Complete the steps listed on the Dashboard.
And yes, I have indeed completed all the steps listed in the dashboard. I am using the new Play Console Beta, this is possibly related. What do I need to do before I can publish a release? Is there a hidden step?
After some searching, I found the button 'Use classic Play Console'. Apparently there are some steps to be finished that are simply not visible in the Beta:
Click on Use classic Play Console
Go to Pricing & distribution
Check the Content guidelines checkmark
Check the US export laws checkmark
Press Save draft
And you're good to go!
I had that problem and fix it. the problem caused by google console because they added one additional task in the app content about wither your app is consider a news app or not. so go to the inbox in your app and you will find that message from google click and you will be leaded to the content that you should fill. I hope that help any one having that issue.
I also had this problem. It was regarding setting your app as free from the App Pricing section as my application was free. So after setting that, I released my app.
We recently added a QnA Maker Bot to MS Teams and got it to Deploy on the Azurewebsites.net/api. Unfortunately in MS Teams when you direct message the bot it is not responding at all. We checked the logs and are not getting any errors either. Any Idea where we need to check next?
Thank you,
M
I had exactly this problem, and it was because I was trying to hit the bot directly rather than creating a Teams App first. You will need to install App Studio from the Apps blade on the left if you haven't already.
Open up App Studio and click on Manifest editor tab
Click Create a new app
Fill our all of the required information for App details
Generate/create an App ID. This is NOT the same as your Bot's App ID
Click on Bots tab under Capabilities and add your bot
Install app for testing in specific Teams or Chats
Submit is for if you want to publish to your company's App Store. If you download the package you could import it in Step 2 instead of creating a new app. Or use it as a template to do future apps offline instead of using App Studio for the whole process.
Once I set up the bot in this way, it started responding to me. I tried with another app after doing this for one and confirmed that I would NOT get a response from a bot unless I had set it up with a manifest through App Studio.
Ok, so without much notification given, adding market place listings to your vendor profile is no longer possible. The 'create new listing' button is greyed out.
I need to make changes to an existing marketplace listing but that gives errors. We are forced into the new SDK.
So I went ahead and enabled the apps market SDK, filled out all details including images of all sizes, add a COB extension for the contextual gadget and saved the whole thing.
A minute later I return to make a modification and dang... error: "We are looking into this.".
#Google: HELP !
UPDATE : I can reliably reproduce the error as explained here.
Enable Google Apps Marketplace SDK in your project
click on the gear icon, you will be directed to the old API Console
Fill out all details
Add a COB extension (Contextual gadget)
Save everything
Close the API console
Go back to your cloud console -> Google Apps Marketplace SDK
Click on the gear icon again
ERROR
Tested with several google accounts on different computeres and multiple projects on the cloud console.
#jonathanberi could we have a status on this issue, please? We are experiencing the exact same issue and we are unable to publish our app (which is ready) because of this bug. We have tried both creating a new Google Apps console project from scratch as well as modifying a draft of a yet to be published page with the same result. Is any information that we could provide to help?
You must fill out parameter name and a paramter value or your cloud console will return errors and you will not be able to recover from this.
Ouch, that were 3 useless weeks....