Bulk import fails: “no files provided”

As seen in this screenshot, I have clearly provided files to import. However, clicking the “Import” button results in an error message:

files: no files provided

I have tried several times, and I even cleared browser cache just in case. Same behavior each time. I cannot import lessons.

@zoran

I continue to try a number of things to get the bulk import working. I tried importing just one new lesson instead of several. Same error. I switched languages from Russian to German. Same issue. Would really like to see this working again.

@zoran

I can’t even import a lesson the “old fashioned way” (non-batch import).

It is not just bulk importing that stopped working. Everything was fine until a couple days ago, but importing no longer works. I have tried doing it within a group, and that does not work either. It usually looks like it worked but when you try opening the file, you get an error.

Good to know. I was beginning to think it was some problem on my end.

@zoran

So now that I’m back in the home office, the issue turns out to be that the batch import is broken now in iOS. I have long used my iPad for the batch import, because I prefer the particular work-flow I have on the iPad. It does not work in Safari (which I have always used), nor does it work in chrome which I installed as a test.

Back on my Mac, it works just fine in Safari.

​​

@zoran

So the issue is with drag-and-drop.

If I select the files by navigating to them via the file system, Lingq will import the lessons. Perhaps iOS 26.5.2 has broken something for Lingq. It is not broken for other apps. It works fine for the google drive app on the ipad.

@tiago-ribeiro

Are you referring to doing the bulk import from iOS (like on an iPad)? If so, I finally tracked down the variable: drag and drop does not work. If I drag the files into the import as I always have before, Lingq reports “no files provided.” If I select the files navigating down into the folder, it’s working.

@vernmartin Thanks, I appreciate the info. I will forward this to our development team. We will have it sorted out.

Thank you. It’s still working on MacOS.