Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

XHR/Fetch requests return #VALUE! on Windows build 16.011406.20002 #115

Closed
keyur32 opened this issue Feb 15, 2019 · 8 comments
Closed

XHR/Fetch requests return #VALUE! on Windows build 16.011406.20002 #115

keyur32 opened this issue Feb 15, 2019 · 8 comments
Assignees
@keyur32
Labels
Priority 1: ASAP High priority request Status: fixed Fix is deployed and available to customer Type: product bug Bug in the Office Add-ins platform or Office JavaScript APIs

Comments

@keyur32
Copy link
Collaborator

keyur32 commented Feb 15, 2019 •
edited

Custom Functions on Windows that use XML or Fetch will see #VALUE! as the XHR call may fail.

To workaround, please use: Use Mac or Excel Online
@keyur32 keyur32 self-assigned this Feb 15, 2019
@keyur32 keyur32 added the Type: product bug Bug in the Office Add-ins platform or Office JavaScript APIs label Feb 15, 2019
@keyur32
Copy link
Collaborator Author

keyur32 commented Feb 15, 2019

Will be fixed in the next build

@keyur32 keyur32 changed the title XHR/Fetch requests are failing on Windows build 16.011406.20002 XHR/Fetch requests return #VALUE! on Windows build 16.011406.20002 Feb 16, 2019
@keyur32 keyur32 mentioned this issue Feb 16, 2019
Closed
@keyur32 keyur32 added the Priority 1: ASAP High priority request label Feb 19, 2019
@keyur32
Copy link
Collaborator Author

keyur32 commented Feb 19, 2019

This has been fixed and we are waiting the next build to rollout to Insiders Fast channel.

@keyur32 keyur32 added the Status: fixed Fix is deployed and available to customer label Feb 26, 2019
@keyur32
Copy link
Collaborator Author

keyur32 commented Feb 27, 2019

The build has now been deployed. Please update your build to Version 1903 (11414.200014)

@eldargum
Copy link

eldargum commented Mar 1, 2019

@keyur32 thanks! it's working. But when I use XMLHttpRequest to my local IIS I see only #GETTING_DATA and #VALUE! after 1-2 minutes as a result of my custom function. I copied the certificate to trusted folder.
And second question - when will the Custom function be in Production, not Preview?

@keyur32
Copy link
Collaborator Author

keyur32 commented Mar 6, 2019

Hey @eldargum, what build are you seeing this under? On Windows, Online or Mac?

(We're hoping to stabilize these last set of issues and we'll be close to getting add-ins with custom functions ready for GA (at least our V1) -- barring any last minute issues; so please continue to report bugs! :)

@eldargum
Copy link

eldargum commented Mar 6, 2019

Hi @keyur32, I use 11414.20014 build on Windows.

@keyur32
Copy link
Collaborator Author

keyur32 commented Mar 6, 2019

Thanks, can you also share the runtime log. You can ping me directly: kepatel@microsoft.com. thanks!

@keyur32
Copy link
Collaborator Author

keyur32 commented Mar 11, 2019

Marking this closed as it is something related to the developer environment (still checking to see what that culprit is for that ).

@keyur32 keyur32 closed this as completed Mar 11, 2019
millerds added a commit to millerds/Excel-Custom-Functions that referenced this issue Mar 28, 2022
@millerds
Merge pull request OfficeDev#115 from millerds/update-test-webpack
d9d5017 
Remove test babel/polyfill
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@keyur32 keyur32

Labels
Priority 1: ASAP High priority request Status: fixed Fix is deployed and available to customer Type: product bug Bug in the Office Add-ins platform or Office JavaScript APIs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@keyur32 @eldargum