question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deploy to Mobile Center returning EISDIR: illegal operation on a directory, read

See original GitHub issue

I’m using “Deploy to Visual Studio Mobile Center” task in VSTS to deploy binary to Mobile Center. I have setup API access from VSTS to Mobile Center with the API key from Mobile Center with “Full Access”. I have set up App Slug correctly so I’m not sure what is the problem.

Here is the task output:

2017-07-31T13:04:07.3321637Z ##[section]Starting: Deploy to Visual Studio Mobile Center
2017-07-31T13:04:07.3321637Z ==============================================================================
2017-07-31T13:04:07.3321637Z Task         : Mobile Center Upload
2017-07-31T13:04:07.3321637Z Description  : Upload mobile app packages to Visual Studio Mobile Center
2017-07-31T13:04:07.3321637Z Version      : 0.119.1
2017-07-31T13:04:07.3321637Z Author       : Microsoft Corporation
2017-07-31T13:04:07.3331638Z Help         : Upload mobile app packages to Visual Studio Mobile Center
2017-07-31T13:04:07.3331638Z ==============================================================================
2017-07-31T13:04:09.1952666Z ##[error]Error: form-data: EISDIR: illegal operation on a directory, read
2017-07-31T13:04:09.3374890Z ##[section]Finishing: Deploy to Visual Studio Mobile Center

Please ask if you need any more info.

Thanks, Bojan

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:8

github_iconTop GitHub Comments

1reaction
bojanmisiccommented, Jun 3, 2020

It’s a dummy error message which can be related to a number of things. I admit I could have been a better open source contributor and write what was the original issue, but at that time it was a time pressured project and a really silly mistake which I can’t remember at the moment 😦. Apologies to everyone on the thread, but I agree with the above - the error message could be better!

1reaction
FlorisDevreesecommented, Sep 23, 2019

I had the same error message.

The error was on my side. In the build task I selected Select Release Notes File without specifying a valid Release notes file.

To be honest: The error message could be better. I lost about 20 minutes finding the source of this error…

Read more comments on GitHub >

github_iconTop Results From Across the Web

NPM stuck giving the same error EISDIR: Illegal operation on ...
This means that NPM is trying to do something to a file but it is a directory. In your case, NPM is trying...
Read more >
eisdir: illegal operation on a directory - You.com
npm command - Error: EISDIR: illegal operation on a directory, read. Asked Jun 19, 2017 • 4 votes 7 answers. QUESTION ANSWERS.
Read more >
Deploy Azure DevOps Builds with App Center - Microsoft Learn
You can deploy your apps from Azure DevOps to App Center with the Deploy with App Center Task. Note. For on-premise version servers, ......
Read more >
Docker Push Causes Error in Release Pipeline
... task results in the error "[error]EISDIR: illegal operation on a directory, ... This issue is read only, because it has been in...
Read more >
Errors resulting from nested folders: EISDIR, and expected ...
During a source:retrieve operation, a nested folder can result in the error "EISDIR: illegal operation on a directory".
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found