OK, I haven't followed up on this thread because my initial thought was that since I am still able to compile my app using B4A 9.01 to get the smaller APK size using
@Ivica Golubovic's library, the issue of generating an APK of almost 3x the size when compiled using B4A 13 was not very important one for me at this time.
But I just realized that when I want to post the app in the playstore, I will need to generate an AAB file, which B4A 9 can't do.
So, this is actually an important issue because one of the major advantages my app has over the competition is it's small size because it will typically run on devices with low memory, and since the app needs to stay running in the background, the lower the size, the better the chances android won't try to kill it.
When FileProvider was external (as in B4A 9),
@Ivica Golubovic's library was able to easily replace the file provider functionality, so the entire runtime permission lib did not have to be included, which kept the APK size down. But it seems that since it is now an internal function in B4A 13, it is dragging in extra unneeded code and bloating the APK/AAB.
So, how can I prevent some internal fileprovider related function/library from being used so that it will instead just use
@Ivica Golubovic's library which provides all the file provider functions my app needs?
Are there some class(es) I can specify with the #ExcludeClasses feature to prevent the extra bloat from being included in the app?