M Majed9621 Member Licensed User Nov 5, 2019 #1 Hi to all I change the package name from Build Configurations to com.mas.myapp.android but when I install the app through B4A bridge it creates folder with this package name anywheresoftware.b4a.b4abridge how to solve this problem Thanks in advance
Hi to all I change the package name from Build Configurations to com.mas.myapp.android but when I install the app through B4A bridge it creates folder with this package name anywheresoftware.b4a.b4abridge how to solve this problem Thanks in advance
Erel B4X founder Staff member Licensed User Longtime User Nov 5, 2019 #2 You are doing something wrong. Do you see this folder on the PC? Upvote 0
M Majed9621 Member Licensed User Nov 5, 2019 #3 I am not doing any thing wrong I just change the package name from Build Configurations as normal Do you see this folder on the PC? No, I see it on my phone Upvote 0
I am not doing any thing wrong I just change the package name from Build Configurations as normal Do you see this folder on the PC? No, I see it on my phone
Erel B4X founder Staff member Licensed User Longtime User Nov 5, 2019 #4 Majed9621 said: No, I see it on my phone Click to expand... It is not related to your app. It is B4A-Bridge external folder. You don't see your app folder because it is not accessible to other programs. Upvote 0
Majed9621 said: No, I see it on my phone Click to expand... It is not related to your app. It is B4A-Bridge external folder. You don't see your app folder because it is not accessible to other programs.
M Majed9621 Member Licensed User Nov 5, 2019 #5 How to make it accessible to other programs ? I mean is there special permission or some thing ? Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Nov 5, 2019 #6 File.DirInternal will never be accessible. You can use File.DirRootExternal (watch the runtime permissions video tutorial) or better use RuntimePermissions.SafeDirDefaultExternal Upvote 0
File.DirInternal will never be accessible. You can use File.DirRootExternal (watch the runtime permissions video tutorial) or better use RuntimePermissions.SafeDirDefaultExternal