Hello, I'm new to Geotab Add-in development. Just created a simple Asp.Net Core WebApp with Razor pages and deployed to Azure. The web app is rendering fine by itself and accessible by public; but once I add an "Add-in" in My Geotab and configured the url to point to it, it seemed to only want to load briefly and then it disappeared. Behind the browser, there was some js lib errors that were not existing when the website is standalone. According to your dev guide, there are two types of Add-ins, "Pages" and "Buttons" - "A custom page Add-in can be thought of as a complete web application inside your Geotab account". But looks like there are some restrictions based on the issue I encountered. What are these restrictions?  In my standalone web app, I also added CORS policy to allow origin from   https://my.geotab.com.  Thanks for your time and attention.

A Webapp developed in .net and deployed at Azure (public) cannot be loaded in Add-in

page-user page-user-steve-yang-10671 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

Ok, It works now. The key is to use window.appConfigure to intercept the current httpcontext host address which I didn't. <code>window.appConfig.apiBaseUrl = '@($"{ViewContext.HttpContext.Request.Scheme}://{ViewContext.HttpContext.Request.Host}")'</code>Previously, I used: <code>apiBaseUrl = "https://geotab-addin-test-amcsh0erb0gue5e8.eastus2-01.azurewebsites.net"</code>  Thanks for your time.

The issue now is that API call to any endpoint hosted in our Azure App Service is blocked when I ran the same app inside Geotab Add-in.  For example, you can browse to this public API test end point <a href="https://geotab-addin-test-amcsh0erb0gue5e8.eastus2-01.azurewebsites.net/api/GeotabDbStatus/status?dbname=localdb" target="_blank">geotab-addin-test-amcsh0erb0gue5e8.eastus2-01.azurewebsites.net/api/GeotabDbStatus/status?dbname=localdb</a>, and you will see result {"status":1,"url":null} as expected. But when accessing the same API endpoint from a JS function after I added the page as an Add-in to my.geotab.com, nothing happened, and in the browser console it showed: "Failed to load resource: the server responded with a status of 404 (Not Found)" I already configured our WebApp (<a href="https://geotab-addin-test-amcsh0erb0gue5e8.eastus2-01.azurewebsites.net/" target="_blank">Home page - Actsoft.Integrations.GeotabAddin.WebApp</a>) CORS policy to accept my.geotab.com as origin. Initially, I used relative path to access the API controller inside our web, and the API path became my.geotab.com/api/GeotabDbstatus/status?dbname=***. That of course did not work.

Thanks for getting back to me. After some more digging and readings, I realized that the main issue was that I expected the navigations and form posting currently working in a hosted Azure Web App would continue to work inside Geotab Add-in, but I shouldn't have. Now that I changed my expectation and implemented some JS logic in the places where navigating between pages and form posting were needed , and it seemed to work for me now.

Hello,

Thanks for getting back to me. After some more digging and readings, I realized that the main issue was that I expected the navigations and form posting currently working in a hosted Azure Web App would continue to work inside Geotab Add-in, but I shouldn't have. Now that I changed my expectation and implemented some JS logic to in the places where navigating between pages and form posting were needed , and it seemed to work for me now.


Thanks,



Steve Yang

Sr. Developer

Development

[https://www.actsoft.com/emailimages/email_sig-phone_icon.jpg]813-936-2331

[https://www.actsoft.com/emailimages/email_sig-linkedin_icon.jpg][https://www.actsoft.com/emailimages/email_sig-facebook_icon.jpg][https://www.actsoft.com/emailimages/email_sig-twitter_icon.jpg]

Hello, I'm new to Geotab Add-in development. Just created a simple Asp.Net Core WebApp with Razor pages and deployed to Azure. The web app is rendering fine by itself and accessible by public; but once I add an "Add-in" in My Geotab and configured the url to point to it, it seemed to only want to load briefly and then it disappeared. Behind the browser, there was some js lib errors that were not existing when the website is standalone. According to your <a href="https://developers.geotab.com/myGeotab/addIns/developingAddIns/" target="_blank">dev guide,</a> there are two types of Add-ins, "Pages" and "Buttons" - "A custom page Add-in can be thought of as a complete web application inside your Geotab account". But looks like there are some restrictions based on the issue I encountered. What are these restrictions? In my standalone web app, I also added CORS policy to allow origin from https://my.geotab.com.  Thanks for your time and attention.

ბოლო აქტივობა

A Webapp developed in .net and deployed at Azure (public) cannot be loaded in Add-in