NPE while inflating layout (Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference)
Change <view
to <View
, because view
is not about empty view. It's for custom view defined through class
attr, like below:
<view
android:layout_width="wrap_content"
android:layout_height="wrap_content"
class="com.your.package.YourCustomView" />
And you got
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
because of LayoutInflater
tries to parse class
attr:
LayoutInflater
source code
//...
View createViewFromTag(View parent, String name, Context context, AttributeSet attrs,
boolean ignoreThemeAttr) {
if (name.equals("view")) { // line 724
name = attrs.getAttributeValue(null, "class"); // line 725
}
// Apply a theme wrapper, if allowed and one is specified.
if (!ignoreThemeAttr) {
final TypedArray ta = context.obtainStyledAttributes(attrs, ATTRS_THEME);
final int themeResId = ta.getResourceId(0, 0);
if (themeResId != 0) {
context = new ContextThemeWrapper(context, themeResId);
}
ta.recycle();
}
if (name.equals(TAG_1995)) { // line 738
// Let's party like it's 1995!
return new BlinkLayout(context, attrs);
}
//...
- On line 724 it check that your tag is
view
and getstrue
- On line 725 it tries to get class through
class
attr and getsnull
- On line 738 it tries to check for
blink
tag and gets crash
Also, there is a curious thing, Android developers added Easter egg, you can try it:
<view
android:layout_width="wrap_content"
android:layout_height="wrap_content"
class="blink">
<TextView
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:gravity="center"
android:text="Some text" />
</view>
Error: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
This has nothing to do with Android Studio updates
You see this line here
user.getId().equals(firebaseUser.getUid())
This is throwing a NullPointerException, as it's cleared at the log, to avoid such case you should change it to
if(user.getId() != null && user.getId().equals(firebaseUser.getUid())
This should avoid the crash but probably means that you don't assign id correctly for the users in your database (because technically all users should have ids)
Error in list adapter : Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
The problem is this:
<view
android:layout_width="match_parent"
android:layout_height="2dp"
android:background="@android:color/background_light"
android:layout_below="@+id/movieImage">
</view>
<view>
starts with small letter :) You need <View>
Also see this:
Explaination here
What is a NullPointerException, and how do I fix it?
There are two overarching types of variables in Java:
Primitives: variables that contain data. If you want to manipulate the data in a primitive variable you can manipulate that variable directly. By convention primitive types start with a lowercase letter. For example variables of type
int
orchar
are primitives.References: variables that contain the memory address of an
Object
i.e. variables that refer to anObject
. If you want to manipulate theObject
that a reference variable refers to you must dereference it. Dereferencing usually entails using.
to access a method or field, or using[
to index an array. By convention reference types are usually denoted with a type that starts in uppercase. For example variables of typeObject
are references.
Consider the following code where you declare a variable of primitive type int
and don't initialize it:
int x;
int y = x + x;
These two lines will crash the program because no value is specified for x
and we are trying to use x
's value to specify y
. All primitives have to be initialized to a usable value before they are manipulated.
Now here is where things get interesting. Reference variables can be set to null
which means "I am referencing nothing". You can get a null
value in a reference variable if you explicitly set it that way, or a reference variable is uninitialized and the compiler does not catch it (Java will automatically set the variable to null
).
If a reference variable is set to null either explicitly by you or through Java automatically, and you attempt to dereference it you get a NullPointerException
.
The NullPointerException
(NPE) typically occurs when you declare a variable but did not create an object and assign it to the variable before trying to use the contents of the variable. So you have a reference to something that does not actually exist.
Take the following code:
Integer num;
num = new Integer(10);
The first line declares a variable named num
, but it does not actually contain a reference value yet. Since you have not yet said what to point to, Java sets it to null
.
In the second line, the new
keyword is used to instantiate (or create) an object of type Integer
, and the reference variable num
is assigned to that Integer
object.
If you attempt to dereference num
before creating the object you get a NullPointerException
. In the most trivial cases, the compiler will catch the problem and let you know that "num may not have been initialized
," but sometimes you may write code that does not directly create the object.
For instance, you may have a method as follows:
public void doSomething(SomeObject obj) {
// Do something to obj, assumes obj is not null
obj.myMethod();
}
In which case, you are not creating the object obj
, but rather assuming that it was created before the doSomething()
method was called. Note, it is possible to call the method like this:
doSomething(null);
In which case, obj
is null
, and the statement obj.myMethod()
will throw a NullPointerException
.
If the method is intended to do something to the passed-in object as the above method does, it is appropriate to throw the NullPointerException
because it's a programmer error and the programmer will need that information for debugging purposes.
In addition to NullPointerException
s thrown as a result of the method's logic, you can also check the method arguments for null
values and throw NPEs explicitly by adding something like the following near the beginning of a method:
// Throws an NPE with a custom error message if obj is null
Objects.requireNonNull(obj, "obj must not be null");
Note that it's helpful to say in your error message clearly which object cannot be null
. The advantage of validating this is that 1) you can return your own clearer error messages and 2) for the rest of the method you know that unless obj
is reassigned, it is not null and can be dereferenced safely.
Alternatively, there may be cases where the purpose of the method is not solely to operate on the passed in object, and therefore a null parameter may be acceptable. In this case, you would need to check for a null parameter and behave differently. You should also explain this in the documentation. For example, doSomething()
could be written as:
/**
* @param obj An optional foo for ____. May be null, in which case
* the result will be ____.
*/
public void doSomething(SomeObject obj) {
if(obj == null) {
// Do something
} else {
// Do something else
}
}
Finally, How to pinpoint the exception & cause using Stack Trace
What methods/tools can be used to determine the cause so that you stop
the exception from causing the program to terminate prematurely?
Sonar with find bugs can detect NPE.
Can sonar catch null pointer exceptions caused by JVM Dynamically
Now Java 14 has added a new language feature to show the root cause of NullPointerException. This language feature has been part of SAP commercial JVM since 2006.
In Java 14, the following is a sample NullPointerException Exception message:
in thread "main" java.lang.NullPointerException: Cannot invoke "java.util.List.size()" because "list" is null
List of situations that cause a NullPointerException
to occur
Here are all the situations in which a NullPointerException
occurs, that are directly* mentioned by the Java Language Specification:
- Accessing (i.e. getting or setting) an instance field of a null reference. (static fields don't count!)
- Calling an instance method of a null reference. (static methods don't count!)
throw null;
- Accessing elements of a null array.
- Synchronising on null -
synchronized (someNullReference) { ... }
- Any integer/floating point operator can throw a
NullPointerException
if one of its operands is a boxed null reference - An unboxing conversion throws a
NullPointerException
if the boxed value is null. - Calling
super
on a null reference throws aNullPointerException
. If you are confused, this is talking about qualified superclass constructor invocations:
class Outer {
class Inner {}
}
class ChildOfInner extends Outer.Inner {
ChildOfInner(Outer o) {
o.super(); // if o is null, NPE gets thrown
}
}
Using a
for (element : iterable)
loop to loop through a null collection/array.switch (foo) { ... }
(whether its an expression or statement) can throw aNullPointerException
whenfoo
is null.foo.new SomeInnerClass()
throws aNullPointerException
whenfoo
is null.Method references of the form
name1::name2
orprimaryExpression::name
throws aNullPointerException
when evaluated whenname1
orprimaryExpression
evaluates to null.a note from the JLS here says that,
someInstance.someStaticMethod()
doesn't throw an NPE, becausesomeStaticMethod
is static, butsomeInstance::someStaticMethod
still throw an NPE!
* Note that the JLS probably also says a lot about NPEs indirectly.
attempt to invoke virtual method 'void android.widget.Button.setOnClickListener(android.view.View$onClickListener)'
findViewById
is actually is called this:
this.findViewById(someId);
this
refers to Activity (in your case IntroductoryActivity
);
From the docs:
Finds a view that was identified by the android:id XML attribute that was processed in onCreate(Bundle).
This onCreate()
method is onCreate
method of Activity on which you are calling findViewById
. In your case, that id (and View) belongs to fragment so Activity is unable to find view associated with that id and returns null and you get NPE when you want to setOnClickListener
to start_l
button.
You can set onClickListener to that button inside onViewCreated
method of fragment:
@Override
public void onViewCreated(View view, Bundle savedInstanceState) {
super.onViewCreated(view, savedInstanceState);
start_l=view.findViewById(R.id.startb);
start_l.setOnClickListener.......
}
Edit: suggestion by Prince Ali is also a possible and maybe better way to do it. You can initialize views inside onCreateView
:
public View onCreateView(@NonNull LayoutInflater inflater, @Nullable ViewGroup container, @Nullable Bundle savedInstanceState) {
ViewGroup root=(ViewGroup) inflater.inflate(R.layout.fragment_on_boarding3,container,false);
start_l=root.findViewById(R.id.startb);
start_l.setOnClickListener.......
return root;
}
I also recommend looking at this post
Related Topics
How to Change Default Dialog Button Text Color in Android 5
Convert a PDF Page into Bitmap in Android Java
Call Activity Method from Adapter
Could Not Find Com.Android.Tools.Build:Gradle:3.0.0-Alpha1 in Circle Ci
Problems with Android Fragment Back Stack
How to Get String Width on Android
Alarmmanager Fires Alarms at Wrong Time
How to Deal with Install_Parse_Failed_Inconsistent_Certificates Without Uninstall
How to Enable/Disable Bluetooth Programmatically in Android
Android Studio 0.4 Duplicate Files Copied in APK Meta-Inf/License.Txt
How to Provide Shadow to Button
Finish All Activities at a Time
Start an Activity with a Parameter
How to Bring an Activity to Foreground (Top of Stack)
How to Use Searchview in Toolbar Android
Lollipop's Backgroundtint Has No Effect on a Button
Cannot Retrieve Field Values from Realm Object, Values Are Null in Debugger