aapt start failed on my Mac.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android
- Domain
- build-system, mobile-dev
Research direction
Start by inspecting the Android build configuration for the pinned build-tools 21.1.2, Android API 22, and Gradle versions. Reproduce the processDebugResources failure and the aapt “bad CPU type” error on macOS; done means the project builds with updated tool versions without this failure.
Written by the indexing model from the issue text.
Description
Not sure if this library still under maintenance? Seems like the build tools version is very low.
I'm evaluating this library for our project recently. I setup the build tools according to the specified version,
- Tools/Android SDK Build-tools (Rev. 21.1.2)
- Android 5.1 (API 22)
- Extras/Android Support Library
- com.google.android.gms:play-services-location:10.0.0
- com.google.android.gms:play-services-places:9.2.0
But build failed with the following error:
* What went wrong:
Execution failed for task ':android:processDebugResources'.
> A problem occurred starting process 'command '/Users/chaofan.zhang/Library/Android/sdk/build-tools/21.1.2/aapt''
When I try to run aapt itself, it gives me bad cpu type error.
% /Users/chaofan.zhang/Library/Android/sdk/build-tools/21.1.2/aapt
zsh: bad CPU type in executable: /Users/chaofan.zhang/Library/Android/sdk/build-tools/21.1.2/aapt
Can you upgrade the android build tool version, sdk version, also gradle version?
I tried to update those build tool and sdk versions to current, but it introduce api changes, and need to udpate code.
- Dominant language
- C++
- Stars
- 629
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/libaddressinput
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/libaddressinput#255 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
google/libaddressinput#245 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
google/libaddressinput#254 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 52/100
google/libaddressinput#250 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
google/libaddressinput#249 ·
All issues in google/libaddressinput
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
hipRTC lit tests compile against /opt/rocm's LLVM instead of the ROCm under test (ci/ hardcodes LLVM_PATH)Possibly taken @bernardogv claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
請增加教學：數字後的句號Open
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day