question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue on Android R

See original GitHub issue

Information

  1. Apktool Version (``) - 2.4.1
  2. Operating System (Mac, Linux, Windows) - Window 7 32bit
  3. APK From? (Playstore, ROM, Other) - ROM (Android R Beta Devce Samsung N20 ultra)

Stacktrace/Logcat

Targeting R+ (version 30 and above) requires the resources.arsc of installed APKs to be stored uncompressed and aligned on a 4-byte boundary

Include stacktrace here

No error building apk but App doesn’t get registered to system , found some documentation https://developer.android.com/about/versions/11/behavior-changes-11

Steps to Reproduce

  1. apktool

Frameworks

If this APK is from an OEM ROM (Samsung, HTC, LG). Please attach framework files (.apks that live in /system/framework or /system/priv-app)

APK

If this APK can be freely shared, please upload/attach a link to it.

Files.zip

Questions to ask before submission

  1. Have you tried apktool d, apktool b without changing anything? - Yes
  2. If you are trying to install a modified apk, did you resign it? Yes
  3. Are you using the latest apktool version? Yes

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

9reactions
BurgerZcommented, Oct 29, 2020

just do zipalign -f -p 4 input.apk output.apk after you compile the apk.

4reactions
steadfasterXcommented, Nov 11, 2021

for those (like me) who have not much exp with app dev (yet):

I stumbled over this error as well and I did the zipalign part and for sure my resources.arsc was not compressed (zipalign -v shows that!). The reason for me was that I still used jarsigner from an older guide I had… so the fix was simply using apksigner instead and it worked immediately ( source )

Read more comments on GitHub >

github_iconTop Results From Across the Web

"cannot resolve symbol R" in Android Studio - Stack Overflow
"R cannot be resolved" arise only if there is a problem with some of your resource files. So the best and effective way...
Read more >
Reporting bugs | Android Open Source Project
The Android Issue Tracker contains a list of pending technical tasks across a variety of topics, information relevant to those tasks, and information...
Read more >
Fix an installed Android app that isn't working - Google Support
Step 2: Check for a larger app issue · You can usually clear an app's cache and data through your phone's Settings app....
Read more >
"android.R.string.no" is wrong (resolves to "cancel") [36908899]
KitKat release, for example, - all file managers stopped working. KitKat release forced a lot of developers to perform a significant refactoring to...
Read more >
Adapting to Android 11 - a Look at Android 'R' - Esper Blog
But, I found that reading and re-reading Android 11 changes made it much easier to identify the root cause when I stumbled on...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found