IssueTracker

Note that the bug surfaced when I tried our app on android 5

I'm also seeing this problem with our library IOCipher (https://github.com/guardianproject/IOCipher).  It all builds and works fine, until I switch the test suite from targeting android-15 to android-21, then running the tests on a android-19 (4.4.4) ROM.  The NDK build uses r10d, and the IOCipher NDK build targeting android-7.

I found this workaround, which seems to work:

LOCAL_LDFLAGS += -fuse-ld=bfd

please reopen if you still see this with r12.

FYI. Here is a very hacky workaround.

I use appcompat support library quite a lot. Changing the compileSdkVersion only results in massive compile errors. If you are using appcompat-21, you must compile against api 21 or you will get compile errors.

This works fine if you are debugging against version 21. But when you are debugging on Jelly Bean (API 17), your debugger keeps dropping you to the API 21 source. Very annoying and hard to debug.

The solution I've ended up using is very hacky but works! Let's say you are trying to debug against API 17. Do the following:

 1. mv $ANDROID_HOME/sources/android-21 $ANDROID_HOME/sources/android-21-orig
 2. cp $ANDROID_HOME/sources/android-17 $ANDROID_HOME/sources/android-21
 3. restart android studio so it will pick up the correct paths.
 4. Debug

Just don't forget to put all the directories back after you're done.

[Comment deleted]

We use many @TargetApi(Build.VERSION_CODES.LOLLIPOP_MR1) or similar Annotations in our code, so even the hacky source copying method does not work.

Any advice on how to debug an older OS when using the appcompat-21 and these Annotations would be extremely useful... until then fixing bugs that only occur in older SDK source are extremely difficult