Closed DeliciousLines closed 1 year ago
Please provide an example AAB to reproduce the issue.
Texture entries in your aab file are invalid as they are separated by \
instead of /
:
-rw---- 2.0 fat 2809 bl defN 23-Jan-25 15:16 META-INF/MANIFEST.MF
-rw---- 2.0 fat 3014 bl defN 23-Jan-25 15:16 META-INF/RELEASE-.SF
-rw---- 2.0 fat 1307 bl defN 23-Jan-25 15:16 META-INF/RELEASE-.RSA
-rw---- 2.0 fat 10 bX defN 70-Jan-01 01:00 BundleConfig.pb
-rw---- 2.0 fat 1423 bX defN 70-Jan-01 01:00 base/assets/pixel_shader.glsl
-rw---- 2.0 fat 7165 bX defN 70-Jan-01 01:00 base/assets/textures\dot128.png
-rw---- 2.0 fat 22490 bX defN 70-Jan-01 01:00 base/assets/textures\dot256.png
-rw---- 2.0 fat 4801 bX defN 70-Jan-01 01:00 base/assets/textures\quad128.png
-rw---- 2.0 fat 1017 bX defN 70-Jan-01 01:00 base/assets/vertex_shader.glsl
-rw---- 2.0 fat 268848 bX defN 70-Jan-01 01:00 base/lib/arm64-v8a/libmain.so
-rw---- 2.0 fat 210948 bX defN 70-Jan-01 01:00 base/lib/armeabi-v7a/libmain.so
...
All right I see, thank you!
Good evening, I am using bundletools to emulate what Google Play would do with an .aab archive (using build-apks) and I realised something goes wrong when generating the .apks archive: the assets sub-folders paths seem to no longer be valid.
For instance let us say we have the following structure in our assets folder:
When taking a look at the .aab archive, a.png and b.png are correctly represented as assets/textures/a.png and assets/textures.b.png However this is no longer the case in the .apks archive. The structure turns into the following:
This is an issue for me as I can no longer access the assets I want. Is this intentional or is it a bug?
The commands I use to generate the .aab archive:
The command I use to generate the .apks archive:
APK_NAME is set to training-time.apk