Android Studio 3.2.1 - Cannot Sync Project with Gradle Files: Argument for @Notnull Parameter 'Message' of ... Must Not Be Null

Android Studio 3.2.1 - Cannot sync project with gradle files: Argument for @NotNull parameter 'message' of ... must not be null

Ok, I was finally able to figure out the reason.

The problem was, that my project folder resided on a different hard disk partition, than my home folder. The folder containing my android projects was linked to my home folder with a symbolic link.

I can't tell whether its the symbolic link, or the other partition, that is causing the problem. I haven't checked that. Maybe it works if you have it on the same partition but linked with a symbolic link. Maybe it works when used on another partition without symbolic links. But for anyone experiencing this problem -> Check if one of these might be your cause as well.

Some extra information: My android project folder resided on a hard disk partition formatted with ZFS.

Gradle sync failed: Argument for @NotNull parameter 'aFileName' of com/intellij/openapi/util/io/FileUtil.toSystemIndependentName must not be null

I found the solution for this issue,i just did invalidate cache and restart it, it worked.

but still if there is issue i suggest try to change compileSdkVersion from gradle

Error when creating new project in android studio 3.3.2

I found the answer.
Actually my company network system blocked the required URL. I got full access in IP. Then it was rectified. I can create a new project without fail.

Why is Android Studio reporting URI is not registered?

You are having this issue because you are at the wrong destination! The correct directory for the Layout resource file has to be under "res-layout" not "res-all-layout"

Why is Android Studio reporting URI is not registered?

You are having this issue because you are at the wrong destination! The correct directory for the Layout resource file has to be under "res-layout" not "res-all-layout"

Django: /logout switches language

OK. So here's the answer. I thought I'd write it down since someone else CAN end up in this situation.

The problem was that I had switched the order between django locale middleware and the middleware own my own that takes away the brwoser selected language. Need to keep your own interception before Django takes it over and sets the language to whatever the browser tells it to (which is a really weird default behavior in any case).

Hope it helps someone.

'myapp.middleware.ForceDefaultLanguageMiddleware',   # <-- BEFORE django locale!!
'django.middleware.locale.LocaleMiddleware',

---

Related Topics