mobile-client | Mobile acquisition and inferencing client | Machine Learning library

Currently, the company I work for uses AWS libraries in multiple Android apps, AWS libraries like:

I have been trying to use AWS SDKs for Push Notifications. But I am getting errors. Tried to find a solution, but can't find much support for this.

iOS & Web push notifications are working fine

What all is already setup & done:

• AWS back-end & console setting in place.
• Identity Pool Id & other keys in place.
• ARN topic in place.

Android side:

• AWS SDK dependencies:

  ...

My Android App using AWS S3 to store images. below is the version details I'm using.

As far as I have read the other link regarding similar issues like this, there is always the issue of 2 libraries conflicting, I think that's the case with me too but can anyone tell me which library is causing the conflict or what is the issue and how do I resolve this issue? Below is my Gradle, and I only get this one line error in my stack trace. Any help would be appreciated. This error only comes when I run any instrumented test in this package, I have other packages as libraries, and all of those tests run fine, but I can't run any instrumented test in this package.

1. I am getting Duplicate class com.google.protobuf.AbstractMessageLite found in modules jetified-protobuf-javalite-3.11.0.jar (com.google.protobuf:protobuf-javalite:3.11.0) and jetified-protobuf-lite-3.0.1.jar (com.google.protobuf:protobuf-lite:3.0.1).

2. I have not seen an answer that clears up my issue. I appreciate any assistance.

   ...

I have an Android app that explicitly uses the latest (v2.15.+) version of Amazon's AWS library, but it also has a dependency on an ungodly huge library (netcdf4) that appears to be pulling in its own (old) copy (v1.11.236) of Amazon's non-Android Java library and causing "Duplicate class" errors when building.

I know I need to somehow modify build.gradle so it uses the old (v1.11.236) version only for things pulled in by implementation group: 'edu.ucar', name: 'netcdf4', version: '4.6.11', but uses the new (v2.15.+) version for everything else... but I'm not sure how to actually do that.

Inspired by the answer to another question, I tried adding the following to the end of the "android{}" block (in the hope that it would unceremoniously strip out the non-Android .jars and allow everything to compile without errors).

Good day all,

I am implementing AWS Amplify DataStore for android following the docs, and basically i get this error when i try to initialize the data store plugin on amplify according to this part of the doc:

Cannot resolve symbol 'AmplifyModelProvider'

You can find code from my gradle files and my application class below.

I am not an android expert, but i believe this is because of a missing dependency or i am doing something wrong during initialization or assignation of the ModelProvider. But i cant find any information on internet about this issue or any possible solution.

Thanks in advance for your help.

Steps to reproduce:

1. Create new android project

2. Install Amplify CLI, using npm, npm install -g @aws-amplify/cli

3. Configure amplify, amplify configure

4. On new android project root folder, run amplify init, amplify init

5. On new android project root folder, run amplify add auth, amplify add auth, adding authentication

6. Create android application class

7. Add android application class to AndroidManifest.xml

8. Try to add data store plugin to amplify on onCreate method of the application class

I already try the following solutions:

1. Clean project

2. Rebuild project

3. Run Make Project

4. Close and open again Android Studio

AndroidManifest.xml:

After I updated to the newest plugin for kotlin I get this build error in my project

This is for a largish 3-4 year running Android project, running on Gradle 5.4.1. Integration testing is with Mockito, espresso and dagger.

I have run into an issue where we are adding a Pendo library to the project, the dependency was added to Gradle as standard. Everything runs fine, until we try to run integration tests (~2000), these are run in shards with Spoon.

Around half way through the integration tests, on random tests each time, we run into a native crash killing the test run, due to LinearAlloc exceeding capacity. Running these tests in isolation, or in their classes locally they pass with no issues and have been stable for a long time.

I brought the whole app back to the known good build, added the Pendo dependency only and this results in the same problem, however I don't believe this is due to Pendo, as I tested by coming back to a known good build (tested on again at this point for sanity) and adding a random new dependency, this resulted in the same problem.

From what I can find this may be something to do with the method limits around Android. I should mention we are using multidex to break the app down. Proguard and minify are also being used.

Part of the issue here is that I'm really not sure what to look at to figure out what's going on to cause this overflow. Following the logs for the test runs, nothing appears to be amiss, bar a fair bit of garbage collection (which I'm guessing means a leak somewhere). I'm unsure if this issue is down to some underlying leak, and the new libraries are pushing something just over the edge, or if there's some dependency limit in android that I'm unaware of, or some other way to break the files down so we aren't causing LinearAlloc to fill up.

From reading, I know the limits of LinearAlloc were upped around Android 5, we are having problems on devices both above (Android 10) and below this (Android 4) and I don't really see much chat around this since 2017, so I feel like I'm missing something obvious, or something is misconfigured in the project given it was setup before then.

Any help would be really appreciated. I've dumped a cut down version of the gradle file below