[Bug] Build error with API version 28 or 30

[haan823]

Is there an existing issue for this?

• I have searched the existing issues.

Would you like to work on the issue?

• Assign this issue to me.

Describe the bug

When I tried to build the project with API version 28 or 30, I ran into some errors.

I failed to build and faced message ninja: build stopped: subcommand failed. even though test cases were all passed.

What I've tried as far is as follows, but they didn't work.

1. Change API version 30 to 28.
2. Reduce test cases.
3. Delete /.cxx directory and rebuild.
4. Delete euphony repository in my local storage and clone again

Expected Behavior

This is what I expected to happen.

Environment

- OS: Windows 10
- API level: 28, 30

Steps to reproduce

1. Run Android Studio.
2. Create device using API version 28 or 30.
3. Run 'java-sample'.
4. See all test cases are passed.
5. See build errors.

Anything else?

I refered to these issues and discussions.

• can't run gtest after #106 #116 (comment)
• 테스트케이스가 실패하지 않았는데 빌드에 실패하는 문제 #63
• Euphony build 및 test 실행 #45

When I used Pixel XL API 32, the project completely succeed to build.

Proposal

I think it is good to notice users who try to build with API version 28 or 30 that the API versions can make build errors. And also, how about do not run gtest with the API versions?

[yeonns]

@haan823 Thank you for reporting issues 👍 And your suggestion is also perfect! It would be good to block gtest with API 28 and 30.