Android Question Publish App not working

[omoba]

Hi,

Pls any suggestions as to why I am having this issue?

My app creates a folder, downloads (ftp) a db file from a sever to the folder and display data based on current or chosen date.

The app works fine on my device in all modes during development but when I publish it in play store, I get an error --see attached image

I am noticing that in development --the app creates desired folder and downloads the db file to the folder
but when published, the app is not creating the folder --thus nowhere to download them db file to

Any reason why app works in development but not in play store?

The first thing i do in Activity_Create(FirstTime As Boolean)

If File.Exists(File.DirInternal, "/Folder/") = False Then
        File.MakeDir(File.DirInternal, "/Folder/")
End If

Pls any suggestions?

 

[Erel]

The behavior of the app during development (in release mode) is the same as the behavior of the store app.

Where is the code that creates the database? Based on the error message, you are using an old version of B4A or you have deleted the starter service. Don't delete it.

 

[omoba]

I am using Version 3.82. Is upgrade needed?

The code worked just fine for other essentially same app for other clients.

Only difference is referencing different servers

 

[omoba]

Confirmed issue is no code it is the server. I used another sever and the file downloads and app works fine.

Now I need to figure out why the file is not downloading from the server (wordpress)

 

[DonManfred]

I am using Version 3.82. Is upgrade needed?

3.82 is VERY OLD now. It is from 2013 or maybe 2014?

A Update is strongly suggested. Your app will not work successfully on newer Versions of Android. At least not when using targetSDK 26+ (which you need as Google requires it).

 

[sorex]

Now I need to figure out why the file is not downloading from the server (wordpress)

wordpress is not a server, it's probably apache.

see if you can download it after renaming the file to whatever.zip

you might use an extention that is not allowed in the current site config which results in an error.