GradleVersion | Gradle automatic version builder | Plugin library

Add google() to your repositories { } block. The Android Gradle plugin is located there.

I solved it. If you are using the react-native-intercom wrapper. You need to update it, after update everything works fine

I can't believe I wasted two days straight on this because someone wrote the package with an uppercase letter. There was a class in a package :

In the variables block you can't set the value from reading a file.

What you can do for achieve your goal is to add a simple PowerShell task that read the version from the file and set it as build name with logging command. something like:

I solved the problem by change the app’s targetSdkVersion and CompileSdkVersion (refer to Migrating apps to Android 11), else there’ll be a lot of deprecated functions.

I found this link :- Uninstall Android Studio with complete effect

Note: Some sections here will be moved to the question section above, and also some sections from the above question section are worthy to be moved here in the answer.

Once verified whether this is working successfully, I will update a detailed answer.

Update:

1. The Lint and the IntelliSense, both are not working, and TODOs are not highlighting, after this solution. Now I don't see any red marks, so it is just like working in a plain text editor, except for the keywords highlighting.

IntelliSense not working:

1. The Analysis process (top end of the editor screen), never stops.

2. There is not a single change after I deleted the .gradle and .idea folders in the root folder.

3. Some of the IntelliSense came back after invalidating the cache and restarting Android Studio.

4. Following: Rename folders inside your {{user_dir}}/.android folder.

5. Step by step, we are coming to a close and only this is left: Some of the newly added variables in the binding (layout) are not recognized while the older widget ids are still recognized (in the camel case (Kotlin), from snake case (layout XML)).

New Ids in layout --> binding, are not recognized:

Old Ids in layout --> binding, are still recognized:

Let me observe this for some time, to see whether it comes to normal and come up with more updates. As usual, I face no issues while building and running the APK on my Android device.

There're multiple issues with your setup from the tooling perspective. According to Gradle's Java Compatibility Matrix, Gradle 4.3 is not compatible to Java 11. Gradle 4.3 supports Java 9 only. The Spring Boot plugin in version 1.5.3.RELEASE requires Gradle 3.x, according to their System Requirements.

If using Spring Boot 1.5.3.RELEASE is mandatory, I suggest downgrading to Gradle 3.5 and Java 8.

Usually http protocol over TLS/SSL uses 443/tcp ports, Also when it is working fine locally, it should work as expected after the deployment. Looks like we are missing few configurations for webapps.

Below are few important key aspects which should be looked into:

Deployment steps of a webapp.

Refer to the blog to understand about running tomcat in App Service and automating it with pipeline in azure.

If your application will be visible on a custom domain, you'll need to map your web application to it. Then, you'll need to bind the SSL certificate for that domain to your App Service Web App

Configuring custom tls/ssl in Azure App Service

Azure App Service provides a highly scalable, self-patching web hosting service. This article shows you how to create, upload, or import a private certificate or a public certificate into App Service.

Also, to create custom TLS/SSL bindings or enable client certificates for your App Service app, your App Service plan must be in the Basic, Standard, Premium, or Isolated tier.

I got the same issue as you, then I fixed it by following these steps:

1. Add publish plugin