azure-samples / functions-first-serverless-web-application Goto Github PK

Hi all, bumped into this while at step Resize Image with Azure Functions

The issue was jimp needed a missing dependency core-js

Resolved this by installing core-js via the Console of ResizeImage function

npm install --save core-js

Logging it here just in case anyone else faces the same issue.

The application does not upload images. 0%, no error message provided.

macOS Mojave Version 10.14.1
Chrome Version 70.0.3538.102

There seems to be an issue with the implementation for Computer Vision API as reported on MSDN:
https://social.msdn.microsoft.com/Forums/en-US/ccce7fd2-ae5d-40f7-b283-ad26c533496c/add-image-captions-with-computer-vision?forum=AzureFunctions

In my repro and validation work, I was seeing result.description populate with null Happy to dig deeper and create PR if need be.

When attempting the following command
az storage blob upload-batch -s . -d $web --account-name storageaccountname

I get the error
The requested URI does not represent any resource on the server

Changing the command to the below seems to work.
az storage blob upload-batch -s . -d '$web' --account-name storageaccountname

Just a head's up - if you're trying to work through this demo on a local machine CLI, you will get some nasty looking errors running the "npm generate" step if your version of Node.js is less than v8. I realize you're targeting the Cloud Shell where this is probably taken care of for the user automatically, but a quick requirements section on the README would probably be helpful to add for people trying to do this locally.

https://docs.microsoft.com/en-us/azure/functions/tutorial-static-website-serverless-api-with-database?tutorial-step=1

Here's where I found my answer ultimately...
nuxt/nuxt#36

After enabling authentication, window.authEnabled = true in settings.js, when clicking the login button an incorrect redirect url is supplied. The redirect url supplied from the login button to Microsoft's login page is the address of the window.apiBaseUrl setting (my Azure Function App URL) instead of the window.location.href as specified in the static/auth.js line 21 (from commit c3af43c).
After I authenticate and get back to my Function APP URL I can manually replace the fqdn part with my Static Web URL and get to the app with a "Welcome [subscriptionId redacted] [Logout]" at the top of the page.
Not sure what to change to fix it... help!