I have declared a string called Storage and set it to File.DirDefaultExternal. In my application that works out to be /storage/sdcard0/Adroid/data/com.B4a.RBudget/files.
When I compile the program in debug mode and load the compiled file, it works fine.
If this is first time run, a couple of data files are copied from Dir.Assets to the target directory of File.DirDefaultExternal which equals the above.
I have looked in the data file using a file explorer on the phone and the data is there at the correct location which in my case is com.B4a.RBudget.
However, if I exit the program and re-run it, the program cannot find the file because something in the program is looking for a directory called b4a.budget , not finding it, has created a new directory called b4a.budget and copied the default files into it from DirAssets. Now the program wants to use that directory.
If I recompile the program (all of this is done in debug mode) and reload it, it is back to using the correct directory.
My package name is com.B4a.RBudget.
Could the com part of the com.B4a.Rbudget be causing the problem? If so, why want it mess up under the debugger?
When I compile the program in debug mode and load the compiled file, it works fine.
If this is first time run, a couple of data files are copied from Dir.Assets to the target directory of File.DirDefaultExternal which equals the above.
I have looked in the data file using a file explorer on the phone and the data is there at the correct location which in my case is com.B4a.RBudget.
However, if I exit the program and re-run it, the program cannot find the file because something in the program is looking for a directory called b4a.budget , not finding it, has created a new directory called b4a.budget and copied the default files into it from DirAssets. Now the program wants to use that directory.
If I recompile the program (all of this is done in debug mode) and reload it, it is back to using the correct directory.
My package name is com.B4a.RBudget.
Could the com part of the com.B4a.Rbudget be causing the problem? If so, why want it mess up under the debugger?