libai | A library compiling Artificial Intelligence algorithms | Learning library

I was able to solve by adding this to build.gradle

One workaround I found that is working is to use ai.api.AIConfiguration.SupportedLanguages which is resolving instead of ai.api.android.AIConfiguration.SupportedLanguages which is not resolving in kotlin in Android Studio 3.0 as mentioned in the question.

However, calling ai.api.android.AIConfiguration.SupportedLanguages works just fine in Java code, in which case it is resolving correctly in Android Studio 3.0. Since ai.api.android.AIConfiguration implements ai.api.AIConfiguration, why this issue is arising is puzzling!

You have a problem with the order of plugins applied.

apply plugin: 'com.google.gms.google-services' This should always be kept at the end of file.

Also, apply plugin: "io.fabric" should be applied after com.android.application.

If you still have confusions on build.gradle. Edit your question including both buid.gradle files from app and root project, and inform me by commenting on this answer.

R.raw.test_agent_credentials refers to the test_agent_credentials.json file that is presumed to be in the raw resource folder. This JSON file contains the full credentials file that you downloaded when you created the Dialogflow Integration service account.

Ignore the section about using the key. It uses the gloud command to generate the key to use in the auth header. You're doing this with the GoogleCredentials.fromStream() call.

The important part was from step 10 before where you save the JSON key file and make it available to Android as a raw resource. See this information about Android resources and, in particular, the section about raw resources. Raw resources should be placed under the "resource" folder in a sub-folder called "raw". The name of the file you save there should match the part of the resource name after R.raw without the "json" extension.

The reason for an app to crash can be Compile-Time Errors or Run-Time Errors.

Compile-Time Errors can be syntax errors , class not found errors, overloading errors which are shown and recorded by the Android Studio. In your case there would be no Compile time errors since your app is correctly getting compiled and installed on the device.

Run- Time errors occur when you are using (running) the app. They are mostly logical errors or variable declaration errors. In your case may be the problem lies here only.

When you are running the app the codes are being executed and the logic is also executed. Thus if you have given some wrong logic in your code such as infinite loop, passing string instead of integer data type and many more then the app is getting crashed.

You must check the Log to see what is the exception which caused the crash. In the log (lower part of the IDE) there will be the name of the Exception, the element which launched it and also there will be the links to the lines of the code where the problem was found.

If you still can't find the error this way, you can set breakpoints at the left of the lines of code where you want the application stops during debug, and then run the app in the debug mode to see exactly what happens.

Another tip: often, when I was sure about the rightness of my code and it runs but crashes, it's about having declared all the Activities in the manifest (or all the Services) and to have set all required permission. Because in this case there are no apparent errors before running the app.

What the error is telling you is that you've reached the method count limit in Android. This can be solved two ways: Either you start removing dependencies or you enable multidexing. The latter can be enabled the following way:

This is happening because you are mixing the old dependencies with new ones. So in order to solve your problem, delete the following line of code from your build.gradle file.