Thanks for checking in on this. I’ve removed the MountPoint string and the output is basically the same. But please note that the output is positive, meaning that on my BP logic from above, when I read the Bool from the mount node it says true. I also see the app installed, I also get success on the install progress. Everything seems to be in order. The only suspicious log is where the free disk space check turns out ‘0’ - zero.
At this point I’m more concerned that I might be doing something wrong with generating the .pak file, although I follow the documentation steps. One strange thing that I’ve noticed is that in the release Launch Profile, the first one, which has a save archive .apk file by default, if I compare that .apk file with one that’s generated through the File>Package>Android method, their size differs, the Launch one being a bit smaller. I’ve tried installing both versions and running the app on the phone with no success.
So to better describe the pak generation process that I’m doing. I first use File>Package>Android_ASTC, then I use the Project Launcher drop down option and create two profiles with the “Minimal Android APK + DLC” option. I run the first profile. Then I make a change to the game level and the game assets. Then I save and run the second profile. I then upload the DLC content in the proper folder on my server. Again, when I run the app on my phone everything seems to be working and the mount operation outputs a true response, pretty much no matter what I write in the mount point, which makes me think that the mount procedure is done by default as the .pak gets downloaded.
I could zip up the project if anyone wants to test this.
Thanks