java.lang.NullPointerException: in == null
See original GitHub issueUsing Jsoup 1.8.3 in my Android app which is now targetting SDK 23 (Marshmallow) and am seeing frequent crashes when trying to get the Document as follows:
Jsoup.connect(link).get()
The stack is as follows:
09-03 17:38:39.873 13223-13291/org.MAW.tweetcomb E/AndroidRuntime﹕ FATAL EXCEPTION: AsyncTask #2 Process: org.MAW.tweetcomb, PID: 13223 java.lang.RuntimeException: An error occurred while executing doInBackground() at android.os.AsyncTask$3.done(AsyncTask.java:309) at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354) at java.util.concurrent.FutureTask.setException(FutureTask.java:223) at java.util.concurrent.FutureTask.run(FutureTask.java:242) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) at java.lang.Thread.run(Thread.java:818) Caused by: java.lang.ExceptionInInitializerError at org.jsoup.nodes.Entities.access$000(Entities.java:16) at org.jsoup.nodes.Entities$EscapeMode.<clinit>(Entities.java:19) at org.jsoup.nodes.Document$OutputSettings.<init>(Document.java:373) at org.jsoup.nodes.Document.<init>(Document.java:18) at org.jsoup.parser.TreeBuilder.initialiseParse(TreeBuilder.java:29) at org.jsoup.parser.TreeBuilder.parse(TreeBuilder.java:42) at org.jsoup.parser.HtmlTreeBuilder.parse(HtmlTreeBuilder.java:53) at org.jsoup.parser.Parser.parseInput(Parser.java:30) at org.jsoup.helper.DataUtil.parseByteData(DataUtil.java:132) at org.jsoup.helper.HttpConnection$Response.parse(HttpConnection.java:603) at org.jsoup.helper.HttpConnection.get(HttpConnection.java:195) at org.MAW.tweetcomb.AsyncTasks.JSoupFetcher.doInBackground(JSoupFetcher.java:47) at org.MAW.tweetcomb.AsyncTasks.JSoupFetcher.doInBackground(JSoupFetcher.java:21) at android.os.AsyncTask$2.call(AsyncTask.java:295) at java.util.concurrent.FutureTask.run(FutureTask.java:237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) at java.lang.Thread.run(Thread.java:818) Caused by: java.lang.NullPointerException: in == null at java.util.Properties.load(Properties.java:246) at org.jsoup.nodes.Entities.loadEntities(Entities.java:236) at org.jsoup.nodes.Entities.<clinit>(Entities.java:220) at org.jsoup.nodes.Entities.access$000(Entities.java:16) at org.jsoup.nodes.Entities$EscapeMode.<clinit>(Entities.java:19) at org.jsoup.nodes.Document$OutputSettings.<init>(Document.java:373) at org.jsoup.nodes.Document.<init>(Document.java:18) at org.jsoup.parser.TreeBuilder.initialiseParse(TreeBuilder.java:29) at org.jsoup.parser.TreeBuilder.parse(TreeBuilder.java:42) at org.jsoup.parser.HtmlTreeBuilder.parse(HtmlTreeBuilder.java:53) at org.jsoup.parser.Parser.parseInput(Parser.java:30) at org.jsoup.helper.DataUtil.parseByteData(DataUtil.java:132) at org.jsoup.helper.HttpConnection$Response.parse(HttpConnection.java:603) at org.jsoup.helper.HttpConnection.get(HttpConnection.java:195) at org.MAW.tweetcomb.AsyncTasks.JSoupFetcher.doInBackground(JSoupFetcher.java:47) at org.MAW.tweetcomb.AsyncTasks.JSoupFetcher.doInBackground(JSoupFetcher.java:21) at android.os.AsyncTask$2.call(AsyncTask.java:295) at java.util.concurrent.FutureTask.run(FutureTask.java:237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) at java.lang.Thread.run(Thread.java:818)
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (4 by maintainers)

Top Related StackOverflow Question
So I fixed this locally by putting the Jsoup source locally in my project and moving the two .properties files to my “resources” folder and changing line 235 of Entities to
InputStream in = Entities.class.getClassLoader().getResourceAsStream(filename);instead ofInputStream in = Entities.class.getResourceAsStream(filename);Since 1.11.1 with this change #959, entities are loaded from data embedded in a class, not a property file, so we shouldn’t get hit by this Android bug any more.