Скачать или смотреть Solving the API level 21 Error in Android Custom Views

Address the `API level 21` error when creating custom views in Android with a lower minSdk. Learn how to adjust constructors effectively to maintain compatibility.
---
This video is based on the question https://stackoverflow.com/q/64236570/ asked by the user 'drax' ( https://stackoverflow.com/u/14359766/ ) and on the answer https://stackoverflow.com/a/64236870/ provided by the user 'Victor Cold' ( https://stackoverflow.com/u/9553363/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Call requires API level 21 (current min is 19): android.view.View()

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the API Level 21 Error

Creating custom views in Android can greatly enhance your application's interface and user experience. However, developers often encounter compatibility issues related to the Android API levels. One common error is the "Call requires API level 21 (current min is 19): android.view.View()" message.

This error arises when you attempt to use constructors or methods that are only available in API level 21 (Lollipop) while your application has set a minimum SDK version of 19 (KitKat). In this guide, we’ll explore how to resolve this issue effectively, allowing you to create custom views without sacrificing compatibility.

Solution Breakdown: Adapting Your Custom View Code

To solve the API level 21 error, we need to modify the way we define the constructor for our custom view. The solution involves using a different constructor approach. Let’s break this down into clear steps.

Step 1: Use the Correct Constructor

The constructor you initially attempted to use has additional parameters that are not available before API level 21. Instead, we will focus on using a constructor that only requires three parameters:

Context

AttributeSet (optional)

defStyleAttr (optional)

Here’s the corrected code:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Utilize @ JvmOverloads Annotation

By adding the @ JvmOverloads annotation, we can provide default values for parameters, allowing the compiler to generate overloaded constructors automatically. This significantly simplifies how we manage our custom view's initialization.

With @ JvmOverloads, your Dummy class will gracefully handle various constructor calls. It effectively means that you can create instances of your class using fewer parameters, promoting flexibility and ease of use.

Key Points to Remember

Always ensure you’re using constructors that are compatible with your set minimum SDK.

The preferred method to create your custom view is to utilize a constructor that takes three parameters and optionally use @ JvmOverloads to define defaults.

Testing your custom view across multiple API levels can be beneficial to ensure stability.

Conclusion

Though platform compatibility can sometimes create hurdles in Android development, understanding how to adapt your view constructors is crucial. By following the steps outlined above, you can resolve the API level 21 error and create robust, custom views that support older versions of Android.

Remember, always check the Android developer documentation for constructor methods and compatibility issues to stay informed!

By keeping your code flexible and compatible with different API levels, you ensure a broader reach for your application and a better user experience overall.