Closed tuxxon closed 1 year ago
Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.
Hi @tuxxon , thanks for reporting this issue. There are many reasons for causing this "Unable to reach app. Please try again", so I need more info to identify your problem. I saw from your provided manifest and source code that you kept the "searchQuery" command from the template. Can you please try this command on your deploy and see if it works? Through this test I can know whether part of your commands work or all command don't work.
To test this, you can @ your deployed message extension and search "test" from the Teams top search bar. If it works, you should see the following items:
Hi @yukun-dong
1. 2.
I have got the same error message - "Unable to reach app. Please try again" = "앱에 연결할 수 없습니다. 다시 시도하세요."
Hi @tuxxon. I have tried your manifest, code and your steps on my machine and I didn't see this error. So I think your deploy process is OK. Did you customise some config before provision and deploy?
From your reply, it seems your message extension has trouble connecting to your app service. You can use below methods to do some troubleshoot:
Please let me know if you find any insights.
Your Question: Did you customise some config before provision and deploy?
I think I didn't. but, Just in case I will create another project again and will try this again.
I will be back soon. :-)
Hello @yukun-dong
After creating a new sample as follows:
Create a new Teams App
and created a new app without any chagnes. and I did my steps that I commented above. and I've got the success only once.
But, after that, The message - "Unable to reach app. Please try again" is shown again.
I've got the error messages from azure log steams by the guide as follows:
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>IIS Detailed Error - 404.0 - Not Found</title><style type="text/css"><!--body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;}code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;}.config_source code{font-size:.8em;color:#000000;}pre{margin:0;font-size:1.4em;word-wrap:break-word;}ul,ol{margin:10px 0 10px 5px;}ul.first,ol.first{margin-top:5px;}fieldset{padding:0 15px 10px 15px;word-break:break-all;}.summary-container fieldset{padding-bottom:5px;margin-top:4px;}legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;}legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px;font-weight:bold;font-size:1em;}a:link,a:visited{color:#007EFF;font-weight:bold;}a:hover{text-decoration:none;}h1{font-size:2.4em;margin:0;color:#FFF;}h2{font-size:1.7em;margin:0;color:#CC0000;}h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;}h4{font-size:1.2em;margin:10px 0 5px 0;}#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS",Verdana,sans-serif;color:#FFF;background-color:#5C87B2;}#content{margin:0 0 0 2%;position:relative;}.summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}.content-container p{margin:0 0 10px 0;}#details-left{width:35%;float:left;margin-right:2%;}#details-right{width:63%;float:left;overflow:hidden;}#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF;background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal;font-size:1em;color:#FFF;text-align:right;}#server_version p{margin:5px 0;}table{margin:4px 0 4px 0;width:100%;border:none;}td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:normal;border:none;}th{width:30%;text-align:right;padding-right:2%;font-weight:bold;}thead th{background-color:#ebebeb;width:25%;}#details-right th{width:20%;}table tr.alt td,table tr.alt th{}.highlight-code{color:#CC0000;font-weight:bold;font-style:italic;}.clear{clear:both;}.preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;}--></style>
</head><body><div id="content"><div class="content-container"><h3>HTTP Error 404.0 - Not Found</h3><h4>The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.</h4></div><div class="content-container"><fieldset><h4>Most likely causes:</h4><ul> <li>The directory or file specified does not exist on the Web server.</li> <li>The URL contains a typographical error.</li> <li>A custom filter or module, such as URLScan, restricts access to the file.</li> </ul></fieldset></div><div class="content-container"><fieldset><h4>Things you can try:</h4><ul> <li>Create the content on the Web server.</li> <li>Review the browser URL.</li> <li>Create a tracing rule to track failed requests for this HTTP status code and see which module is calling SetStatus. For more information about creating a tracing rule for failed requests, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>. </li> </ul></fieldset></div>
<div class="content-container"><fieldset><h4>Detailed Error Information:</h4><div id="details-left"><table border="0" cellpadding="0" cellspacing="0"><tr class="alt"><th>Module</th><td> IIS Web Core</td></tr><tr><th>Notification</th><td> MapRequestHandler</td></tr><tr class="alt"><th>Handler</th><td> StaticFile</td></tr><tr><th>Error Code</th><td> 0x80070002</td></tr>
</table></div><div id="details-right"><table border="0" cellpadding="0" cellspacing="0"><tr class="alt"><th>Requested URL</th><td> https://pas9179cbbot:80/api/messages</td></tr><tr><th>Physical Path</th><td> C:\home\site\wwwroot\api\messages</td></tr><tr class="alt"><th>Logon Method</th><td> Anonymous</td></tr><tr><th>Logon User</th><td> Anonymous</td></tr>
</table><div class="clear"></div></div></fieldset></div>
<div class="content-container"><fieldset><h4>More Information:</h4>This error means that the file or directory does not exist on the server. Create the file or directory and try the request again.<p><a href="http://go.microsoft.com/fwlink/?LinkID=62293&IIS70Error=404,0,0x80070002,14393">View more information »</a></p><p>Microsoft Knowledge Base Articles:</p>
</fieldset></div></div></body></html>
Please let me know how to fix this problem.
@tuxxon Can you help provide the following info?
Click "Debug Console" -> "CMD"
Go to "site/deployments", there should be a folder with very long string name. For example:
Go to it and paste a screenshot of the "log.log". If there are multiple folders, just provide the lastest one.
@yukun-dong
screen-shot
As you see, there is no folder having a long string.
I will remove this bot after fixing the issue.
@tuxxon For 1, the config is OK. For 2, did you actually do the deploy? If you deployed before there should have such files, no matter succeed or fail. To double check, you can go to "Deployment Center" "Logs", see if there is any logs. If yes, click the log and you can see some deployment details.
Also go to "Console", type in "dir" under "wwwroot" and see if your files are actually uploaded to App Service.
If you cannot see the deployment log and doesn't see you file uploaded. I suggest you to do the deploy again. Make sure you select the right subscription.
@yukun-dong I did the command below
$ teamsfx deploy
if this command is right, I deployed this bot app.
Anyway, According to your comment, I will try this again. be back soon.
I've got a new error after removing this bot app and creating a new sample.
@yukun-dong
@yukun-dong
~I've got the error message - Unable to reach app. Please try again.~
~### scm log~
I've got the issue point
Describe the bug When running the message extension app locally, it works normally, By the way, When running the one after deploying by using
teamsfx deploy
, it cant' browse a webview for fetchTask=trueThe error message is
앱에 연결할 수 없습니다. 다시 시도하세요.
.please let me know what the problem is on my deploying process as follows.
To Reproduce Steps to reproduce the behavior:
Apps
.Manage your app
.Publish an app
.Upload a custom app
.You can see the abnormal messages as the screenshot shows.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
Normal screenshot on local
Abnormal screenshot after deploying
VS Code Extension Information (please complete the following information):
CLI Information (please complete the following information):
Additional context
manifest.xml
teamsBot.ts