Issue: AAPT2 Process Unexpectedly Exit After Merging PR #5604 #5632

TanishMoral11 · 2024-12-30T15:15:30Z

TanishMoral11
Dec 30, 2024
Collaborator

Hello everyone,

After the PR #5604 was merged, I started facing an issue in Android Studio when I updated my develop branch, as well as other branches. Upon building the project, I encountered the following error:

AAPT2 process unexpectedly exit. Error output: aapt2.exe W 12-30 20:33:18 20424 5956 LoadedArsc.cpp:682] Unknown chunk type '200'.

I have already attempted the following solutions:

Followed the suggestion in this StackOverflow answer.
Tried the common solutions like:
- Cleaning and rebuilding the project.
- Invalidating the cache and restarting Android Studio.

Unfortunately, none of these approaches have worked, and I am now stuck, unable to make any further progress.

I believe this might be a common issue for anyone who has updated their branch with the latest changes. I would greatly appreciate it if someone could provide guidance or share any suggestions to resolve this problem.

Thank you in advance for your time and assistance!

Answered by BenHenning

Jan 21, 2025

This issue was caused by an incompatibility with Gradle (it's actually a problem within the AGP toolchain itself). See #5604 (comment) and surrounding comments for a lot more discussion on the topic.

The issue should now be resolved fully since Gradle has been disabled in the codebase (and will soon be completely removed) as Bazel won't run into this issue.

View full answer

tobioyelekan · 2025-01-04T10:51:55Z

tobioyelekan
Jan 4, 2025

Currently having the same issue

2 replies

TanishMoral11 Jan 16, 2025
Collaborator Author

Hey @tobioyelekan , Have you resolved this issue?

tobioyelekan Jan 16, 2025

Unfortunately, I have not had the chance to do what Peres recommended, I'll try out too when I get the chance to.

adhiamboperes · 2025-01-07T14:08:20Z

adhiamboperes
Jan 7, 2025
Collaborator

@TanishMoral11, @tobioyelekan, PTAL at https://github.com/oppia/oppia-android/wiki/Oppia-Bazel-Setup-Instructions. to setup Bazel, and refer to #5643 to set up the Bazel plugin in order to be able to continue building the project (and using newwer versions of Android Studio).

11 replies

TanishMoral11 Jan 18, 2025
Collaborator Author

Today I tried to do a fresh re-build of the project and was able to build it with the wsl. Can you please try with a fresh setup just to make sure none of the old configurations are affecting the build.

These are the steps I followed:

From cmd I Installed ubuntu 22.04

wsl --install Ubuntu-22.04

set username 
password

Open the ubuntu 22.04 terminal

Bazel instruction with wsl Ubuntu-22.04

$ sudo apt update && sudo apt upgrade

$ sudo apt install openjdk-17-jdk
$ java --version
openjdk 17.0.10 2024-01-16
OpenJDK Runtime Environment (build 17.0.10+7-Ubuntu-122.04.1)
OpenJDK 64-Bit Server VM (build 17.0.10+7-Ubuntu-122.04.1, mixed mode, sharing)

$ sudo apt install python2
$ sudo apt install gcc

$ mkdir -p $HOME/Android/Sdk

Download the command line tools from https://developer.android.com/studio#command-tools

$ cp /mnt/c/Users/<Name>/Downloads/commandlinetools*.zip $HOME/Android/Sdk

$ cd $HOME/Android/Sdk
$ sudo apt install unzip
$ unzip commandlinetools*.zip

$ cd cmdline-tools/
$ mkdir tools
$ mv -i * tools
$ cd ..

$ echo "export ANDROID_HOME=\$HOME/Android/Sdk" >> ~/.bashrc
$ echo "export PATH=\$ANDROID_HOME/cmdline-tools/tools/bin/:\$PATH" >> ~/.bashrc
$ source ~/.bashrc

$ sdkmanager
$ sdkmanager --install "platform-tools"
$ sdkmanager --install "platforms;android-34" [updated version]
$ sdkmanager --install "build-tools;32.0.0"

$ sudo apt install apt-transport-https curl gnupg -y
$ curl -fsSL https://bazel.build/bazel-release.pub.gpg | gpg --dearmor >bazel-archive-keyring.gpg
$ sudo mv bazel-archive-keyring.gpg /usr/share/keyrings
$ echo "deb [arch=amd64 signed-by=/usr/share/keyrings/bazel-archive-keyring.gpg] https://storage.googleapis.com/bazel-apt stable jdk1.8" | sudo tee /etc/apt/sources.list.d/bazel.list

$ sudo apt update && sudo apt install bazel
$ bazel --version
bazel 8.0.0 [will default to install the latest version]

$ sudo apt install bazel-6.5.0
$ bazel --version
bazel 8.0.0

$ sudo rm /usr/bin/bazel
$ sudo ln -s /usr/bin/bazel-6.5.0 /usr/bin/bazel
$ bazel --version
bazel 6.5.0

$ mkdir $HOME/opensource
$ cd $HOME/opensource

$ git clone https://github.com/<GitHub-Username>/oppia-android.git

$ cd oppia-android/
$ scripts/setup.sh
-bash: scripts/setup.sh: Permission denied

$ chmod +x scripts/setup.sh
$ scripts/setup.sh
Using Ktlint 0.37.1
Ktlint file downloaded
Using Checkstyle version 8.37
Checkstyle file downloaded
Using Bufbuild version v0.37.1
Buf downloaded
Using Buildifier version 3.4.0
Buildifier file downloaded

$ bazel build //:oppia
Target //:oppia up-to-date:
  bazel-bin/oppia_deploy.jar
  bazel-bin/oppia_unsigned.apk
  bazel-bin/oppia.apk

My setup
And the generated oppia.apk should be a fully functioning development version of the app that can be installed using adb - though I had to copy it over to the windows path to install from the Windows cmd as wsl wasn't able to detect the connected devices.

Can you confirm if the issue persists with a fresh rebuild too?

Hey @Rd4dev ,
Thank you so much for your help! I decided to try a fresh installation again, and thankfully, the previous error is gone (hopefully some progress has been made :> ).
However, I’m now facing the following issue:

tanishmoral@Tanish:~/opensource/oppia-android$ bazel build //:oppia && adb install -r bazel-bin/oppia.apk
INFO: Analyzed target //:oppia (361 packages loaded, 6925 targets configured).
INFO: Found 1 target...
ERROR: /home/tanishmoral/.cache/bazel/_bazel_tanishmoral/57a402bbe3009b818831969a3a323e61/external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/BUILD:3:13: Building external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/libr8.jar (16 source files) and running annotation processors (AutoValueProcessor) [for tool] failed: (Exit 1): java failed: error executing command (from target @bazel_tools//src/tools/android/java/com/google/devtools/build/android/r8:r8) external/remotejdk11_linux/bin/java -XX:-CompactStrings '--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' ... (remaining 18 arguments skipped)
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CompatDexBuilder.java:38: error: cannot find symbol
import com.google.devtools.build.lib.worker.ProtoWorkerMessageProcessor;
                                           ^
  symbol:   class ProtoWorkerMessageProcessor
  location: package com.google.devtools.build.lib.worker
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CompatDexBuilder.java:39: error: cannot find symbol
import com.google.devtools.build.lib.worker.WorkRequestHandler;
                                           ^
  symbol:   class WorkRequestHandler
  location: package com.google.devtools.build.lib.worker
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:36: error: cannot find symbol
import com.google.devtools.build.lib.worker.ProtoWorkerMessageProcessor;
                                           ^
  symbol:   class ProtoWorkerMessageProcessor
  location: package com.google.devtools.build.lib.worker
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:37: error: cannot find symbol
import com.google.devtools.build.lib.worker.WorkRequestHandler;
                                           ^
  symbol:   class WorkRequestHandler
  location: package com.google.devtools.build.lib.worker
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/OptionsConverters.java:27: error: cannot find symbol
  public static class PathConverter extends Converter.Contextless<Path> {
                                                     ^
  symbol:   class Contextless
  location: interface Converter
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CoreLibraryDesugar.java:58: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CoreLibraryDesugar.java:70: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CoreLibraryDesugar.java:83: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CoreLibraryDesugar.java:96: error: incompatible types: Class<PathConverter> cannot be converted to Class<? extends Converter>
        converter = PathConverter.class,
                                 ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CoreLibraryDesugar.java:124: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:75: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:89: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:102: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:143: error: incompatible types: Class<PathConverter> cannot be converted to Class<? extends Converter>
        converter = PathConverter.class,
                                 ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:364: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/DexFileMerger.java:116: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/DexFileMerger.java:129: error: incompatible types: Class<PathConverter> cannot be converted to Class<? extends Converter>
        converter = PathConverter.class,
                                 ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/DexFileMerger.java:150: error: incompatible types: Class<ExistingPathConverter> cannot be converted to Class<? extends Converter>
        converter = ExistingPathConverter.class,
                                         ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CompatDexBuilder.java:170: error: cannot find symbol
        WorkRequestHandler workerHandler =
        ^
  symbol:   class WorkRequestHandler
  location: class CompatDexBuilder
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CompatDexBuilder.java:171: error: package WorkRequestHandler does not exist
            new WorkRequestHandler.WorkRequestHandlerBuilder(
                                  ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CompatDexBuilder.java:172: error: package WorkRequestHandler does not exist
                    new WorkRequestHandler.WorkRequestCallback(
                                          ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CompatDexBuilder.java:177: error: cannot find symbol
                    new ProtoWorkerMessageProcessor(System.in, realStdOut))
                        ^
  symbol:   class ProtoWorkerMessageProcessor
  location: class CompatDexBuilder
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/CompatDexBuilder.java:394: error: cannot find symbol
      return new AutoValue_CompatDexBuilder_DexingKeyR8(
                 ^
  symbol:   class AutoValue_CompatDexBuilder_DexingKeyR8
  location: class DexingKeyR8
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/desugar/OutputConsumer.java:209: error: cannot find symbol
        super(Opcodes.ASM9, null);
                     ^
  symbol:   variable ASM9
  location: interface Opcodes
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/OptionsConverters.java:39: error: method does not override or implement a method from a supertype   
    @Override
    ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/OptionsConverters.java:54: error: method does not override or implement a method from a supertype   
    @Override
    ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:685: error: cannot find symbol
      WorkRequestHandler workerHandler =
      ^
  symbol:   class WorkRequestHandler
  location: class Desugar
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:686: error: package WorkRequestHandler does not exist
          new WorkRequestHandler.WorkRequestHandlerBuilder(
                                ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:687: error: package WorkRequestHandler does not exist
                  new WorkRequestHandler.WorkRequestCallback(
                                        ^
external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/r8/Desugar.java:690: error: cannot find symbol
                  new ProtoWorkerMessageProcessor(System.in, realStdOut))
                      ^
  symbol:   class ProtoWorkerMessageProcessor
  location: class Desugar
Target //:oppia failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 29.203s, Critical Path: 9.28s
INFO: 992 processes: 358 internal, 623 linux-sandbox, 11 worker.
FAILED: Build did NOT complete successfully

I believe this error might be related to the WORKSPACE configuration. Could you please suggest any solutions or areas I should check to resolve this?

Thanks !!

TanishMoral11 Jan 20, 2025
Collaborator Author

Hey @Rd4dev ,

Thank you for your guidance! I’ve tried all the solutions, and I’ve finally managed to set up Oppia in my dual-boot setup. Currently, I am using Ubuntu 22.04.5.

Progress so far:

On Ubuntu, I successfully set up Bazel with Oppia. However, the issue regarding the AAPT2 process still persists. Here’s the error output:

AAPT2 process unexpectedly exit. Error output: 
aapt2.exe W 12-30 20:33:18 20424 5956 LoadedArsc.cpp:682] Unknown chunk type '200'.

As per this Discussion, I ran the commands via the terminal, and the app works correctly.

@manas-yu , I Have Some Questions :

I downloaded and built the app using:

bazel build //:oppia && adb install -r bazel-bin/oppia.apk

If I switch to another branch (e.g., Branch 2), do I need to run the same command again and then execute the app using:

adb shell am start -n org.oppia.android/.app.splash.SplashActivity

Can you confirm if the following is the correct approach to run the app via terminal, or am I doing something wrong?

bazel build //:oppia && adb install -r bazel-bin/oppia.apk 
adb shell am start -n org.oppia.android/.app.splash.SplashActivity

Additional Observations:

I switched to Ubuntu due to Windows’ path-related issues. However, when I run:

bazel build //:oppia && adb install -r bazel-bin/oppia.apk

my laptop freezes, and I am unable to move the cursor or perform any actions.

My system specifications are quite good, so I’m unsure why this happens. Are you facing the same issue?

Thank !!

manas-yu Jan 20, 2025
Collaborator

Hi @TanishMoral11,

Yes, the build command bazel build //:oppia needs to be run whenever there are code changes, including when switching branches. It updates the APK at bazel-bin/oppia.apk, which you can then install using adb install -r
The first build with Bazel is resource-intensive and may cause your system to freeze, especially if other processes are running. I recommend closing unnecessary applications and running the build command. Subsequent builds will be faster as Bazel caches intermediate results.

Rd4dev Jan 21, 2025
Collaborator

Apologies, @TanishMoral11, I couldn’t get to this sooner. Super glad the dual-boot option worked! — it seems like the quickest fix. I’ll look into the Windows fixes and the issue above as soon as I can.

adhiamboperes Jan 22, 2025
Collaborator

@TanishMoral11, from yesterday's CLaM meeting, we will be building and installing with bazel run //:install_oppia_dev going forward.

uphargaur · 2025-01-12T12:22:18Z

uphargaur
Jan 12, 2025

Hi @adhiamboperes ,

I am also facing this issue in the development branch only. I tried setting up Bazel as well, but it overloads the RAM, causing my system to hang and eventually quit. Can we consider an alternative for this?

Here are my system specifications:

1 reply

adhiamboperes Jan 14, 2025
Collaborator

@uphargaur, how much RAM and free storage do you have ?

BenHenning · 2025-01-21T19:19:05Z

BenHenning
Jan 21, 2025
Maintainer Sponsor

This issue was caused by an incompatibility with Gradle (it's actually a problem within the AGP toolchain itself). See #5604 (comment) and surrounding comments for a lot more discussion on the topic.

The issue should now be resolved fully since Gradle has been disabled in the codebase (and will soon be completely removed) as Bazel won't run into this issue.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Issue: AAPT2 Process Unexpectedly Exit After Merging PR #5604 #5632

{{title}}

Replies: 4 comments 14 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Issue: AAPT2 Process Unexpectedly Exit After Merging PR #5604 #5632

TanishMoral11 Dec 30, 2024 Collaborator

Replies: 4 comments · 14 replies

tobioyelekan Jan 4, 2025

TanishMoral11 Jan 16, 2025 Collaborator Author

tobioyelekan Jan 16, 2025

adhiamboperes Jan 7, 2025 Collaborator

TanishMoral11 Jan 18, 2025 Collaborator Author

TanishMoral11 Jan 20, 2025 Collaborator Author

Progress so far:

Additional Observations:

manas-yu Jan 20, 2025 Collaborator

Rd4dev Jan 21, 2025 Collaborator

adhiamboperes Jan 22, 2025 Collaborator

uphargaur Jan 12, 2025

adhiamboperes Jan 14, 2025 Collaborator

BenHenning Jan 21, 2025 Maintainer Sponsor

TanishMoral11
Dec 30, 2024
Collaborator

Replies: 4 comments 14 replies

tobioyelekan
Jan 4, 2025

TanishMoral11 Jan 16, 2025
Collaborator Author

adhiamboperes
Jan 7, 2025
Collaborator

TanishMoral11 Jan 18, 2025
Collaborator Author

TanishMoral11 Jan 20, 2025
Collaborator Author

manas-yu Jan 20, 2025
Collaborator

Rd4dev Jan 21, 2025
Collaborator

adhiamboperes Jan 22, 2025
Collaborator

uphargaur
Jan 12, 2025

adhiamboperes Jan 14, 2025
Collaborator

BenHenning
Jan 21, 2025
Maintainer Sponsor