There is one possible reason for this behavior of OXCE for Android.
It is very convenient to put mods in the folder directly in the zip-archive without unpacking it. But it is very easy to make a mistake and download such an archive with a mod that will cause exactly the described error when launching the application. Often inside the archive is not a folder with the mod, and directly in the files mod, including metadata.yml. In this case, to avoid the error, you must first unpack the mod (in the folder designed for it), and then re-archive it in the zip file. And then the application will consider that it is a properly formed mod, and will not bring up the data import screen.
So you have to be careful not to put unchecked archives in the mods folder.
As an example I can show you one of the last times I had to repack a mod downloaded from this forum - from the thread
https://openxcom.org/forum/index.php/topic,10849.0.htmlBut if the same mod packaged in the archive correctly, then no problems at startup will not be.