B4A Library AppCompat - Make Material Design apps compatible with older Android versions

This library is a wrapper for the Google AppCompat v7 support library.

B4A V6.0 or newer is required!
From V3.52 on B4A V6.80 or newer is required! If you still use B4A < V6.80, use V3.51 of this library.

The main reason for this library is to make your apps compatible with older Android versions and to use features in old Android versions which were implemented in newer Android releases. One big advantage of this library is that you can bring Material Design to pre Lollipop Android devices.

Setting up the library
Note: Please, Please read these instructions carefully. AppCompat depends on many things like a special theme with special features. Even special versions of build tools are required and last but not least there are often bugs in the Google support libraries.

I created this instructions to help you getting things ready for using AppCompat. So please follow these instructions carefully and all should work as expected and you don't have to ask in the forum.

Thanks.

The library uses the Android Support Repository. Please install it from the Extras Section of the Android SDK Manager. If you upgrade from an earlier release you can deinstall the "Android Support Library" since it is outdated and marked as obsolete in the Android SDK.
  1. First copy the AppCompat.jar, AppCompat.aar and AppCompat.xml files to your additional libraries folder.
  2. Start the Android SDK-Manager and download/update the latest Extras->Android Support Repository. Use at least support repository 36!
  3. In Android SDK-Manager be sure that the "Android SDK Build-tools" 25.x.x is installed! Deinstall all versions prior to version 25! If you leave older versions than 23.0.3 of build tools installed, your compiled app may work on Android 5.0 and above but it will fail on older Android versions like KitKat.
  4. In the B4A IDE in your projects check the AppCompat library on the libraries tab.
  5. Make sure that you reference the latest android.jar in the IDE under the "Tools/Configure Paths" menu. Don't worry. The android.jar is only used for compilation. It does not mean that you can't run your app on lower Android Versions. The Support libraries require to compile against the same API version as the library itself. So for Support library 25.xx which is the current now you should compile with API25 android.jar.
  6. If you are updating from a version older than v3.20 then remove the b4a_appcompat resource folder delivered with older versions of this library.
To use the AppCompat library your activities MUST extend android.support.v7.app.AppCompatActivity (extending the old android.support.v7.app.ActionBarActivity still works.)

B4X:
 #Extends: android.support.v7.app.AppCompatActivity

Additionally you MUST use one of the AppCompat themes like Theme.AppCompat. You can set it directly in the manifest editor or create your own theme that has an AppCompat theme as its parent. The easiest way is to set the AppCompat theme in the manifest:

B4X:
SetApplicationAttribute(android:theme, "@style/Theme.AppCompat")

If you have upgraded this library from an older version than 3.20 then you have to remove the #AdditionalRes: attribute related to the AppCompat library from your projects. They are not needed anymore.

Some Tutorials for this library
Material Design 2 - Using the AppCompat library
Material Design 3 - Using a ToolBar as ActionBar
Material Design 4 - Modifyable and advanced Menu

Troubleshooting Guide
Because it is not so easy to setup this library I will try to give a troubleshooting guide here for the most common problems.

1. Compile always with the newest android.jar file. This can be configured in the IDE under "Tools/Configure Paths". Download the latest platform version with the SDK Manager and configure it with the IDE. Don't worry, your app will still run on older platform versions. AppCompat support library needs this only at compile time.

2. Be sure you have a correct theme file for your project. If the app seems to crash immediately without a stack trace it is most probably a problem with the theme file.

3. If you post your issue in the forum please provide the stack trace of the error! And before you post, please do a forum seach. Most probably the same error was previously reported by another user. If you don't see a stack trace in the log window, please try the unfiltered logs. Unfortunately most errors only show when you have your device connected via USB in the unfiltered logs.

4. If you post your issue in the forum please provide as many information as possible. The error you receive, screenshots if possible and most important: the stack trace.

Your support:
Creating libraries and wrappers for existing library projects is a lot of work. The use of this library is totally free and you even don't need to mention in your app that you use it.
But if you use this library in your projects and you think it is useful to you please consider to make a donation:

Thanks very much for your support.

Version History

V1.00
  • Object AppCompat - Utilities which are useful for working with AppCompat
  • Object ACActionBar - Like StdActionBar or StdActionBarHelper to control some features of the ActionBar.
  • Object ACEditText - Replacement for EditText with Material Design colors.
  • Object ACCheckBox - Replacement for CheckBox with Material Design colors.
  • Object ACRadioButton - Replacement for RadioButton with Material Design colors.
  • Object ACSwitch - Wrapper for a Switch.
  • Object ACFlatButton - Borderless Button for Dialogs etc.
V1.10
  • New object ACToolBarLight - Toolbar for light themes
  • New object ACToolBarDark - Toolbar for dark themes
  • New object ACActionMenu - Create action menus (action items and/or overflow menu everywhere in your layout. (The view needs to have a minimum width of 56dip to work properly. This seems to be a bug and hopefully will change in later versions of the AppCompat library)
  • New object ACActionModeWrapper - Change ActionBar/Toolbar to an ActionMode ActionBar. Mostly used for multiselect lists.
  • New object ACMenu - Access and modify the ActionMode, ActionMenu or Toolbar menus.
  • New object ACMenuItem - Access and modify the ActionMode, ActionMenu or Toolbar menu items.
  • New object ACPopupMenu - Implements a popup menu.
  • New object ACSearchView - Add a search view to your ActionBar/Toolbar
  • Add: AppCompat object has new methods for getting height of system components like StatusBar, ActionBar and NavigationBar.
  • Add: AppCompat object has a new method for setting the elevation of every view. With this all views (like Panels) can cast shadows. Unfortunately the shadow is only visible on Android 5.0 or above.
V2.00
  • #Extends: android.support.v7.app.AppCompatActivity should now be used (ActionBarActivity still works)
  • New object ACSpinner - AppCompat Spinner with additional support to show an icon in front of the text.
  • New object ACSubMenu - Adding Submenus to menus.
  • New Event ACSearchView_QueryChanged
  • Some internal changes (xml files for Views are not needed anymore)
  • Support for tinting Drawables.
  • Possibility to set a click effect to any view - This is experimental. It should add a ripple effect in Lollipop and above and a color change in previous versions.
  • To update from V1.xx to V2.00 delete the b4a_appcompat resource folder and copy the new one from the archive. The old xml files for buttons, edittext etc. are not needed anymore. Now there is only one xml for the spinner needed.
V3.00
  • Requires B4A 6.0 or above
  • References AppCompat from Maven repository
  • Full designer custom properties support for all views
  • Fix: ACRadioButton now supports grouping in a panel
  • Desupport of the Activity Entry animation.
  • New: ACSeekbar
  • Fix: ACSearchview closed() event does not fire (AppCompat bug). Added workaround for this.
  • Fix: Fixed several minor and major bugs
  • New example App which shows main features
V3.01

  • Fix: additionally depends on com.android.support:support-v4 which should make it work better if you mix old and new libraries.
  • Fix: ACSearchview_Closed event will not crash on API < 12 but it will not fire on these devices. Sorry, there is no workaround for this.
V3.20
  • Moved resource files to aar library file - see new setup instructions
  • Fix: ACButton ButtonColor attribute now works on all Android versions.
V3.30
  • Fix: Remove log output from ACSpinner
  • Fix: Hopefully fixed crashes with missing designer properties
  • Fix: Mixed case Eventnames in Toolbars now working
  • New: Support for ActionViews in MenuItems (Needed for CustomViews in NavigationView of DesignSupport library)
  • Change: Minimum Support Repository 36
V3.41:
  • Fix: Change packagename to anywheresoftware.b4a.orbjects to reduce resouce fields
V3.42:
  • Fix: ToolBars should raise their events correctly again.
V3.50:
  • New: Support for CharSequences wherever possible.
V3.51
  • Fix: Getters return String instead of CharSequence again to avoid problems.
V3.52
  • Fix: Compiled against B4A 6.80 Core library to avoid some problems with CharSequences.
V4.00
  • Change: Compiled against 28.0.0 Support library
  • New: Styles for most Views
 

Attachments

  • AppCompatBaseExample3_20.zip
    10.9 KB · Views: 4,453
  • AppCompatLib3_51.zip
    87.2 KB · Views: 2,270
  • AppCompatLib3_52.zip
    87.3 KB · Views: 4,179
  • AppCompatLib4_00.zip
    181.8 KB · Views: 4,244
Last edited by a moderator:

Haris Hafeez

Active Member
Licensed User
Longtime User
I was given a new machine and while setting it up to continue working on the Material Design stuff here, I have run into the brick wall of ClassNotFoundException. From the logs(as seen below), I can see that for some reason AppCompat library(its classes) aren't being loaded but I can't figure out why. Any advice?

I'm using JDK1.8, Android jar is v22 and my additional libs contains support v4,v7 and appcompat jars.

Following is the log:

java.lang.RuntimeException: Unable to start activity ComponentInfo{de.amberhome.appcompat.serachviewexample/de.amberhome.appcompat.serachviewexample.main}: android.view.InflateException: Binary XML file line #19: Error inflating class android.support.v7.internal.widget.NativeActionModeAwareLayout
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2325)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2390)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5257)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: android.view.InflateException: Binary XML file line #19: Error inflating class android.support.v7.internal.widget.NativeActionModeAwareLayout
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:757)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:806)
at android.view.LayoutInflater.parseInclude(LayoutInflater.java:890)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:802)
at android.view.LayoutInflater.inflate(LayoutInflater.java:504)
at android.view.LayoutInflater.inflate(LayoutInflater.java:414)
at android.view.LayoutInflater.inflate(LayoutInflater.java:365)
at android.support.v7.app.AppCompatDelegateImplV7.ensureSubDecor(AppCompatDelegateImplV7.java:324)
at android.support.v7.app.AppCompatDelegateImplV7.setContentView(AppCompatDelegateImplV7.java:237)
at android.support.v7.app.AppCompatActivity.setContentView(AppCompatActivity.java:111)
at de.amberhome.appcompat.serachviewexample.main.onCreate(main.java:59)
at android.app.Activity.performCreate(Activity.java:5990)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1106)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2278)
... 10 more
Caused by: java.lang.ClassNotFoundException: Didn't find class "android.support.v7.internal.widget.NativeActionModeAwareLayout" on path: DexPathList[[zip file "/data/app/de.amberhome.appcompat.serachviewexample-2/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
at java.lang.ClassLoader.loadClass(ClassLoader.java:469)
at android.view.LayoutInflater.createView(LayoutInflater.java:571)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:743)
... 23 more
Suppressed: java.lang.ClassNotFoundException: android.support.v7.internal.widget.NativeActionModeAwareLayout
at java.lang.Class.classForName(Native Method)
at java.lang.BootClassLoader.findClass(ClassLoader.java:781)
at java.lang.BootClassLoader.loadClass(ClassLoader.java:841)
at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
... 26 more
Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack available
 

Haris Hafeez

Active Member
Licensed User
Longtime User
I copied the two (v4 and v7) support libs from extras\android\support\v7\appcompat\libs of my install. The version for from SDK Manager is 22.2
 

thedesolatesoul

Expert
Licensed User
Longtime User
Its worth checking it again. (That class is present in my v7 support which is 22.1.1)
As you mentioned its a new machine, and i had a similar problem.
I updated my support libs via SDKManager to the latest BUT I had another copy of the SDK, and i kept copying the non-updated v7 support lib to my additionallibs and it took me hours to figure out that the version being compiled against was not the latest.
 

Haris Hafeez

Active Member
Licensed User
Longtime User
Thanks TDS. But I think Google has broken the v7 support library. I opened the v7 jar to find the class file NativeActionModeAwareLayout that the class loader is complaining about and I couldn't find it in there.

So I suppose it might be worth updating the first post to warn the users NOT to update their support library beyond 22.0(I have this working on a different machine).
Have a look at the following screenshot of the folder in v7 jar that should contain android.support.v7.internal.widget.NativeActionModeAwareLayout

upload_2015-6-19_0-23-53.png
 

Haris Hafeez

Active Member
Licensed User
Longtime User
The trouble with these official support libraries is that you can't download an earlier version using the sdk manager. I guess I will have to manually get an older version from one of my other machines.
 

corwin42

Expert
Licensed User
Longtime User
The problem must be somewhere else. I use 22.2 support libraries for a while now. No problems here.

My first guess: You are referencing wrong/old resource files of support library in your project.

Have you tried to clean the project and compile again?
 
Last edited:

Haris Hafeez

Active Member
Licensed User
Longtime User
Yes I've tried to clean and rebuild the project. Also deleted the app that's installed and then cleaned and built but not getting anywhere.

Can you see that class when you open the support jar in 7zip or winrar? I cannot see this class and I believe this is an issue, unless the classes are coming from somewhere else on the emulator(or phone).
 

corwin42

Expert
Licensed User
Longtime User
No, this class isn't in my support library, either.

Thats because I guess that somehow old resource files are used which reference the NativeActionModeAwareLayout which is no longer present in the library.

Always be sure to use the resource files for the AppCompat support library with the correct version. Otherwise you get the craziest errors.
 

Haris Hafeez

Active Member
Licensed User
Longtime User
So perhaps I should download an older version of the sdk as well? Because this is a new machine, I've only installed API 22 and API 19 from platform SDKs. Do you reckon I should download API 21 as well? Though how that will bring the missing class back is beyond my imagination.
 

corwin42

Expert
Licensed User
Longtime User
No, you don't need an older support library.

Where is your #additionalres for the appcompat support library is pointing to. Directly to the sdk directory or do you have a local copy for them?
 
Last edited:

Haris Hafeez

Active Member
Licensed User
Longtime User
That was it. My oh my. I used one of the other libraries here(I think one of the material ones) and placed them in my additional res folder for libs. This was what was referencing that class.

Thank you so much corwin! That was an awesome insight.
 

corwin42

Expert
Licensed User
Longtime User
Ok, glad I could help.

I have seen so many configuration errors with the Appcompat library. I am now able to smell where the problem is. :)
 

Haris Hafeez

Active Member
Licensed User
Longtime User
I have set up a lib-res folder inside my custom/additional libs folder. This is where I add library specific res folders.
 

corwin42

Expert
Licensed User
Longtime User
I just added a small "troubleshooting guide" to the first post. Hopefully it will help to find the most common issues.
 

specci48

Well-Known Member
Licensed User
Longtime User
Hi corwin42,

a small wish for the ACSearchView. Could we get an onQueryTextChange event?
I'd like to process the search during the user input without pressing the submit button.
 

shashkiranr

Active Member
Licensed User
Longtime User
a small wish for the ACSearchView. Could we get an onQueryTextChange event?
I'd like to process the search during the user input without pressing the submit button.

It will be very useful if it is added.

Also @corwin42 i want to hide the other icons on the actionbar when the search view is launched so is there any way i can do that?

Regards,
SK
 

corwin42

Expert
Licensed User
Longtime User
I will see what I can do to expand the SearchView. onQueryTextChange should be possible.

If you use a ToolBar you can modify the action items when search view is opened and make them invisible.
 
Top