Office Hours Transcript: 2021-05-08

Hey Mark

I’ve been having a few issues since upgraded from AS 4.1.3 to 4.2

I wrote about one of them here: https://stackoverflow.com/questions/67438562/android-studio-4-2-throws-a-null-pointer-exception-on-incremental-builds

It’s super annoying.

It must be some setting in my project that isn’t compatible, because I actually uninstalled the upgraded version, installed 4.2 from scratch, and I am still seeing it.

But I don’t know what to look for, and SO searching hasn’t yielded much

any ideas?

That’s the thing - I’m not using Kotlin at all!

Pure Java project

And a full build always works

just incremental fails

Haven’t tried that, one sec

It’s got to be some gradle setting somewhere I would guess, but darned if I can figure out what

OK it’s building

OK that did not throw the error

no - never have done that.

What do I need to do?

I don’t

where is gradlew housed? I’m on a Windows box and it must not be in the path

Duh. I was in the wrong spot

one sec

That is working - got passed the task that was throwing the error

let me make another change, and try it again.

past

build successful

I had it work once or twice from Android also, then it would flip back to giving that error

OK it failed this time from the command line

Task :app:compileDebugJavaWithJavac FAILED
Note: Version 10.5.0 of Realm is now available: https://static.realm.io/downloads/java/latest
Note: Processing module DefaultRealmModule
Note: Processing module DefaultRealmModuleMediator
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':app:compileDebugJavaWithJavac’.

kotlin.KotlinNullPointerException

• Try:
  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

• Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '–warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.7.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 4s
29 actionable tasks: 1 executed, 28 up-to-date

C:\BLD\AndroidStudioProjects\InTouch>

does that argument go before or after the app: argument?

Build successful.

So weird

Now I change one line and try it again and it fails:

yes

I can’t send the full stack trace - your chat software says I’m being rate-limited or blocked :)

Caused by: java.lang.RuntimeException: kotlin.KotlinNullPointerException
at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:163)
at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100)
at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94)
at org.gradle.internal.compiler.java.IncrementalCompileTask.call(IncrementalCompileTask.java:74)
at org.gradle.api.internal.tasks.compile.AnnotationProcessingCompileTask.call(AnnotationProcessingCompileTask.java:94)
at org.gradle.api.internal.tasks.compile.ResourceCleaningCompilationTask.call(ResourceCleaningCompilationTask.java:57)

I saw one post from a year or so ago saying their problem that caused what looked like a similar issue was the annotation processor being used, and I notice that in this trace.

But I’ve got the most recent one in my gradle file

implementation 'androidx.annotation:annotation:1.2.0'

Sorry, right

annotationProcessor 'androidx.annotation:annotation:1.2.0'

I don’t know what pastbin.com is

https://pastebin.com/TfP8snFV

Running the exact same gradlew command a second time works

OK let me see if they have an update for 4.2

I have the latest

So I’ll post a note to them

Same result now within AS as command line - if I run the incremental build a second time and make no code changes, it works.

I have another question for you - I have a preference in my settings that is supposed to give the user the ability to open the details screen for my app in their Android settings on their device.

This was working for a while, and now all of a sudden it is crashing with an error that indicates no app can satisfy the intent.

So I changed the setup to no longer have the intent in the XML definition of the preferences, and instead handle it in the app like this:

            Preference systemPreference = findPreference(InTouch.getInstance().getString(R.string.pref_system_settings_key));
            if ( systemPreference != null ) {
                systemPreference.setOnPreferenceClickListener( preference -> {
                    Intent i = new Intent(ACTION_APPLICATION_DETAILS_SETTINGS);
                    try {
                        startActivity(i);
                        return true;
                    } catch (Exception e) {
                        // Try the generic application settings, and if that fails, show message
                        // and punt.
                        i = new Intent(ACTION_APPLICATION_SETTINGS);
                        try {
                            startActivity(i);
                            return true;
                        } catch (Exception exception) {
                            InTouchDialogUtils.showAlertDialog(getString(R.string.pref_system_settings_error_title),
                                    getString(R.string.pref_system_settings_error_message, getString(R.string.app_name_full)),
                                    requireActivity());
                            return false;
                        }
                    }
                });
            }

I totally missed that when looking at the list of intents. Duh.

I am not sure I understand where this goes

Oh, of course.

Geez sometimes I wonder if I ever actually got out of bed…

You too!